01 / 04
Three separate tools
Support started in webmail, then moved to a translator and a separate draft. Every ticket meant switching between three disconnected tools.
An AI support inbox that syncs, translates, triages and answers customer email, now rolling out to full auto-reply.

The problem
01 / 04
Support started in webmail, then moved to a translator and a separate draft. Every ticket meant switching between three disconnected tools.
02 / 04
The team translated each message into English, then translated the reply back into German. Both steps relied on manual copying and pasting.
Hallo, ich möchte meine Bestellung ändern…
Translate DE → EN
Understand the request
Translate EN → DE
Prepare the answer
03 / 04
Every response began from a blank draft, even for familiar questions. The same answers had to be written again and again.
To: customer@email.de
Hi — thanks for reaching out. I've checked your order and…
04 / 04
Webmail held the messages, but not ownership, history or ticket status. The team had no shared view of what needed attention.
12 unread
No owner
Text only
No history
Local copy
Not shared
Delivered
No ticket status
Email syncs, translates, gets triaged and becomes a ready-to-review reply—in one place.
Sync
Translate
Triage
Reply
Mail syncs every 10 minutes and is threaded into one conversation per customer and topic, shown in English.

The AI reads the full history, tags the topic and picks the next step and the playbook for it.

Routine cases get a reply in the brand's voice, written from the playbook for that request type. While auto-send is being tested, a person gives each one a final check.

Tech stack used
Built with Next.js,
TypeScript,
Firebase,
Gemini AI,
Tailwind CSS, and
shadcn/ui.