Customer service

Answer the order-status question once, properly

Most service teams answer the same question several thousand times a month. That is the first thing to hand over, and the easiest to measure.

Written by

Founder desk, Agentic Global

Updated

28 July 2026

Reading time

6 minutes

Setting
A 40-person logistics firm, one shared inbox, two service staff
Freed to
spend the day on the twelve conversations that decide whether a customer stays

Agents observed doing this work

Intercom Fin · Zendesk AI agents · Salesforce Agentforce

Named for reference only. Capability data is held separately in the registry and sourced from vendors and public material, with provenance on every field.

Open the registry

The situation

Two people were spending most of each morning pasting tracking links. Neither of them had been hired to do that, and both of them knew it. The queue that actually mattered — damaged deliveries, invoicing disputes, the customer thinking of leaving — was reached at about two in the afternoon, tired.

The task is narrow, high-volume, and has one correct answer that already exists in a system. That combination is the strongest signal that an agent can carry it.

What we did

We gave the agent read access to the order system and nothing else. It answers three intents: where is my order, has it shipped, and what is the return window. Everything else — every single thing — is handed to a person with the conversation intact.

We wrote the fallback sentence before we wrote anything else: “I am an assistant and I cannot answer this one. I am passing you to Marta, who can.” That sentence is the product. The rest is plumbing.

What changed

Volume into the human queue fell by roughly half within a month. The number that mattered more: first-touch on a complaint moved from four hours to under thirty minutes, because the morning was no longer spent on tracking links.

Nobody lost a job. One of the two moved to account retention, which is the only version of this story worth repeating.

What to watch for

  • A confident wrong answer costs more than a slow right one — set the confidence threshold high and check it monthly.
  • Tell people they are speaking to an AI system. In the EU this is not a courtesy, it is required.
  • Deflection targets set without a quality floor will produce both.