B2B customer service: one address per customer, a record the company owns

B2B customer service runs on relationships: one account manager, a few hundred customers, and years of email between them. That is also its weak point, because the relationship lives in a mailbox the company cannot open. This is the system we built at Hellomatik to keep the customer's record without taking email away from anyone: AI agents that read each message, build the case file and draft the reply, each inside a limit a person sets.

Where a customer's history used to live

The company this was built for sells through account managers, and its customer record was never in the CRM. It lived in the inbox of whoever handled that customer, and nowhere else. That works while nothing changes.

Then the manager is out sick for a week. Or leaves. Or the customer is moved to somebody else. The new manager inherits a name and a phone number, and none of the months of email that explain them.

B2B customer support: one address per customer, always to its owner

Every customer gets their own support address and writes to it the way they used to write to a person. What arrives there is captured before anyone reads it. The system identifies the customer, tags the message with a subject (the category it belongs to: a delivery query, an invoice question, a return) and routes it to the manager who owns that account. A case is one incoming message and everything attached to it. The manager still answers their customers.

A customer service AI agent, here, is a program that reads a message, decides what to do and acts on it, inside a limit a person has set. Several of them work on each case. The whole thing runs on our platform and is connected, company by company, to their mailbox, their ERP and their warehouse system.

Ownership can move without the history moving. If a manager is out, their customers' cases route to whoever covers them, with everything attached. If a customer is reassigned, the new manager opens the record and finds every message since the address went live. The record starts the day the address goes live; whether older email from personal inboxes is imported is outside this text.

Every message is tracked from arrival to reply, and every case is tagged. For the first time the company can see what its customers write about, and to whom.

What the AI agent prepares before the manager opens the case

When a manager opens a case, the case file is already built.

Four things wait in it. The first is a summary. The system has read every thread with that customer since the address went live, however many people wrote them. It compresses them into what was asked before, what was promised and what is still open.

The second is the order. The case file is built from live queries to the warehouse and the ERP: order status, dispatch time, the carrier's forecast. In the example on the screen above, the customer writes that order 4471 was due yesterday and has not arrived. The manager sees that it left the warehouse yesterday at 4:40 p.m., and that the carrier now expects it today. There is nothing to look up.

The third is the visit notes the manager wrote after the last meeting with them. That is how the draft knows this customer wants a single delivery day per week. The fourth is the draft reply itself, and that one gets its own section.

The AI model never supplies a figure of its own: every number in the case file comes from those queries. What the draft promises is a commitment, and a person approves it. If a system cannot be reached, the file says so rather than showing yesterday's status as today's.

Three autonomy levels and two overrides decide who sends the reply

The draft reply is written from that file. In the example above, that is why it opens by admitting the order is late and says the carrier expects it today. It then commits to confirming the delivery slot before noon. The manager can send it, change it or throw it away.

How much the system does on its own depends on the subject: a three-level ladder per subject, plus two overrides. At suggested draft, the agent writes and the manager edits and sends. At reviewed reply, the agent writes and the manager approves it as it is. At verified autonomous, the agent sends on its own, within the subjects a person has approved for it.

A level rises only by explicit approval. A subject is not promoted automatically after a run of good weeks. And a level falls on its own when quality drops, without anyone having to notice first. With automatic promotion, a system ends up sending something nobody agreed it could send. With automatic demotion, it stops before somebody files a complaint.

The delay is detected before the customer asks

Here the company finds the problem with a delivery and writes to the customer before the customer has to ask. In this system that is one concrete thing: a delay is detected against the carrier's tracking, and the manager writes first.

One more agent does that work after the reply is sent. It reads the dated promises inside outgoing replies, "it ships tomorrow" or "you will have it before Friday." When a shipment slips, it warns the manager who owns that customer.

The notes from every visit go into the record too

What is said in a visit or a call used to live in the manager's head. After a meeting, the manager writes three lines of visit notes into the customer's record: what was discussed, what matters to them, what was agreed. The system stores them against the customer, and from then on the summary includes them and the next draft reply knows them.

What the manager gets out of it

