Philippines staffing guide · Published
Write a delivery exception script for an outsourced logistics support desk
A delayed parcel and a damaged parcel need different facts and different promises. A written exception script keeps the customer informed without inventing a remedy the client has not approved.

The short answer
Classify the exception, collect the carrier facts, and give the customer a checkpoint the desk can keep. The desk can document and route the case, but the client's claims owner should decide refunds, replacements, and carrier disputes.
Classify the exception before you speak
A delivery exception is easier to handle when the desk names the type before contacting the customer. A delay, a damaged parcel, a wrong address, a lost shipment, and a carrier hold each need different facts and a different next step. Write the categories into the script with one example each.
A coordinator who starts with an apology instead of a category will collect the wrong details. Read the category back to the customer before asking for more.
Use the carrier's own scan and exception code as the first source, not the customer's summary. The scan may say the address is incomplete, while the customer says the driver never arrived. Both can be true, and the script should record both without choosing a culprit.
The desk gathers evidence; the carrier and the client decide responsibility. Write both versions in the note, with the source and time.
Ask for the facts the carrier needs
Most carrier claims stall because the first contact did not capture the order number, the tracking number, the shipping address, and a reachable phone number. Ask for those four items in a fixed order and read them back. Confirm the apartment, suite, or gate code that often causes a failed delivery.
A clean fact set saves a second call. Repeat the facts back so the customer can correct a digit.
For damage, ask for photos of the outer box, the label, the packing material, and the item. Ask whether the customer kept the packaging, because a claim may require it. Record the time the photo was taken and who took it.
Do not promise a refund or a replacement before the client's claim owner reviews the evidence. Say who will review it and when the customer will hear back.
Set the expectation you can keep
Give the customer the next checkpoint, not a guaranteed delivery date the desk cannot control. Say what the carrier's scan shows, what the desk will check, and when the customer will hear back. Avoid phrases like it should arrive tomorrow unless the carrier has confirmed the route.
A missed promise costs more trust than an honest, uncertain interval. A specific checkpoint is easier to keep than a vague promise.
When the carrier gives a new date, repeat it as the carrier's estimate and record the source. If the customer needs the item by a specific date, ask what happens if it arrives late and route that answer to the client. Do not invent compensation to calm the call.
The script should offer only the remedies the client has approved. If the customer asks for more, record the request and route it.
Record the promise and the next check
Every exception note should show what the customer was told, when the desk will check again, and who owns the check. Use a timestamp and a specific action, such as call the carrier or review the scan at noon. A note that says follow up is not a commitment.
The next coordinator should be able to continue without reading the whole thread. Use the same fields in every note so the queue can be searched.
Set the next check before the customer's patience runs out, not at the end of the day. For a delayed parcel, that may be the next scan window; for a lost parcel, it may be the claim acknowledgment. Record the outcome of each check, even when nothing changed.
Silence in the log looks like neglect, even when the desk is waiting on the carrier. A short update is better than no update when nothing has changed.
Hand off claims and damaged goods
A damage or loss claim belongs to the client's claims owner, not the support desk. The handoff should include the order, the tracking, the photos, the customer contact, and a short timeline. State what the customer was promised and what remains open.
A complete, calm handoff is faster than a dramatic one that omits the order number. Attach the photos and the timeline to the handoff.
Keep the customer informed while the claim moves, even if the answer is that the review is still open. Give a new checkpoint at each handoff so the case does not go quiet. Record the claim number and the owner's name.
If the claim is denied, route the decision back to the client before telling the customer. Give the customer the decision and the next step in plain language.
Review exception codes weekly
Count exceptions by type, carrier, destination, and week. A cluster of address failures in one region may point to an autocomplete problem, while a cluster of damage claims may point to packing. Read a sample of notes to confirm the category before changing a process.
The count shows where to look, not what to fix. Read the notes behind the count before drawing a conclusion.
Bring the top two patterns to the client with the evidence and a proposed test. Change one thing at a time and compare the next four weeks. Record whether the rate moved and whether the customer contact changed.
A weekly review that never changes anything is a report, not an improvement cycle for the desk or the client. Name the one change and the date the next review will test it. Keep the test result with the weekly review notes.
Questions to copy for the sales call
- "Which exception type does the carrier scan describe?"
- "What are the order, tracking, address, and callback facts?"
- "What checkpoint did the customer receive, and who owns it?"
- "Does this case belong to the claims owner, and what evidence moved with it?"
Sources
- FTC: Mail, Internet, or Telephone Order Merchandise Rule: Official guidance on shipment timing and customer communication; application depends on the transaction.
- SBA: Manage your business: Small-business guidance on customer service and operational records.
- ISO 9001: Quality management systems: A process-control reference for consistent exception handling.
Common questions
Can the desk promise a replacement parcel?
Only when the client has approved that remedy for the exception type. Otherwise record the request and route it to the claims owner.
What should the desk do when the scan and the customer disagree?
Record both versions and the source of each. Do not decide who is right; gather the evidence the carrier and the client need.
How often should a delayed parcel be checked?
At the next scan window named in the script, then at the committed checkpoint. Record the outcome of each check.
Who owns a damage claim?
The client's claims owner. The desk prepares the evidence and keeps the customer informed while the claim moves.