Guide
AI for customer, supplier and operational email
The hardest customer and supplier emails are not hard because they need a polished reply. They are hard because the detail that decides the outcome is buried in a long thread, written in another language, or sitting in an attachment somebody now has to interpret. Kerna handles that part, inside Gmail and Microsoft Outlook.
Last reviewed .
Definition
The challenge is comprehension, not replying
An operational email can carry a commercial decision, a delivery consequence or a customer expectation. Before anyone can answer it, the work has four parts.
- Understanding the whole conversation rather than only the latest message in it.
- Identifying what changed, and which of those changes still matters now.
- Finding and using the details inside whatever document came attached.
- Preparing a clear response that the person answerable for it can check before it goes.
The problem
Why these threads take so long
On an operational inbox, writing the reply is the last step. Three things ahead of it are what actually consume the afternoon.
The answer is somewhere in the middle of the thread
An original request, a clarification, a revised price, an amended quantity and a final question, separated by days. The newest message is rarely the whole picture, and reconstructing the rest by scrolling is how an hour disappears.
The language changes partway down
A conversation can move between a customer, a colleague and a logistics partner in three languages. Reading it quickly enough to act on it, and checking the commercial detail rather than taking it on trust, is a real constraint rather than an edge case.
The numbers are in the document, not the message
A revised order, an invoice, a specification. Someone opens the file, finds the fields, and types them somewhere else — every time the work moves between people.
What it takes
The same pattern, across the business
The example works just as well starting from a supplier: a revised date, a partial delivery, a document with updated details. The inbox holds the context, the change and the file, and somebody has to turn them into a clear next step. That is true in more places than most teams expect.
Customer service
Understand a complaint or request in its full context before replying, so the answer addresses what actually happened rather than the last two lines of it.
Sales and account management
Track commercial changes through a long conversation and prepare considered responses, without losing what was agreed three weeks ago.
Purchasing and supply chain
Assess supplier updates and the documents attached to them, and move the relevant detail into whatever comes next.
Operations and order management
Spot the changes that need following up, and get the information ready for the process that handles them.
Finance and accounts receivable
Organise invoice correspondence and pull the relevant fields out of attachments instead of rekeying them.
International and export teams
Kerna reads, summarises, translates and drafts across 45 languages, handled per language rather than passed through a single translation step. On a thread that switches language partway down, that is the difference between workable and not.
Worked example
A worked example: a changed customer order
An order has been in progress for two weeks. The thread covers packaging questions, a quantity change and a delivery-date discussion, with a revised document on the latest message. Today the customer writes: "Please proceed with the revised quantity and confirm the earliest possible delivery." A colleague who was not part of the original conversation picks it up. Here is what they do with Kerna.
- 1
Summarise the thread
One action in the side panel returns the original request, the amendments since, and the question being asked today — without scrolling back through two weeks of replies. Three depths are available, from a quick orientation to a fuller account you can check against the thread.
- 2
Categorise the email
It shows up as the kind of work it is — an order change, a customer request — against the categories this team chose, rather than a generic priority label. What belongs together becomes visible, and so does what is waiting.
- 3
Extract the attachment
Kerna reads the revised document and returns the reference, quantities, dates and line items as named fields, exported to a spreadsheet. The colleague checks the numbers against the thread instead of transcribing them.
- 4
Prepare the reply
A draft confirming what can be confirmed, or asking the one follow-up question that is genuinely open — in the tone and intent chosen for this customer, in their language if that is not yours. It waits in the compose window until the colleague is satisfied with it.
Kerna
The judgement stays where it belongs
No assistant should decide whether a revised delivery date is acceptable, whether a customer request changes the commercial position, or how a dispute gets resolved. Those are business decisions. Kerna is built for the work leading up to them, and stops there deliberately.
- Kerna prepares: thread summaries, categories, extracted fields, draft replies.
- You decide what the thread means for the business and what can be promised.
- Kerna does not send mail. Every message leaves because a person sent it.
- There is no separate console and no mailbox migration. You work in the Gmail or Outlook you already use, and Kerna acts only on the message you point it at, when you ask.
- Content is processed to answer that request: the application runs on Cloud Run in Belgium with Firestore in Poland, personal data is redacted before anything reaches the model, and nothing is retained afterwards.
Questions
Questions people ask
- Can Kerna help with long email threads?
- Yes. Kerna summarises a thread at three depths so you can establish the context and the current position without reading it end to end — which is what makes picking up somebody else’s conversation practical.
- Can it work with attached documents?
- Yes. Kerna extracts named fields from PDF, DOC and XLS attachments using a hundred presets across twenty industries, plus custom fields you add, and exports them to Sheets or Docs in Gmail and Excel, Word or CSV in Outlook.
- Can Kerna draft a reply in another language?
- Yes. Kerna translates and drafts across 45 languages. You choose the language, tone and intent, review the wording, and send it when it is right for the situation.
- Will Kerna make commitments to customers or suppliers?
- No. Kerna prepares drafts for review. Your team keeps control of the commercial decision and of every outgoing email, and Kerna does not send mail itself.
- How quickly can a team start?
- Kerna installs into Gmail or Outlook from the marketplace in a couple of minutes. Starter is €0 and includes every feature, with a token allowance, so you can run it against real mail before paying for anything. There is no data migration and no process to redesign first.
- Is this only for export managers?
- No. International sales and export teams feel it most sharply, but this page describes anyone whose important work arrives through customer, supplier and operational email — including teams who never send a message abroad.
Read next
Where to go from here
Operational inbox management
The category this page makes concrete.
Before your ERP or CRM
Where the work sits relative to your system of record.
Getting data out of attachments
Presets, custom fields and the four export targets.
Build or buy
If writing it yourself is on the table.
Kerna in Gmail
The same work, on the Google side.
Kerna in Outlook
The same work, on the Microsoft side.
Start from clarity, not guesswork
Install Kerna on the inbox you already use and run it against the next order change that lands with a document on it. Starter is €0 and includes every feature, with a trial token allowance to run them on — one real thread tells you more than any demonstration.