Prime Day orders are shipping now, so take "where's my order?" off your support team

Prime Day ended on Friday. Over four days, June 23 to 26, US shoppers spent $26.4 billion online, up 9.3% from last year. That figure comes from Adobe, which measures direct online sales across US retail sites as a whole, so it covers far more stores than Amazon.

Those orders are in trucks right now. Over the next ten days, a predictable share of those customers will write in to ask the same question: where is it?

If you sell anything that ships, “where’s my order?” is the support question I would hand to an agent first. The answer already lives in your systems, the question repeats all day, and the rules for answering it can be written on one page. This week, while the post-sale wave is still building, is a good time to set it up.

By the numbers

26.4 billion

US dollars spent online over Prime Day, June 23 to 26

Source: business.adobe.com

Why order status is the right first job

Most support questions need judgment. Order status mostly needs a lookup. A person on your team who answers one of these opens the order system, finds the order, copies the tracking number into the carrier’s site, reads the status and types a reply. None of that requires them. All of it takes their time.

An agent connected to the same two systems can do that in seconds, at 2am, in the customer’s language, on email, chat or text. It doesn’t get bored on the fortieth one of the day, and it never forgets to include the tracking link.

The tools for this are now built into the products small companies already use. Meta’s Business Agent, which went global this month, connects to systems like Shopify and Zendesk so it can act for the business inside WhatsApp, Messenger and Instagram. Most help desks include a resolution agent too, and pricing has moved toward paying per solved conversation. Fin, which Salesforce agreed to buy two weeks ago, charges about 99 cents per resolution and nothing when the agent fails.

Set it up in five steps

Count them first. Pull the last 30 days of tickets and tag every one that is a status question. Note how long each took to close. This is your baseline, and it tells you how many hours are actually on the table. Do it before you turn anything on, because you will not be able to reconstruct it afterward.

Connect read-only. The agent needs to read two things: your order records and the carrier’s tracking data. It does not need to change orders, issue refunds or edit addresses for this job. Give it the narrowest access that answers the question.

Verify before you answer. An order status reply can include a home address and what someone bought. Have the agent confirm the order number plus the email or ZIP code on the order before it shares anything. Write that rule down and test it by trying to get information about an order that isn’t yours.

Write the answer for each status. This is the part most companies skip, and it’s where the quality comes from. List every status a package can be in and write what the agent should say and do for each one.

Send updates before they ask. The cheapest ticket is the one that never gets written. If your store sends a shipping email with tracking and a delay notice when a carrier scan stalls, a share of these questions disappears before the agent sees them.

FlowAn order status request with an agent

01Customer asks
02Agent checks order and ZIP
03Agent reads carrier status
04Answers or hands off
05Person handles exceptions

The agent handles the lookup, and a person gets every case that needs a decision.

The rules for each status

Here is the kind of table I would write. Adjust the wording and the timing to your business.

Label created, no scan yet. Tell the customer the label exists and the carrier has not picked it up. Give the expected ship date. If it has been more than three business days, hand it to a person.
In transit and on time. Share the tracking link and the carrier’s estimated delivery date.
In transit and late. Say plainly that it is running behind, share the latest scan and the new estimate if the carrier has one. Don’t promise a date the carrier hasn’t given.
Delivered, but the customer says it isn’t there. Hand it to a person. This involves a judgment about a reship or a claim, and it is often an upset customer.
Returned to sender or lost. Hand it to a person with the order and tracking history attached.

The pattern is simple. The agent answers when the answer is a fact in a system. A person decides when the answer costs money or needs a judgment call.

Write the tone into the rules as well. A late package is rarely anyone’s fault in the conversation, and customers can tell when a reply is padded. I would tell the agent to acknowledge the delay in one short sentence, give the facts and the next step, and stop. No paragraphs of apology, no “we totally understand your frustration.” Customers want to know where the box is and when it will arrive. A reply that says that in three lines reads as competent, and competent is what calms people down.

Before and after

The agent handles

Tracking link and ETA
Late package updates
Label not yet scanned

A person handles

Delivered but not received
Reships and refunds
Lost or returned parcels

Split the work by whether the answer costs you money.

Measure what it actually took off the team

After two weeks, look at four numbers. What share of status questions did the agent close without a person? How many of those customers wrote back with the same question, which tells you the answer didn’t land? How long did the handed-off ones take to resolve? And how many hours did your team spend on order status compared with your baseline?

Decide in advance what the hours go to. If the agent takes order status off two people’s plates, those people should move to the work that was waiting: the delivered-but-missing cases, the returns backlog, the customers who are about to churn. If nobody decides, the time disappears into the inbox and you will have a hard time saying what the agent was worth.

Read twenty of the agent’s conversations yourself, start to finish. You will spot the phrasing that confuses people and the status the carrier reports in a way you didn’t plan for. Then fix the rules. Every change goes into the one-page table, so the next person who reads it sees the current version.

What to do this week

Tag last month’s tickets and count how many were order status questions.
Write the one-page status table above with your own timing and wording.
Check whether your help desk or store platform already includes an agent that can read orders and tracking.
Turn it on for one channel, such as email, with the verification rule in place.
Assign one person to review the handoffs every day for the first two weeks.