Help / Quinn and language

Translating messages between languages

Each side writes in the language they think in, and reads in it too.

The bilingual feature that matters most in the field is per-message translation. In a mixed-language thread, a contractor, a worker, and a homeowner can each read in their own language without anyone switching back and forth.

How it works

Each message is translated for the reader on the other side. Write in Spanish and your customer reads English. They reply in English and you read Spanish. Nobody copies text into a separate translator, and nobody has to settle on a shared language.

Where it earns its keep

• Contractor to worker. An English-speaking foreman and a Spanish-speaking crew lead coordinate a job in one thread, each reading their own language.
• Contractor to homeowner. A measurement, a schedule change, a question about access, all of it lands in the reader's language the moment it is sent, with no person in the middle re-telling it and dropping detail.

Per-user preference

Translation follows a per-user setting: es, en, or auto, which follows the device, so most people never touch it. The preference is per user, which is the key. Two people in the same thread can hold different settings and the thread serves each of them.

One thread, one record

Translation is a layer on top of the thread, not a fork. The conversation stays in one place tied to the job, and both sides read the same exchange, rendered in their language. Nobody is reading a slightly different version of events.

Quinn drafts in whichever language you set, and the customer still reads in theirs. The full bilingual picture is in Bilingual English and Spanish.