The manager stops looking up the order in the ERP every time somebody asks about it. They can also take a vacation: whoever covers them sees the whole history.

That is the difference between a shared inbox and a record. A shared inbox holds messages. The record holds the customer: what they bought, what they were promised, what they said across a table. And it holds it for the company, not for whoever happened to be in the room.

What this system does not do, and what we cannot prove yet

We have no customer figures for this system. It is running, and everything above describes what it does today. None of it says how much it saved anyone. When there is a month of real activity we will publish it with its numbers, as we did for the warehouse watched in real time.

A wrong classification is not caught later. The subject is decided once, when the message arrives. The quality checks that move a level look at the replies, not at that first decision.

It does not know what it was not told to watch. The promises it verifies are the ones it knows how to detect. A promise phrased in a way nobody anticipated produces no alert at all.

This text does not say where your customers' data is processed or what is kept. The emails carry orders and amounts. That question will be asked of you the moment you propose this. The answer goes in writing before anything connects, and it is not here.

If one person still keeps up with your mailbox and no customer ever changes hands, this is machinery you would be paying to maintain. It pays in three cases: when the volume is past one person, when answers need the warehouse or the ERP, and when customers outlive the manager who first handled them.

FAQ

What happens when an account manager leaves or is out?

Cases from the absent manager's customers route to whoever covers them, with the whole record attached: every thread, every order, every visit note. Since the address went live, nothing lives only in the inbox of the person who left.

Does the customer have to change how they write to us?

No. Each customer gets a support address of their own and keeps writing as before. Replies come from the same people, and for a short list of approved subjects the system sends on its own. What changes is that the company keeps the record.

Does it connect to my ERP and my warehouse?

The support system connects to the ERP and the warehouse system, and the case file is built from those queries: order status, dispatch time, the carrier's forecast. Which systems you have is the first question of the conversation. Connecting them is implementation work, and it is the work we do first.

Does the system send replies on its own?

Only for subjects a person has approved at verified autonomous, the highest of the three autonomy levels. Every other subject sits lower, where the agent drafts and the manager approves. An angry message or a legal mention always escalates to a person.

When does a person step in?

Two ways. By level: for every subject except the ones approved as verified autonomous, a person edits or approves the reply before it goes out. By override: if the customer's message is angry or mentions a lawyer, a claim or anything legal, the case goes to a person whatever the level, and that check runs when the message is classified, before any reply exists.

What is B2B customer service, and how is it different from B2C?

B2B customer service is the support a company gives to business customers who buy repeatedly, usually through an account manager. In B2C each message comes from a person who may never write again; in B2B one manager owns a few hundred customers, each message is about an order, an invoice or a delivery that lives in the ERP, and the relationship lasts for years. The record has to outlive the person: that is why this system gives every customer their own support address and keeps the case file with the company.

Which B2B customer service best practices does this system rely on?

Five, and the system described here applies all five: one owner per customer, so nobody has to ask who handles an account; a customer record owned by the company, not by an inbox; replies written with the order's live status from the ERP, not from memory; escalation to a person whenever the tone is negative or anything legal appears; and follow-up on the dated promises it can detect in sent replies, until the shipment is delivered.

When does the manager hear about a delayed shipment?

Before the customer claims. An agent reads the dated promises in sent replies, checks them against the carrier's tracking and warns the account manager when a shipment slips, so the manager writes first.

What does the manager have to do after a meeting?

Write three lines of visit notes into the customer's record. The case summary and the next draft reply pick them up from there.

What do you need from me to set it up?

Access to the mailbox, the ERP and the warehouse system, and one person who decides, per message category, which autonomy level replies may use and when a category moves up.

What does it cost?

It depends on what has to be connected, not on the method. It is quoted case by case after seeing your systems and your mailbox volume, and before that we do not give a figure we could not stand behind.

Where this comes from

1. 1.The support system described here, read from the product in September 2026: the per-customer address, the assignment to the manager, the case file, the three autonomy levels, the visit notes and the commitment watch. Internal, without customer figures. ↩
2. 2.How an agent of ours is allowed to read, alert and execute ↗ ↩