An Order-Status Agent That Knows When to Hand Off

A morning of missing mugs

At 9:10, Katie at Button Basket, a made-up promo supplier, opens an email from Leo at Sprout Street Promotions. He ordered 240 mugs for a customer event. His customer counted 200. Where are the other 40?

Katie's order system says "shipped." One tracking page says "delivered." Another says "Label Created." Three perfectly readable statuses have somehow produced no usable answer.

She could paste the first tracking link and say the order arrived. That would be quick. Leo would still be missing 40 mugs, and Katie would soon be reading his second email.

The people and companies here are made up, but the problem probably isn't. Your customer asks about an order. Your records answer about a carton. Someone has to notice the difference before a helpful reply becomes another thing to fix.

An order-status agent should take the lookup work off Katie's plate. It should find the right order, check the latest records, and answer the questions your team has agreed it can answer. When the facts don't add up, it should give a person a head start, not a cheerful guess.

Find the right order before sharing anything

Leo's email includes a PO number. That's useful, but it isn't the whole check. The tool should match it against his verified customer account, your order number, and the relevant message history.

If two orders fit, it should ask for the smallest missing detail that separates them. It shouldn't send back both shipping addresses and ask which one looks familiar. That's a very efficient way to show someone another customer's business.

Finding an order and being allowed to discuss it are separate questions. Follow your shop's rules for who can receive order information, especially shipping addresses, recipient details, and programs that aren't public. A familiar company name or a copied PO number doesn't settle that by itself.

Once matched, note which order the conversation is about. If Leo later asks about a different PO, the tool needs a new match. Otherwise yesterday's correct answer can become today's wrong-account reply.

Check what the records actually say

Before drafting a reply, pull together the order record, production updates, shipment records, carrier tracking, and any delivery promises your team has approved. Keep the source and check time with each fact.

In Katie's case, the internal order system says "shipped" in an update from yesterday afternoon. A carrier check at 9:18 this morning shows shipment A delivered and shipment B still at "Label Created." Those aren't three ways of saying the same thing.

Keep the difference visible. Don't choose "shipped" because it sounds more reassuring. A record copied yesterday isn't a fresh observation from the warehouse, and a shipping label isn't proof that a carton left it.

UPS explains "Label Created" as receipt of the shipment details and billing information from the sender. UPS says the status updates once it has possession of the shipment and has it moving through its network. That status alone doesn't confirm possession or movement.

Tracking also belongs to a shipment, not automatically to the whole order. Before saying "your order was delivered," account for every expected package and destination. One delivered carton can't speak for a second carton that hasn't shown movement.

The same habit matters earlier in the process. Our post on sales order readiness review covers checking an order before production. Status replies need their own checks against what happened afterward.

Let the tool answer the simple questions

Some questions don't need Katie to investigate. If the customer and order are matched, the requester is allowed to receive the information, and the records agree, the tool can prepare a routine answer.

That might be a verified tracking link with the carrier's current status and the time it was checked. It might explain that artwork approval is still pending, naming the exact proof and what the customer needs to do.

Write down which replies your team allows the tool to send and which need review. "Can look it up" and "can send it to the customer" aren't the same permission.

Keep estimates as estimates. A carrier's estimated arrival isn't a delivery guarantee. A supplier's target production date isn't a promise that the customer's mugs will arrive that day. The tool shouldn't improve either one while making the sentence friendlier.

When there isn't a reliable answer, a clear acknowledgment is useful: "We're checking whether the second shipment has left the warehouse. Katie is handling the follow-up." That tells Leo what's happening without promising a result. It also doesn't mean his case is finished.

Work through the 40 missing mugs

Here is how Katie's case should go. The steps follow the facts instead of treating the word "shipped" as the answer.

1What Leo reported

Leo ordered 240 mugs and reports that his customer received 200. The order record assigns 200 mugs to shipment A and 40 to shipment B. A has a carrier delivery event. B has only a created label.

Keep Leo's report as he gave it. "Customer reports receiving 200" is different from "customer probably missed a carton." The second sentence adds a theory nobody has checked.

2What the records show

There are 40 mugs to account for, and the carrier status doesn't verify possession of shipment B. A record assigning 40 mugs to B doesn't prove someone packed them or handed them to the carrier.

Shipment A's delivery event doesn't settle the whole order. The tool has enough information to identify the gap, but not enough to explain where the missing mugs are.

3What the tool does next

Put Leo's report, the shipment quantities, packing records, tracking events, and check times together for Katie. Ask the warehouse to confirm B's packing and dispatch state under the shop's approved short-shipment procedure.

Agree on that procedure before the tool handles these cases, and ask Leo only for what it calls for, such as carton labels or a packing-list reference. Don't send him on a scavenger hunt for every document the tool can name.

4What it doesn't do

Don't say all 240 mugs arrived. Don't decide that the supplier short-shipped, the carrier lost a carton, or the customer miscounted. And don't promise a replacement, credit, or rush shipment just because those would make a nicer reply.

Keep the case open until the remaining shipment or shortage is established and the person allowed to decide the remedy makes that call.

