“Delivered” is a carrier event, not a final answer. When the parcel is missing, open an investigation with one owner, not another tracking line.
Keep four things separate: the customer’s report, carrier record, investigation and remedy decision. That keeps the next message honest when the answer is unknown.
Acknowledge the gap before asking for evidence
Start with what both sides know: tracking shows delivered and the customer cannot locate the parcel. Confirm the shipment reference and the safest way to continue. Avoid asking the customer to prove a negative.
The earlier delivery address workflow may cross dispatch, carrier and merchant teams. The customer should still see one case owner. A first reply can say: “I can see the delivered scan, and I understand the parcel is not with you. I’ll check the delivery record and update you by 15:00 tomorrow.”
Record two accounts without choosing a winner
The customer report and carrier event are evidence from different sources. Neither should silently overwrite the other.
| Record | Keep | Check next | Do not conclude |
|---|---|---|---|
| Customer report | What is missing, when it was noticed and a safe contact route | Household, reception or agreed safe place when relevant | The customer is mistaken |
| Carrier event | Tracking status, delivery time and available delivery record | Address match, service type and carrier investigation route | The parcel reached the customer |
| Investigation | Checks requested, owner and next update time | Responses, conflicts and missing evidence | Silence confirms delivery |
| Outcome | Decision, reason and action promised | Completion and customer notification | Every case gets the same remedy |
A shared inbox can keep the conversation, assignment and private notes together. Record only what the case needs. Do not copy a full address or identity document into general notes when a restricted reference is enough.
Check the delivery record in a fixed order
Use the same sequence so urgent language does not change the standard. Confirm the reference and address match. Check whether the service involved a doorstep, reception, locker, safe place or signature. Ask the carrier for the evidence available under that service and record the expected response time.
The Stripe product-not-received evidence guide asks merchants to include delivery notifications, a photo or signature when available and only relevant shipping details. Its list is non-exhaustive bank-dispute guidance, not a finding that the customer received the parcel or an automatic service remedy.
The related damaged-product workflow also checks whether the merchant has a separate loss, replacement or dispute process. This article does not decide liability or replace local consumer rules.
Give the investigation one owner and a clock
Assign one person or queue to coordinate the carrier, fulfilment team and customer update. The owner must know what is outstanding.
Create a contact or case record with a state such as reported, carrier check open, review, decision made or action completed. Keep a decision separate from a completed remedy.
Set the next update before ending each message. If nothing has changed, say that the carrier response is still pending and give a new time.
Use automation for reminders, not verdicts
Workflow automation can flag a due response, stop duplicate follow-ups or route an overdue case. It should not decide fraud, liability or the remedy from a delivered scan.
Before activating a rule, test a late reply, corrected address, duplicate message, recovered parcel, replacement, declined claim and stop request. Keep a human route visible.
If updates continue in a WhatsApp conversation, identify the business and keep the purpose clear. WhatsApp’s Business Messaging Policy requires accurate, non-misleading communication, respect for stop requests and a clear escalation path when automation is used. Approved templates outside the customer-service window do not make an unsupported outcome true.
Close the case only after the action is verified
Possible outcomes include locating the parcel, opening a carrier claim, replacing or refunding under policy, declining with an explanation or referring the case for review. Do not present one outcome as automatic.
Before closing, record the decision, what the customer was told and whether the promised action completed. Then remove pending reminders. A tidy status is not a completed remedy.
Frequently Asked Questions
Does a delivered scan prove the customer received the parcel?
Not by itself. It is one carrier event to compare with the service, address, available delivery evidence and the customer’s report. Follow the relevant carrier and merchant process.
What should the first reply say?
Acknowledge the mismatch, confirm the shipment reference, name the case owner and promise a realistic next update time. Do not accuse the customer or promise a remedy before review.
Should we ask for a police report or identity document?
Only when the applicable process genuinely requires it. Explain why, use a secure route and collect the minimum needed. Do not make sensitive documents a casual first step.
What should the team measure?
Track time to ownership, investigations updated when promised, duplicate contacts avoided, decisions explained and remedies completed. Keep those measures separate from the carrier’s delivered-event rate.
Want help applying this guide?Ask the DripTell team
From reading to action
Want help applying this to your business?
Share your details. We will read the article you are on and start with a useful answer for your team.
DripTell Editorial
Practical guidance reviewed by the DripTell product and customer workflow team.
See how DripTell checks product claims, uses primary sources and handles corrections.
Editorial and source policy
