Console loginCall

Order lifecycle · 5 entries

The parts of an order nobody should automate

An order is easy in the middle and hard at both ends. The interesting moments are the ones that cannot be undone, the ones where somebody is upset, and the ones where a cheerful automated reply does more damage than no reply at all. What an agent does at those five points tells you more about it than anything it does when things are going well.

What does the AI escalate to a human instead of handling?

Anything irreversible or emotional: a cancellation, a return, a complaint, an angry message. Those go to a person immediately with the order and the conversation attached — not into a clarifying loop, and not into a reassurance the agent has no authority to give.

Judge an agent on what it refuses at nine at night.

Always a person3

Three moments where speed is worth less than judgement

uc-023

“Cancel my order”

— three words, and no way back once they are acted on

Order cancel kar do

“Cancel my order.”

UC-023HINDINAGPURPALANQUIN

What you'll observe

It does not cancel. The request goes to a person with the order's current state attached, because a cancellation acted on after despatch is a truck already moving and stock already committed.

The temptation here is that cancellation is easy to implement and feels like good service. It is the single clearest case where being able to do something is not a reason to.

uc-022

An angry message at nine at night

— the tone is the content, and it is not a query

What you'll observe

Straight to a person, with no cheerful acknowledgement in front of it. An automated reassurance to somebody who is already angry is the message that turns a complaint into a lost customer.

There is no clarifying question here either. Asking an upset person to rephrase is the second-worst thing available.

uc-021

A return request, with a photo of the damage

— a claim about goods and money, arriving as an image

What you'll observe

The photograph and the order go to a person together. Whether a return is accepted is a commercial decision about evidence, and the agent's job is to make sure the person deciding has both halves in front of them.

Where a person is already behind it2

Two cases that look automated and are not

uc-020

A payment reminder somebody approved

— a reminder, not a dunning loop that runs on its own

What you'll observe

It goes out because a person decided this buyer should be reminded, and it stops when they reply. Nothing escalates on a schedule, and no second message is sent because the first was not answered by Tuesday.

uc-125

A POS terminal, answering while the customer waits

— the counter staff are mid-transaction and cannot go and look

What you'll observe

The question is answered at the counter in the seconds available, from the same catalog and stock as everywhere else. The person serving stays the person deciding.

Part of

Questions people ask before they try it

Why not let it cancel an order if the buyer clearly wants to?

Because the buyer's clarity is not the issue — the state of the order is. A cancellation after despatch means a vehicle in motion, stock already allocated and possibly an invoice raised, and none of that is visible in the sentence asking for it. A person takes two minutes and gets it right.

Does escalating everything difficult make it slow?

It makes a small number of things slower and the rest faster, which is the trade you want. The questions that make up most of a day — stock, rate, status, GST — are answered immediately; what gets queued is the handful where being wrong is expensive.

Can it chase payments automatically?

It carries a reminder a person approved and records what comes back. It does not run an escalating sequence on its own, because an autonomous dunning bot damages relationships faster than it recovers money, and it does it to your best customers as readily as your worst.

Test it, don't take it from us

Ask it: “Cancel my order”

You're talking to the product. Nothing you send is added to any business's catalog.