Esta página se muestra en inglés. La versión en español está en camino.
Help Bilingual
Translating messages between languages
Per-message translation in mixed-language threads, so each side reads in their own language. Set a per-user preference of es, en, or auto.
Quotrr is bilingual in English and Spanish as a first-class feature. The part that matters most in the field is per-message translation in a mixed-language thread, so a contractor, a worker, and a homeowner can each read in their own language without anyone switching back and forth.
How per-message translation works
In a two-way thread, each message is translated for the reader on the other side. If you write in Spanish and your customer reads in English, they see English. When they reply in English, you see Spanish. Nobody has to copy text into a separate translator or pick a shared language to settle on. Each person writes in the language they think in, and reads in the language they think in.
Where it works
- Contractor to worker. A foreman who works in English and a crew lead who works in Spanish can coordinate a job in one thread, each reading their own language.
- Contractor to homeowner. A Spanish-speaking customer and an English-speaking office can talk through a job, a change, or a schedule without a language wall in the middle.
Per-user language preference
Translation follows a per-user language preference, set to es, en, or auto. Auto 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 in their own language rather than forcing one shared choice.
It is the same thread, not a separate one
There is one thread and one record. Translation is a layer on top of it, not a fork. That means the conversation stays in one place tied to the job, and nobody is reading a slightly different version of events. Each side reads the same exchange, rendered in their language.
Why this matters on a real crew
Plenty of crews run mixed. A lead foreman works in English, half the crew works in Spanish, and the customer might go either way. The old fix is a person in the middle who translates by hand, which is slow and drops detail. Per-message translation takes that bottleneck out. A measurement, a schedule change, a question about access, all of it lands in the reader's language the moment it is sent, so the job does not stall waiting on a translator and nothing gets lost in a hallway retelling.
Quinn speaks both
Quinn works in either language and answers in the one you set. If you draft a follow-up or a message and you work in Spanish, Quinn drafts in Spanish, and the customer still reads it in theirs through the same per-message translation. You are never forced into English to use the assistant.
Setting it up
Set your own preference in settings, English, Spanish, or auto, and the whole app speaks that language, including Quinn. For the full picture of bilingual support across proposals and the portal, see Setting up bilingual English and Spanish.
Still stuck? Email [email protected]. Back to the help center.