CODFamilia
Features How it works Pricing Blog FAQ Academy Sign up Sign in

COD lead management: handling an order before confirmation

A lead is an order that is still only an intention. Where leads come from, what makes a bad one, duplicates, damaged leads and how they are routed to agents.

The essentials

What is it?
A lead is the initial state of a COD order: someone left their details asking for a product, and the item, the total price, the address and even the genuine intention to buy are all unverified. It becomes an order only once confirmed by phone.
Who is it for?
The lead is the working object of the seller, who produces it, and of the confirmation agent, who calls it. It also matters to the account manager, because the quality of a seller's leads predicts their results better than their order count does.
How does it work?
It arrives from a store, a form, a direct message, a file or an API, and enters a queue. An agent takes it, the lead is locked for the duration of the call, and there are three outcomes: confirmed, callback due, or cancelled. A confirmed lead becomes an order and commits stock.
What is it for?
Because the lead/order distinction is the single most useful idea in COD: you pay to acquire a lead, you only earn on a delivered order. Confusing the two means counting sales that do not exist and dispatching parcels that will come back.
How do you use it?
You need one queue, a lead locked during the call, somewhere for callbacks and somewhere else for leads that arrived incomplete. CODFamilia provides those four things, with leads able to come from a YouCan store, a Google Sheets file, a webhook or the REST API.

A lead is an order that is still only an intention to buy: a name, a phone number and a requested product that nobody has verified yet, and which becomes an order only after a confirmation call.

Lead or order: the distinction that decides everything

A lead costs money the moment it arrives; an order earns money the moment it is delivered. Between the two there is a phone call, and that call is the only thing that turns a cost into revenue.

The asymmetry is brutal. The lead is paid for in advance, in advertising, in time or in an introducer's cut. The order only pays after delivery and collection, and only if the customer was there, still wanted the product and had given an exact address. A seller who says "I did a hundred orders today" has almost never done a hundred orders: they received a hundred leads, some of which will never exist.

That is why the two must stay separate in the figures as much as in the tool. Measuring an advertising budget against leads received gives a flattering cost per lead and tells you nothing: the only useful report compares the spend with delivered orders.

Where leads come from

Moroccan leads arrive through five channels, and each has its own way of producing dirty data.

  • An online store — The customer fills in the order form themselves: nobody transcribes anything, so it is the cleanest source. A YouCan store connects directly to CODFamilia; another type sends its orders by webhook or through the REST API.
  • A capture form — A single page with three fields, usually behind an advert. It produces plenty of volume and weak intent: filling in three fields costs nothing.
  • A direct message — Instagram, Facebook, WhatsApp. The most common channel among small sellers and the most expensive in data entry: everything has to be pulled out of a conversation by hand.
  • A spreadsheet — Leads collected elsewhere and then imported. CODFamilia can read a Google Sheets file; the quality depends entirely on how disciplined the columns are.
  • An API — A site or an application pushes the leads in directly. CODFamilia exposes a public REST API with API keys, as well as webhooks.

What makes a bad lead

A bad lead is not one that says no: it is one that could never have worked out, and that consumed a call anyway, sometimes a parcel. The cases repeat often enough to be listed.

  • The number belongs to nobody — A missing digit, an unreachable landline, a typo. Nothing is recoverable: the call is lost before it is made.
  • The customer does not remember ordering — A form filled in at a glance, or out of curiosity. Common on leads from very broad adverts.
  • The price was never understood — The customer thought the product cost less, or had not seen the delivery fee. Discovering the total on the phone means a cancellation; discovering it in front of the courier means a refusal, which costs far more.
  • The address cannot be delivered to — A district with no street name, a city with a namesake, no landmark. The lead is good, the address is not, and the call has to rebuild it.
  • The product is not the one the customer pictured — A size or colour variant, an accessory assumed to be included. A misunderstanding about the item is an almost certain return.
  • The lead is weeks old — An intention to buy goes stale. Calling late means calling somebody else.

Duplicates and damaged leads

Two anomalies are handled differently and are often confused: the same customer arriving twice, and a lead arriving in bad shape.

