Eligibility, deadlines and instructions have to read the same in the assistant, on the web page and in the mailed letter. FluentC keeps them identical across every language you serve.
Three agents, one translation. Illustrative example.
Agent flows
Two government & public sector flows, and where FluentC fits.
Example flows, not customer stories. The steps and text are illustrative.
Flow 1
Resident services assistant
An assistant answers residents from program rules, in the language they write in.
Resident question
Service agent
Program rules
FluentC, both ways
Answer
Each agent on its own
The chatbot, the web page and the mailed notice describe eligibility in different words.
With FluentC in the loop
Eligibility and deadline wording is identical in the assistant, on the web and in notices.
Residents ask and read in their own language.
Add languages as your community needs them.
Flow 2
Public notices and forms
Notices are translated once, published, and reissued without starting over.
Notice
Batch job
FluentC
Website
Archive
Each agent on its own
Each reissued notice is worded differently, and staff can't tell what actually changed.
With FluentC in the loop
Reissued notices change only where the English changed.
Reviewed once, reused everywhere.
HTML keeps its markup.
A note on responsible use. For legally binding notices, follow your jurisdiction's rules on certified translation.
Running several agents?
The same words, from every agent.
When each agent translates for itself, the same sentence turns up in several versions. With FluentC in the loop they all return one translation, whichever model is behind them.