Core differentiator
Three languages, one conversation
Your business language, your team's language and your customer's language can all be different — and nothing gets lost between them.
Business language
The default language of your workspace — reports, templates and internal notes follow it.
Employee language
Each team member picks their own interface and reading language, wherever they are based.
Customer language
Stored per contact and detected automatically, so every outgoing message matches it.
How it flows
A Japanese customer, a Filipino VA
- 1
Customer sends a message in Japanese
- 2
TumiFlow stores the original message
- 3
Your VA reads it in English or Tagalog
- 4
The VA replies in their own language
- 5
The customer receives it in Japanese
Original · 日本語
初回相談の空き状況を教えていただけますか？できれば今週中が希望です。
Team view · English
Could you tell me your availability for a first consultation? This week would be ideal.
What you get
Built into every conversation
Automatic language detection
Incoming messages are identified on arrival and tagged to the contact record.
Live translation
Threads are readable in your language while the conversation is still moving.
Original-message preservation
The customer's exact wording is always kept and viewable next to the translation.
Translated outgoing replies
Write in your language; the customer receives it in theirs, tone intact.
Per-user interface language
Every teammate sees TumiFlow itself in the language they work in.
Per-contact preferred language
Set it manually or let detection maintain it as the relationship grows.
Interface languages
Planned launch language support
The localization architecture is designed to continuously add interface languages — each one is a translation file, not a rebuild. Arabic switches the interface to right-to-left.