Cash-on-delivery orders are easy to place and easy to abandon at the door. The customer has not paid yet. The address may be incomplete. Someone has to be home. If any of those fail, the parcel comes back, and the brand has already paid to send it.
A short confirmation before dispatch is the practical fix. An AI voice call can ask the customer to confirm the order, the address, and that someone can receive it. WhatsApp can send the same details in writing, plus a payment link if the customer wants to pay now. A person steps in only when the answer is unclear or the order looks wrong.
Key takeaways
Confirm a cash-on-delivery order before it leaves the warehouse, not after the courier has already tried the door.
The voice call handles the conversation: product, address, availability, and whether the customer still wants the order.
WhatsApp carries the written record: address, payment link, and a follow-up when the call is missed.
Unconfirmed, wrong-number, and refused orders can be held instead of shipped.
A prepaid option can be offered on the call. Paying is still the customer’s choice.
Disputes, address changes the bot cannot close, and high-risk orders stay with a person.
What COD confirmation is
Cash on delivery means the customer pays when the parcel arrives. The shop does not know, at the moment of checkout, whether the buyer will be there or still wants the item.
Confirmation is a second conversation before dispatch. It checks four things:
The customer placed the order and still wants it.
The product, size, colour, and quantity are right.
The delivery address and phone number are usable.
Someone expects to be available to receive it.
If the customer confirms, the order can move to dispatch. If they cancel, the order can be stopped. If they do not answer, the team can retry, hold the order, or review it, according to the rule the brand sets.
Why voice and WhatsApp work together
A phone call is the faster way to settle a yes or no. The customer can correct an address out loud, refuse the order, or ask for a different delivery day. The bot records that outcome.
WhatsApp is the written half of the same job. A payment link is awkward to read out on a call. An address is easier to check on screen. A missed call still needs a message the customer can answer later.
A typical split:
Step | Voice | |
|---|---|---|
First contact | Calls to confirm the order | Optional message that a call is coming |
Detail check | Confirms product, address, and availability | Sends the address in text if the customer wants to see it |
Prepaid option | Asks if the customer wants to pay now | Sends the payment link |
No answer | Retries on a set schedule | Sends a short confirmation request |
After the call | Stores the outcome | Sends a recap of what was confirmed |
The two channels should share one order record. Otherwise the call can say “confirmed” while the message thread still shows the order as unpaid and unchecked.
How the workflow runs
Order placed. The checkout marks the order as cash on delivery and passes the product, price, address, and phone number to the confirmation flow.
Call placed. The voice bot calls after the order, on the timing the brand chooses. The aim is to call before the parcel is handed to the courier.
Identity and order. The bot confirms it is speaking to the buyer and restates the item and the amount.
Address and availability. The bot reads the delivery address and asks whether someone can receive the parcel.
Outcome. The reply is stored as confirmed, cancelled, reschedule, callback, no response, or wrong number.
Prepaid offer, if the brand uses one. The bot can offer payment now and send a link on WhatsApp. The order stays cash on delivery if the customer declines.
Dispatch rule. Confirmed orders can ship. Cancelled and wrong-number orders should not. Unanswered orders follow the brand’s hold or review rule.
The path is: COD order, voice confirmation, address and availability check, optional WhatsApp payment link, then confirmed, held, or cancelled. Dispatch happens only if the rule allows it.
What the call should ask
Keep the script short. The customer did not ask for a sales call.
State the shop name, the order, and the item.
Ask if the details are correct.
Read the address and ask for a correction if it is wrong.
Ask if someone will be available for delivery.
If the brand offers it, ask once whether they would rather pay now.
Close with what happens next: dispatch, a payment link, or a hold.
A correction the bot understands, such as a flat number or a landmark, can be written back onto the order. A change it cannot parse should go to a person before the label is printed.
What WhatsApp should send
Use WhatsApp for anything the customer may need to open again.
A payment link, when they agree to pay before delivery.
The address they just confirmed, so they can reply if a word was misheard.
A missed-call message with a simple confirm or cancel reply.
The dispatch update after the order is released, which is a separate message from the confirmation itself.
Do not send a payment link to every cash-on-delivery buyer. Send it when the customer has agreed on the call, or when they choose that option in the WhatsApp reply.
What to do with each outcome
Outcome | What it means | Sensible next step |
|---|---|---|
Confirmed | Item, address, and availability accepted | Release for dispatch |
Pay now | Customer asked for a payment link | Send the link; ship after payment, or on the brand’s rule |
Cancelled | Customer does not want the order | Do not ship |
Address change | A correction was captured | Update the order, then confirm again if the change is large |
Callback | Customer asked to be called later | Schedule one more call |
No response | Calls were not answered | Retry, then WhatsApp, then hold or review |
Wrong number | The person reached is not the buyer | Hold the order for a person |
Repeat buyers with a clean delivery history can be left out of the call list if the brand wants the bot focused on new or risky orders. That is a routing choice, not a requirement.
What stays with a person
The bot is for a known script. A person should take:
An address change that does not fit the fields on the order.
A dispute about price, product, or a previous delivery.
A customer who is angry or asks for something the script does not cover.
An order the rules flag as suspicious, such as a number that never connects or an address that fails a basic check.
The point of the automation is to stop obvious refusals and dead numbers from becoming shipped parcels, and to leave the unclear cases in a queue a person can finish.
Where this sits in the order journey
Confirmation is one step, not the whole delivery conversation. An abandoned cart is a different call, made before checkout. An order-status call is later, when a shipment is delayed or out for delivery. A return call happens after the customer has the item.
Cash-on-delivery confirmation belongs in the gap between payment choice and dispatch. If that call happens after the courier has the parcel, it can still record a refusal, but it can no longer stop the trip.
Explore Fonada
COD order confirmation for the ecommerce workflow
Voice AI for the confirmation call
WhatsApp for the payment link and the written follow-up
Order status calls for updates after the parcel ships