How to send appointment reminders in each client's own language
Store a preferred language on each client record, then send from message templates that already exist in that language. At send time the message is selected, not translated — which is what makes it safe to automate across 20 locales.
That is the whole mechanism, and any system can implement it. What differs between tools is how far the language travels: most apply it to one channel and stop. So the test worth applying is simple — does the client's language reach the invoice and the portal login, or only the reminder?
How it works, in three steps
Record the language on the client, not the account
The business has one working language; each client has their own. Storing it on the client record means it travels with them, instead of being a global setting somebody must remember to switch before sending.
Write each message once per language, not once per client
Reminders, invoices and confirmations are templates. Each needs one version per language you serve — written once by a person, then reused for every client who speaks it.
Resolve at send time, and always have a fallback
When a message goes out, take the client's language and fall back to the business's own if they never set one. A missing translation should degrade to a readable message, never to a blank or a raw key.
The part most tools miss
A reminder in the client's language followed by an invoice in yours is a half-finished job. In ClientFlow the stored language is read by appointment and payment reminders, invoices and credit notes, automated messages and portal login mail — so the client sees one language across everything, while the business keeps working in its own.
What this deliberately does not do
It does not machine-translate wording you write yourself. Built-in reminders, invoices and portal pages ship already translated; for your own message text you add a version per language, and ClientFlow falls back to your business language where one is missing. An automated message that quietly machine-translates itself is one you cannot stand behind.
20 locales, at full parity
Every locale carries the same complete key set, so there is no main language with the rest half-finished. Arabic renders right-to-left. Each client record stores its own language, and reminders, invoices, credit notes, automations and portal mail all read it.
Common questions
Does it translate my messages automatically?
No. Built-in reminders, invoices and portal pages are already written in 20 locales, and each client is served the one matching their language. Your own custom wording takes a version per language, and falls back to your business language when one is missing.
What happens if a client has not chosen a language?
They receive the business's own language. Nothing is left blank and no message is held back waiting for a preference to be set.
Which languages are covered?
20 locales, including Arabic with right-to-left layout. They are complete rather than partial — every locale carries the same key set as English.