WhatsApp customer complaints: 4 steps
Managing customer complaints on WhatsApp means your system logs and acknowledges each complaint within minutes but never settles it alone. Four steps: log it with a number and a time and name who follows up; match it to the order and proof of delivery; let a named person decide within their limit; and close only when the customer confirms the fix. This follows the delivery notification checks: the order arrived, and now the customer reports a problem.
Why delivery and complaint times matter
Article 340 of the Saudi Civil Transactions Law requires a buyer to check goods on receipt as soon as they can, as is customary, and to report a defect to the seller within a reasonable time, or be deemed to accept it. Article 339 excludes defects arising after delivery unless an earlier cause lies behind them. Article 338 lets the seller avoid cancellation or a price-difference claim with a similar, sound substitute, so replacement comes first. Under Article 344, a defect claim is not heard 180 days after delivery unless the seller guaranteed longer. Keep the delivery condition and complaint time that long at least; disputes go to your legal adviser.
A case from the floor
Illustrative example: the same food supplier serving 120 restaurants got 9 WhatsApp complaints in a week, and the system settled none of them alone.
Five had the shortage or damage already in the proof of delivery, so the rep sent replacements with the next delivery. Two were delays; the rep checked the trip record and called. One was damage not recorded at delivery, which went to the sales manager with photos. One was an item near expiry: the system told the restaurant not to use it and alerted the owner.
Four steps for every complaint
- Log and acknowledge. Complaint number, linked order, arrival time, photos. The first reply confirms receipt and says who follows up and by when, promising nothing and admitting no fault before checking.
- Match it to the order and delivery. Staff see what was ordered and loaded, who received it and when, any damage recorded at receipt, and the delay before the complaint. Recorded damage is confirmed at once; the rest needs checking.
- A named person decides, within a limit. A promise of compensation commits you to what nobody approved: one of the cases where the system must stop and ask. The rep approves replacements up to a written limit; above it, the sales manager or owner. Outcomes: a like-for-like replacement, deducting the defective part's value from the customer's account, or a reasoned refusal with evidence, sent in writing only once approved.
- Close on confirmation, record the cause. A complaint closes when the customer confirms the fix arrived. No reply in 48 hours: the system asks once, then closes it as "unconfirmed". Each gets a cause (loading, transport, warehouse, delay); review the most frequent monthly.
What the system does in each case
| Case | What the system does |
|---|---|
| Damage recorded at delivery | Confirms it; the rep sends a replacement |
| Damage not recorded at delivery | Sends photos and proof to the decision-maker; promises nothing |
| Late past the window | Shows the rep the trip record to call the customer |
| Possible food-safety issue | Asks the customer not to use the item; alerts the owner |
| Third complaint from one customer in a month | Escalates to the owner with the history |
| No reply to the confirmation request | Asks once after 48 hours, then closes as "unconfirmed" |
The conversation as it happens
Wednesday afternoon, the restaurant's receiver writes:
Customer: Order 2231 came today with 3 cartons of oil broken. (photo)
System: Complaint 417 logged at 4:10 pm. Faisal from sales will reply before 6 pm.
An hour later the owner asks:
Owner: How many complaints today?
System: Three. Two closed, confirmed by the customer after replacements arrived. The third needs you: 3 broken cartons in order 2231, damage not recorded at delivery, above the rep's limit. Send the photos and proof?
Owner: Replace them with tomorrow's delivery.
System: Recorded, and the customer is told. I will check after delivery that it is solved.
That is what running the business from WhatsApp adds: complaint, order, proof and decision in one record.
Checklist before automating replies
- Every complaint has a number, a time and an order?
- The first reply names who follows up and when, and promises nothing?
- Proof of delivery shows alongside the complaint?
- Each person's limit is written down?
- Complaints close only on confirmation or after one unanswered follow-up?