When your customers speak different languages, keep one feedback board and translate each post and comment into every reader's language, with the original a click away. Don't run one board per language, and don't make everyone write in English. The same request in five languages then stays one request with one vote count. Every customer reads the board in their own language, and nobody's words are replaced by a machine's.
Three ways to handle languages#
I build Swingback in Switzerland, a country of four national languages, where a product's customers rarely all write in the same one. Each of the usual answers costs something:
- One language for everyone, usually English. It's the cheapest, and you pay for it in what you don't hear. People writing in a second language write shorter and vaguer requests, and some don't write at all. The customer who would have explained their whole workflow in French sends three words in English, or nothing.
- A board per language. Everyone writes comfortably, and every request splits. "Export to PDF" arrives on the French board, the German board and the English one, each with a third of the votes, so none of them looks like what your customers want most. Your team reads five boards, and keeps five copies of each status in step by hand.
- One board, translated. One request, one count, one status, and each reader reads it in their language. What it costs is a translation for each post and comment, and some rules about what a translation may do.
The third one is the only one where votes add up. It's the same reason duplicates hurt: a request split across five places looks five times smaller than it is.
What a translation must never do#
A translation is text that nobody on your team wrote and, often, nobody read before it went up. So it needs bounds. These are the ones I settled on:
- Never replace the original. The original stays a click away: the translation shows under a line that says it's automatic and which language it came from. The author always reads their own words.
- Never outlive an edit. When someone changes their post, its translations go at once, and new ones are written. A translation of an older text is worse than none.
- Never change what isn't words. Formatting, code and links stay as they are. A translation with a link or an image the original doesn't have is thrown away whole: otherwise, a translation would be a way to slip a link past your moderation.
- Never reach what you held back. What a rule or the AI flagged, and what you held or rejected, isn't translated. A post that only waits for your approval is, so that your reviewers can read it. Your team's internal notes never are: they aren't even sent to the model.
Search should keep matching the original's words too, and emails should quote a post as its author wrote it. A translation is for reading, not a second version of the record.
The rest of the board in their language#
Translating posts helps little if the buttons around them are in a language the reader doesn't read. The board's own words, its buttons, labels, statuses and dates, should follow the reader. That means the language their browser asks for, with a menu to change it, and your default language for the rest.
The page where people write matters most. It should say plainly that they can write in their own language and that others will read it in theirs. Without that line, people assume the board is English-only and write in the English they have.
Let readers turn it off#
Some readers would rather read every post as written. A bilingual customer, or a team member who reads French better than a machine translates it, should be able to turn translations off for themselves, without turning them off for anyone else. Two switches, then: the workspace's, which decides what gets translated, and each reader's, which decides what they see.
A model, not a translation service#
When I compared them in October, translating a post into six languages with a language model came out about 20 to 50 times cheaper than the translation services at their list prices. And a model can be told what to leave alone: code, product names, links and Markdown, which is what people complain about on boards that translate. One request per post does all the languages at once, and names the language it was written in.
The checks above are what make a model safe here: an answer missing a language, of a very different length from its original, or with an address the original doesn't have, is refused whole, and the post simply shows as written.
In Swingback#
Your portal speaks English, French, German, Spanish, Italian, Portuguese and Dutch, to each visitor in theirs. With Translate posts and comments Beta on, under Settings → AI, each post and public comment is translated into the others, by Anthropic's Claude, and shown under a line that says it's automatic, with the original a click away. Each member of your team reads them in the dashboard in their own language, and a customer who'd rather not turns them off on their Your account page.
It's on every plan. A post or comment counts as one read the first time the AI reads it, whatever it does with it: a post tagged, checked for duplicates and translated is one read. It counts again when the AI reads it after an edit, or when someone asks the AI about it again, such as where its issue could go. A month has 50 on Free and 2,000 on Pro. A backfill Beta translates the posts you had before turning it on, and a post whose title and text pass 4,000 bytes stays as written.
AI features has every rule, and Portal and boards how the portal picks a reader's language.
