Order status and returns
This playbook covers two customer service workflows that share a desk and stop at different places on the autonomy ladder: answering order-status questions and processing returns. It describes the work today, what our forward-deployed engineers build and who does what at each level.
The work today
Section titled “The work today”Order-status questions
Section titled “Order-status questions”Customers email and call to ask where an order is, when it will ship or what the tracking number is. The customer service rep looks in the ERP for the order and on the carrier’s tracking page for the shipment. If the order has not shipped, the rep calls the warehouse or the scheduler. Then the rep replies.
- The answer is in three places, and one of them is a person who is busy.
- The ERP says the order is open and nothing more.
- The same customer asks again two days later.
- Status questions fill the phone queue while orders wait to be entered.
Returns
Section titled “Returns”A customer wants to send something back. The wrong item shipped, it arrived damaged, it is defective or they ordered the wrong thing. The rep checks the order and invoice against the return policy: the return window, the restocking fee and the items that cannot come back, such as material cut to length. The rep issues a return authorization number, often tracked in a spreadsheet. The goods arrive at the dock and receiving inspects them. Someone decides whether to restock, scrap or send them back to the supplier, and accounting issues the credit.
- Goods arrive with no return number on the box, and sit.
- The credit is issued late, or before anyone has seen the goods.
- One rep applies the restocking fee and another waives it.
- Return reasons are not recorded, so the same picking error keeps happening.
- The claim against the supplier or the carrier is never filed.
Who touches it
Section titled “Who touches it”The work touches customer service, shipping, the scheduler, receiving, quality, accounting for credits and purchasing for supplier returns. The workflow owner is typically the customer service manager.
What gets built in the operations layer
Section titled “What gets built in the operations layer”- Screens: one view for each order that brings together its lines, pick and ship status, the tracking number, the scheduled date for anything not yet made and the supplier’s date for anything back-ordered. A return view that shows the request beside the original order and invoice, with the policy checks marked.
- Queues: status questions from the customer service inbox, matched to a customer and an order. Return requests. Returns waiting for goods, for inspection and for credit.
- Rules: who may be told what. Order details go only to contacts on the account, and only confirmed dates are quoted. The return policy, written down: the window, the restocking fee, non-returnable items and who approves a return outside policy. A credit follows the inspected goods, not the request.
- Integrations: reads of orders, shipments, invoices and schedule dates. Write-backs: create the return authorization and, after approval, the credit memo, through interfaces the ERP supports.
Phone calls stay with your reps. What changes for a call is that the answer is on one screen while the customer is still on the line.
The path up the ladder
Section titled “The path up the ladder”| Level | What the agent does | What people do |
|---|---|---|
| Level 0 (Recorded) | Nothing yet. | Reps log each status question with its answer, and each return request with its reason, on a screen instead of in a mailbox and a spreadsheet. |
| Level 1 (Assisted) | Reads the question, finds the order and drafts the reply with the status and the tracking number. For a return, summarizes the request and checks the original order and invoice against the policy. | The rep checks the draft and sends the reply. The rep issues the return authorization. |
| Level 2 (Prepared) | Prepares the complete reply. Prepares the return authorization and, once receiving has recorded the inspection, the credit memo. | A rep approves every reply and every authorization. Accounting approves every credit. |
| Level 3 (Supervised) | Answers status emails on its own when the order has shipped or has a confirmed date and the sender is a contact on the account. Issues return authorizations that are inside policy and under an amount limit. | Reps handle late orders, missing dates, complaints and returns outside policy. People inspect returned goods and approve every credit. |
| Level 4 (Autonomous) | Owns order-status replies by email. | Customer service sets the rules for what may be said and reviews a sample. |
How far this workflow should go
Section titled “How far this workflow should go”The two workflows have different ceilings.
- Order-status replies by email can reach Level 4. The agent reports facts your systems already hold, quotes only confirmed dates and passes anything late or unclear to a person. That bounds what a wrong answer can cost.
- Returns should stop at Level 3, for authorizations inside policy. Credits stay behind a person’s approval for good. A credit is money leaving, and it should follow goods that someone has seen.
- Receiving, inspecting and deciding what to do with returned goods is physical work and stays with people.
- A complaint is not a status question. Anything that reads like one goes to a rep at every level.
When the agent replies to a customer by email, it sends from an address your IT team sets up for this workflow, under a name and signature the workflow owner decides.
Common exceptions
Section titled “Common exceptions”| Exception | Who it usually goes to |
|---|---|
| The order is late or has no confirmed date | Rep, with the scheduler or the warehouse |
| The customer asks to change or cancel the order in the same email | Order desk |
| The sender is not a contact on the account | Rep |
| Tracking shows a problem: damaged, lost or refused | Rep, with shipping |
| A complaint, or a customer asking for the third time | Rep or the customer service manager |
| A return outside the window, or for a non-returnable item | Customer service manager |
| Goods arrive with no return number, or do not match the authorization | Receiving, then the rep |
| A defect claim that needs inspection or lot tracing | Quality |
What to measure
Section titled “What to measure”- Status questions per day, by email and by phone, by customer and by what was asked.
- Time from a question arriving to its answer.
- How many email questions are answered with no rep involved.
- Repeat questions about the same order.
- Returns by reason, item and customer.
- Time from return request to authorization, and from goods received to credit issued.
- Credits issued outside policy, and who approved them.
- Claims opened against suppliers and carriers, and how they ended.
These are things to measure, not targets. The threshold for each level is set with the workflow owner and written down before that level starts.