Why Your Confirmation Call Script Is Costing You Deliveries

In most e-commerce markets, a customer who places an order has already paid. The delivery is the last step, not a second decision.

In Morocco, it works differently.

The dominant payment model is cash on delivery (COD). The customer orders, pays nothing upfront, and decides whether to accept the parcel when the courier arrives. If they change their mind, are not home, or simply do not answer the door, the courier brings the order back. That is a return-to-origin, or RTO.

No sale. No revenue. And a cost you have already absorbed: the product was packed, the courier was paid for the attempt, and the return trip needs to be paid for as well. Depending on your courier contract, you may be billed for both legs.

In markets with card payment, a failed delivery is an inconvenience. In a COD market like Morocco, it is a direct hit to margin, and it happens at scale. RTO rates of 20 to 40 percent are common. For some product categories and some operations, they go higher.

Merchants who take this seriously look at three places: their targeting, their product pages, and their couriers. Those three levers matter. But there is a fourth one that is consistently underestimated: the confirmation call.

What the Confirmation Call Is Supposed to Do

After an order is placed, most Moroccan e-commerce operations call the customer before dispatching. The purpose is straightforward: verify that the order is real, confirm the address, and make sure someone will be available to receive it.

Done well, the confirmation call significantly reduces RTO. A customer who has spoken to a real person, confirmed their address, and been told when to expect the courier is far more likely to be present and willing to pay on delivery.

Done poorly, it creates a false signal. The order gets logged as confirmed, dispatched, and returned, and the data shows a confirmed delivery that failed with no visibility into why.

Most operations are doing it poorly without knowing it.

The Four Variables That Determine Call Outcome

1. Timing

The window between order placement and the confirmation call matters more than most merchants realise.

Call within fifteen to thirty minutes of order placement and you are reaching a customer who still remembers placing the order and is still in a buying frame of mind. Wait two or three hours and you are reaching someone who may have reconsidered, moved on, or simply forgotten the context of what they ordered.

Calls made the following day have significantly lower confirmation rates for impulse-driven products. If your team batches calls at the end of a shift, your confirmation rate data is probably hiding the cost of that delay.

2. Tone

There is a difference between reading a script and having a brief, clear conversation. Customers can hear the difference.

A call that opens with an agent moving quickly through order details signals that the agent wants to finish as fast as possible. That is not a buying environment. It is a checkbox environment. A customer who confirms in that context has not recommitted to the order. They have just said yes to get off the phone.

A call that moves at a pace allowing the customer to engage, even briefly, produces a qualitatively different confirmation. One that actually holds.

This does not require a long call. It requires not sounding like a script is being read.

3. Information Accuracy

Customers who know what to expect receive their parcels at higher rates than those who do not.

Being specific about the delivery window makes a practical difference. "Thursday or Friday, the courier will call you before coming" is useful. "Two to three days" is not. If a customer does not know when to expect the parcel, they will not plan to be available for it.

Confirming the address out loud also matters. An agent who reads back the address and the customer corrects a detail has just prevented a failed delivery before it happened. An agent who assumes the address is correct and moves on has passed that risk to the courier.

4. Handling Hesitation

A customer who expresses doubt on the confirmation call is not automatically a lost order. They are the order most worth saving.

Common forms of hesitation include asking about the price again, asking what happens if they want to refuse, or saying they need to check with a family member. Each has a productive response that is not pressure. Most agents either push past hesitation quickly or are not trained on it at all. The result is a customer who says yes but is not committed. That is the most expensive kind of confirmation: it registers in your data but does not deliver.

Common Script Problems and What They Cost

Opening with the order total. Leading with price before the customer has re-engaged with what they ordered creates unnecessary friction. Confirm identity and the product first.

Vague delivery window. A customer will not clear their schedule for "as soon as possible." Give a specific day or two-day window wherever you can.

Not confirming the address out loud. One wrong digit in a phone number, a misheard street name, an incomplete building reference. Read it back every time.

No clear close. The call ends without the customer knowing what happens next. Will the courier call before arriving? Will there be an SMS? If the customer does not know what to expect, they are more likely to be unavailable when it matters.

The Deeper Problem With the Call Model

Fixing the confirmation call script is possible. But it misses the structural issue.

A call-based confirmation process requires trained agents, consistent execution, available phone lines, and enough headcount to reach every order within the right timing window. When order volume goes up, the cost goes up with it. When an agent has a bad day, your RTO rate reflects it. When the team is at capacity, calls get batched and delayed, and timing, as covered above, directly affects whether a confirmation holds.

The call model is also one-directional in a way that does not suit how customers in Morocco actually communicate. A customer who receives a call at an inconvenient moment will confirm just to end it. A customer who receives a WhatsApp message can respond when it suits them, and that response carries more genuine intent.

A More Efficient Confirmation Model

Automating the confirmation journey removes the dependency on agent availability, script consistency, and timing discipline. The sequence covers initial confirmation, address verification, delivery window communication, and pre-delivery reminder. It runs automatically across WhatsApp and SMS from the moment an order is placed.

The customer gets a message within minutes of ordering, not hours. They confirm at their own pace. The address is verified through a structured exchange rather than a conversation that depends on one agent hearing correctly. And the follow-up before delivery happens without anyone having to remember to send it.

This does not just reduce RTO. It reduces the cost per confirmed order significantly, because the process no longer scales with headcount.

For operations processing more than a few dozen orders a day, the resource gap between a call-based model and an automated one is substantial, in time, in salary cost, and in the management overhead required to keep call quality consistent.

Where to Start

If your current confirmation process relies on calls and your RTO rate reflects it, the question is not how to train your agents better. It is whether the call model is the right foundation at all.

Sorato builds and manages automated confirmation journeys for Moroccan e-commerce operations — WhatsApp and SMS sequences that handle the full process from order placed to parcel received. If you want to see what that looks like for your operation, get in touch.