If B later gets a scan showing carrier possession, refresh the answer using that evidence. If the records instead say all 240 mugs were packed in the delivered cartons, follow the shortage-investigation path. New facts change what needs checking. They don't give the tool permission to assign blame.

Credit, replacement, expedited shipping, and admissions of fault stay with whoever has that authority in your business. The tool can prepare the facts and options. It doesn't get a refund budget because it found a tracking number.

Give the person the facts, not another search job

Forwarding Leo's email with "escalated" would leave Katie doing the same lookup again. A useful handoff includes:

1. The customer's question and any relevant deadline.
2. The verified order match and important identifiers.
3. The facts retrieved, their sources, and when they were checked.
4. Conflicts between records or evidence that's still missing.
5. Actions already taken and messages already sent.
6. The decision or investigation needed next.

For this case, the next question is specific: were the 40 mugs assigned to shipment B packed and dispatched? That's something the warehouse can answer. "Please investigate order" is less helpful.

Keep internal comments separate from the customer draft. A note about a possible packing error isn't an approved explanation. Private financial information and guesses about supplier fault don't belong in Leo's reply either.

The customer draft should contain only facts and commitments approved for that recipient. Someone reviewing it should be able to see where each came from without untangling the internal conversation.

Assign a named owner and a next-check time. Katie might own the case and check the warehouse answer at 11:00. Your shop should set the next-check time to fit the case. What matters is that someone knows when to pick it back up.

If Leo confirms that the event is tomorrow, make that deadline visible. Urgency belongs in the handoff. It doesn't turn into permission to promise the mugs will make it.

Pick back up without sending the same reply twice

A new tracking event, a warehouse answer, or a reply from Leo should trigger the relevant checks again. Reread what changed and anything it affects before drafting the next update.

If UPS now shows possession of B, don't repeat the earlier "Label Created" answer. Check the current shipment record and tracking status, then explain the change. If the warehouse answer conflicts with tracking, keep that conflict visible rather than quietly dropping one side.

Two systems may report the same event. That shouldn't produce two customer emails. Check what has already been sent, record the approved reply and its delivery result, and attach later messages to the same case.

If a send has an uncertain result, check the communication record before trying again. Leo needs an answer about mugs, not three copies of an answer because a screen timed out.

Close the case only when the requested information has been provided or the issue reaches your business's defined resolution state. A simple tracking question can finish with an accurate answer. A disputed shortage or a promised follow-up stays open. "Handed to Katie" isn't a resolution for Leo.

Check whether the answers are any good

Counting replies sent is easy. It won't tell you whether customers got the right answers.

Look for wrong order matches, replies based on old records, handoffs that weren't needed, handoffs that were missed, customers who had to write twice, and how long cases take to actually finish. Check some of the ordinary answers too, because a wrong reply nobody flagged won't show up in a list of exceptions.

Start testing with real ticket examples and your current short-shipment procedure, with private details removed. Include cases where the records disagree, where several orders match, and where someone asks for a remedy the tool can't approve.

Compare the work saved with the cost of checking and fixing replies. Our guide on measuring AI workflow cost and ROI walks through that comparison. Fewer loose ends matters more than a bigger automated-reply count.

Order-status checklist

• The order is matched to the right account and requester.
• The requester is allowed to receive the information in the reply.
• Each fact keeps its source and check time.
• Conflicting records stay visible until they're explained.
• Every expected shipment and destination is accounted for before calling the order delivered.
• Estimates remain estimates, and remedies need the right approval.
• Internal comments stay separate from the customer draft.
• Each handoff has the six facts above, a named owner, and a next-check time.
• New information triggers a fresh check without duplicate updates.
• Shortages and promised follow-ups stay open until the agreed resolution.

Frequently asked questions

1Does UPS "Label Created" mean the package has shipped?

It doesn't confirm that UPS has the package. UPS says it has received shipment details and billing information. The status updates once UPS has possession and the shipment is moving through its network.

2Can an order-status agent answer customers without review?

Only for the replies your team has approved for automatic sending. It still needs the correct order, an authorized requester, and current facts that support the answer. Anything outside those rules remains a draft or goes to a person.

3What should it do when a customer reports missing items?

Keep the customer's report intact, compare the ordered and shipment quantities, check packing and tracking records, and hand the gap to the right person. A shipment record alone doesn't prove the missing items were packed or received.

4Can it offer a credit or send replacements?

Not without the business authority for that remedy. It can collect the evidence and prepare options, but finding a shortage doesn't authorize spending money or admitting fault.

5When is an order-status case finished?

When the requested information is provided or the issue reaches the resolution state your business has defined. Sending a tracking link doesn't close a disputed shortage. Handing off doesn't close a promised follow-up.

Where Trelium fits

Order lookup and customer-service handoffs fit alongside Trelium's order workflow use cases. Start with the questions your team already answers the same way every time. Write down which records to check, what the tool may send, who handles the messy cases, and how work picks back up. The useful part isn't answering everything. It's answering the simple things accurately and leaving the right person ready to handle the rest.