home / use cases / email and inbox / multilingual-email-support

Support in their language, notes in yours

An Aivell answers customer email in the sender's language — Portuguese complaint in, Portuguese reply out — while the summary, the internal note and any escalation arrive in yours. Understanding and drafting run onboard the box, so customer correspondence is never shipped to a translation service or an AI cloud.

Watch the demo

starts when: A customer writes in a language your team doesn't speak

The problem

The order came from Porto, the complaint is in Portuguese, and nobody in your Milan office speaks it. So the message sits while someone pastes it into a free translation site — customer name, address and grievance included — composes an answer in stiff English, and hopes the tone survives the round trip. The customer waits a day and receives a reply that sounds like a form.

Selling across borders created this quietly: a support inbox in five languages served by a team that speaks two. Hiring for every market’s language is unrealistic for a small firm, and pasting customer data into web translators is exactly the practice that GDPR’s privacy-by-design principle tells you to engineer away.

How your Aivell does it

  1. The email is understood, whatever the language. Not detected-and-translated — read. The request, the mood and the register all register.
  2. The answer comes from your documents. Return policy, shipping times, price list — retrieved from the knowledge base, then composed natively in the customer’s language. A guardrail keeps your documents the only source.
  3. Your team reads everything in one language. Under each outgoing reply sits an internal note in yours: what was asked, what was answered. Colleagues supervise a Polish conversation without reading Polish.
  4. The sensitive ones become drafts. Refunds, returns, anything with legal wording — prepared with a translated summary and handed to the colleague you named. The original stays attached, untranslated, for the record.
  5. The day closes with a briefing. One evening email: who wrote, in which language, about what. Handy for spotting that German inquiries doubled since the trade fair.

The chore reads like instructions to a multilingual hire — because that’s what it is. And since every word is processed on the box behind your firewall, going multilingual no longer means routing your customers’ private mail through someone else’s servers.

The chore, as you'd write it.

No flowcharts, no code — a chore is just a message to your Aivell, in your own words. It shapes it into a solid, guarded procedure and follows it to the letter. This one:

Giulia Aivell · answer in their language ● active

read every customer email in support@, whatever the language

answer routine questions from the knowledge base, in the sender's language

keep the register right — formal in German and French, warmer in Spanish

under each reply, add an internal note in Italian — what they asked, what was answered

returns and refunds: draft only, pass to Elena with a translated summary

can't tell the language, or it's half dialect? reply in English and say so politely

legal wording in any language goes straight to Elena, original attached untranslated

at 18:00 send Elena the day's list — who wrote, in which language, about what

You
Got it — I'll start right away, and check with you whenever something needs a human.
Giulia Aivell

The tools it uses.

Connected with single-click passkeys — no copied tokens, no OAuth hell.

Email reads and replies across languages
Knowledge Base your policies and prices, the only source

Sensible guardrails.

Every tool can be limited to exactly what this chore needs. For this one, you might set:

Email Replies go only into the customer's own thread; internal mail is restricted to your team's domain.
Knowledge Base Answers draw only on the approved policy and price documents; an unsourced question escalates instead of being invented.

Questions, answered.

Which languages does it handle? +

The major European languages, comfortably — reading, register and all, not word-for-word substitution. The chore adds a safety net you write yourself, like "unsure of the language, fall back to English and escalate". Chores themselves can be written in English, Spanish, French or Italian today.

Isn't this just machine translation stapled to a mailbox? +

No — nothing is translated and pasted. Your Aivell understands the request, finds the answer in your documents, and composes the reply natively in that language, with the register you specified. The internal note in your language is a summary, not a back-translation.

Does customer mail pass through a translation service? +

No, and that's the point of the box. Every step — reading, understanding, drafting — runs onboard, inside your network. Customer names, complaints and order details never reach a translation vendor or an AI cloud.

How do I check replies in a language nobody here reads? +

Through the note under each one — every reply carries a summary in your language of what was asked and answered. Sensitive topics like refunds go out as drafts for human approval, and one sentence in the chore is enough to widen or narrow that list.

Related.

What is an Aivell?

An Aivell is an on-premise AI colleague: a small box that plugs into your network, runs its own AI onboard and takes the repetitive work off your desk. Prompts, documents, data — nothing ever leaves your office. Unplug the internet: it keeps working.

You describe each task as a chore, in plain language. Your Aivell turns it into a solid, guarded procedure and runs it in the background — with guardrails on every tool, a complete audit trail, and approvals in your hand when you want them. One-time setup, fixed monthly fee. No tokens, no overages.

Watch the demo

onboard inference · air-gapped · fixed monthly fee