A duplicate is not always a mistake: the same number can come back because the customer clicked twice, because they ordered from two adverts, or because they genuinely want a second unit. Deleting the second lead automatically loses sales; dispatching two parcels to the same address loses more. The workable rule is to match leads by number, flag them to the agent, and let the call settle it.

A damaged lead is something else: it arrived malformed — a name in the phone field, a missing city, a product written as free text matching no reference, a value truncated on import. It is not bad, it is unreadable, and it must not enter the queue: an agent who lands on it wastes their time and ends up cancelling it.

What a seller can still change before confirmation

The window before the call is the only one in which a correction costs nothing. After it, every change involves somebody else: an agent who has already quoted a price, a hub that has already printed a label, a courier that has already taken the parcel.

  1. Fix the contact details — A number mistyped out of a direct message, an incomplete name. This is the most profitable correction of all: it saves a call.
  2. Clarify the address and the city — The city sets the delivery fee, and therefore the profit. A wrong city gives a wrong calculation and sometimes a misrouted parcel.
  3. Change the item or the quantity — As long as nothing is confirmed, the lead commits no stock.
  4. Add a note for the agent — "The customer asked for black", "call back in the evening". The agent reads the note during the call rather than rediscovering the context.
  5. Cancel the lead — An obviously empty lead does not need calling. Cancelling it is a decision, not neglect.

Routing leads to agents

A lead must belong to one person at a time. Without that, two agents call the same customer within the hour — which happens every time a queue is shared without a lock — and the customer draws the obvious conclusion about how the operation is run.

The mechanism is simple: the agent takes a lead, it is locked to them for the duration of the call, and it returns to the queue if the call does not conclude. If the customer asks for another time, a callback is scheduled rather than left to the agent's memory. If the call goes well, the agent can offer a larger quantity before confirming: it is the only point where the basket still grows without extra acquisition cost.

That leaves the question of who calls. A seller may confirm their own leads, in which case no confirmation fee applies — they pay in telephone hours, and the choice holds badly beyond a certain volume. Everyone else relies on confirmation agents, overseen by an account manager.

Frequently asked questions about COD leads

What is a lead in COD?
An order that is still only an intention: a name, a phone number and a requested product, none of them verified. It becomes an order after a confirmation call that settles the item, the total price and the address. The full cycle is covered on the order management page.
Why not just dispatch without calling?
Because a parcel sent without confirmation comes back far more often, and a return costs the delivery fee, the return fee and the advertising spent on the lead. The call checks intent, address and total price — the three most frequent causes of refusal.
What is a damaged lead?
A lead that arrived malformed: a field in the wrong place, a missing city, a product written as free text, a value truncated on import. On CODFamilia it is held in a separate list where the seller completes it before returning it to the confirmation queue.
What do you do when the same customer orders twice?
Do not delete it on sight. Leads are matched by phone number and flagged to the agent, who asks during the call: a double click gets merged, a genuinely wanted second unit is kept. The customer decides, not an automatic rule.
Can two agents call the same lead?
No, and that is deliberate. The lead is locked to the agent who took it for the duration of the call, then returns to the queue if the call does not conclude. Without that lock, a customer gets two calls within the hour.
Can a seller confirm their own leads?
Yes, and in that case no confirmation fee applies. In exchange they make the calls themselves: workable at low volume and hard to sustain afterwards, because the number of calls rises before the revenue does.
Where can leads come from on CODFamilia?
From a connected YouCan store, a Google Sheets file, a webhook, the public REST API with API keys, or manual entry. A store of any other type sends its orders through the API or a webhook.
How do you tell whether a lead source is any good?
By judging it on delivered orders, never on leads received. A source can produce a large volume of leads at the lowest cost each and still end up the most expensive per delivered sale. That requires the source to stay recorded on the lead all the way to delivery.
How long does a lead stay usable?
Less long than one hopes. An intention to buy cools off, and a late callback feels like a cold call. That is why callbacks are scheduled and tracked rather than postponed indefinitely.

Also worth reading

A clean lead queue, and calls that do not collide

Leads from your store, a file or the API, locked during the call, scheduled callbacks and a separate list for leads that arrive incomplete.

Sign up