A confirmation call is the last human conversation before a parcel leaves the warehouse. If it goes well, the customer is ready, the address is right and the courier delivers on the first attempt. If it goes badly — a wrong size, an unclear address, a customer who felt pressured — you pay for it twice: once in the failed delivery and once in the return.
Yet in many COD confirmation centers across Morocco, Egypt, Saudi Arabia, the UAE and the wider region, nobody can actually hear what happened on those calls. Supervisors rely on what agents report, merchants rely on what supervisors say, and disputes are settled by whoever argues best.
Call recording changes that. This guide explains how to use call recording for quality control (QC) and dispute resolution in an order-confirmation team: what to record, how to sample, what to score, how to coach, how to handle privacy and legal notice in MENA markets, and how to connect recordings to the orders they belong to.
Why recordings matter more in confirmation than in most call centers
Confirmation calls are short and repetitive, which makes them easy to underestimate. But they carry three kinds of risk:
- Commercial risk. The merchant pays for every failed delivery and every return. A confirmation that "sounded fine" but missed the size or the delivery day creates both.
- Relationship risk. If you confirm on behalf of several merchants — as a call-center agency or as a courier offering confirmation — each merchant will eventually dispute a cancellation or a "customer never ordered" status. Without a recording, it is your word against theirs.
- Customer trust risk. A first-time COD buyer who is talked into confirming an order they did not really want is likely to refuse at the door — and to stop buying.
A recording linked to the order solves the factual question in seconds: what was actually said.
What to record and how to link it
The minimum useful setup is:
- Record every connected confirmation call, not only some agents or some days. Selective recording creates blind spots exactly where problems happen.
- Link the recording to the order (parcel) and to the agent. A recording you cannot find from the order screen is almost useless during a dispute.
- Keep the status and notes next to the recording. The QC reviewer should see "cancelled — customer says price too high" while listening.
In Speedliv, calls can be recorded and attached to the order and agent, on the same record that shipping, COD settlement and warehouse use. Combined with the predictive dialer — which only connects agents to answered calls — recordings contain conversations, not minutes of ringing.
Building a sampling plan that supervisors can actually follow
Listening to every call is impossible. A practical sampling plan for confirmation teams:
| Sample | Why | Suggested volume |
|---|---|---|
| Random calls per agent | Baseline quality, fairness | A few calls per agent per week |
| All cancellations of a given day (or a sample) | Find avoidable cancellations | Daily review of a subset |
| Orders confirmed but refused at delivery | Find weak confirmations | Weekly batch |
| Disputes raised by merchants or couriers | Settle facts | Every case |
| New agents in their first two weeks | Fast coaching | More frequent |
| Calls longer than usual | Script gaps, difficult customers | Weekly |
The most valuable sample is often the second-to-last row reversed: orders that were confirmed but then refused or returned. Listening to those calls tells you what a "weak yes" sounds like in your market.
A scorecard for confirmation calls
Keep the scorecard short — eight to ten items — so reviewers use it consistently:
- Identification: agent introduced themselves and the store correctly.
- Order recap: product, variant (size, color), quantity and total price read back clearly.
- Payment: cash on delivery and the exact amount confirmed (including delivery fee).
- Address: city, district/neighborhood, street or landmark, building/apartment where relevant.
- Availability: delivery day or window confirmed; alternative phone number if useful.
- Customer intent: a clear yes, not a hesitant "okay". Agent checked doubts.
- Status accuracy: the status set in the system matches what was said.
- Tone and language: appropriate dialect/language, polite, no pressure.
- Compliance: recording notice given where required.
- Upsell (if your policy allows): offered without pressure, recorded on the order.
Score each item as yes / partial / no. Trends per agent and per team matter more than individual scores.
Dialect and language: quality is local
What "good" sounds like changes by market:
- In Morocco, customers switch between Darija, French and sometimes Amazigh; an agent who insists on formal Arabic can sound distant.
- In Algeria, Algerian Darija and French dominate, with Kabyle in some regions.
- In Egypt, Egyptian Arabic is expected; addresses rely heavily on landmarks and building descriptions.
- In Saudi Arabia and the Gulf, Gulf Arabic for nationals, and often English (or other languages) for residents.
Recordings let you calibrate QC per market rather than applying one script everywhere. Combine this with call routing so customers reach agents in the right language in the first place.
From recording to coaching
QC without coaching is just surveillance. A simple loop that works:
- Weekly 1:1, 15 minutes. Pick two calls: one good, one to improve. Listen together.
- One focus per week. For example "always read back the total price including delivery".
- Team clips. Share anonymized examples of excellent address capture or handling a hesitant customer.
- Script updates. If many agents fail the same item, the script or the screen is the problem, not the agents.
Agents usually accept recording faster when they see it used to settle disputes in their favor — for example proving that the customer did confirm and the courier was at fault.
Using recordings in disputes
Typical disputes in confirmation operations and how recordings settle them:
- "Customer never ordered." The recording shows the customer confirming the product and address.
- "Agent cancelled without calling." The call log and recording show the attempts and the conversation.
- "Wrong delivery day." The recording shows which day was agreed.
- "Price was not what the customer expected." The recording shows whether the total was read back.
Define who may access recordings (supervisors, QC, account managers) and log access. Share extracts with merchants only when needed and according to your contracts.
Privacy and legal notice in MENA
Recording phone calls involves personal data. Rules differ by country and change over time, so treat this as orientation, not legal advice:
- Morocco: Law 09-08 on personal data protection, supervised by the CNDP.
- Algeria: Law 18-07 on the protection of natural persons in the processing of personal data.
- Tunisia: Organic Law 2004-63, supervised by the INPDP.
- Egypt: Personal Data Protection Law No. 151 of 2020.
- Saudi Arabia: Personal Data Protection Law (PDPL).
- UAE: Federal Decree-Law No. 45 of 2021 on personal data protection.
Common good practice everywhere: tell the customer at the start that the call may be recorded for quality and service purposes, define a retention period, restrict access, and document the purpose. Validate your setup with a local legal advisor. Speedliv provides the recording capability; your organization remains responsible for its use.
KPIs to track with QC
- QC score per agent and team (trend over weeks)
- Avoidable cancellation rate — cancellations where the recording shows the agent could have saved the order
- Refused-at-door rate for confirmed orders — the best proxy for confirmation quality
- Dispute resolution time — how fast you can answer a merchant with evidence
- Coaching coverage — share of agents with at least one reviewed call per week
How Speedliv supports QC
- Call recording linked to the order and the agent
- Statuses, notes and attempt history on the same record
- Review by status, agent, team or time window
- Predictive dialer so recordings contain conversations, not ringing
- Call routing by country, language, merchant or shift
- AI-assisted confirmation to flag suspicious or incomplete orders
AI voice agents that take a larger share of calls and escalate to humans are on our roadmap (phase 2), not live today — when they arrive, the same recording and QC discipline will apply to them.
Getting started
- Turn on recording for all connected calls and add a recording notice to your script.
- Define the scorecard above (adapt to your market).
- Set the sampling plan and assign reviewers.
- Start weekly coaching with two calls per agent.
- After four weeks, compare refused-at-door and avoidable-cancellation rates.
Want to see how recordings, the dialer and routing fit together? Book a meeting or message us on WhatsApp at +212 661-962932.
