A call rule connects a store event to a confirmation call. It filters orders with conditions, waits, calls inside your window, retries and gives up when you say so.
A COD call rule decides which orders get a confirmation call and when. Conditions such as payment method, COD amount, order total and item count pick the orders. Timing sets the wait before the first call, total attempts, gaps between attempts, which results trigger a retry, when to give up, and the IST calling window.
order.created starts a call for rules that trigger on it. order.cancelled cancels any pending call for that order. order.paid cancels a pending COD call, since the order was paid online. Other events are stored and ignored.
The order must match every condition. By default: payment method is COD and COD is not already confirmed.
By default 2 minutes, so the customer can finish checkout and quick cancellations arrive first.
Calls are placed between the window start and end in IST, 09:00 to 21:00 by default. Orders outside it are called when the window next opens.
If the call is not answered, busy or failed, it is retried after the gaps you set, up to the total attempts, until the order settles or the give-up time passes.
Every setting is adjustable per rule
| Setting | Default | What it does |
|---|---|---|
| Trigger | order.created | The store event that starts a call (order.created or order.paid) |
| Conditions | Payment method is COD, COD not already confirmed | Only orders matching all conditions are called |
| Wait before the first call | 2 minutes | Lets the customer finish checkout first |
| Calling window (IST) | 09:00 to 21:00 | Orders outside it are called when it opens |
| Attempts (total calls) | 3 | First call plus retries |
| Gaps between attempts | 30 minutes, then 120 minutes | The last gap repeats |
| Retry when | No answer, busy, call failed | Add "answered but no key pressed" to redial silent calls |
| Give up after | 48 hours | The order settles as Expired even with attempts left |
| Caller ID | Your first number | The number customers see |
| Script | Hindi or English | Customer name, store, order number and amount filled in |
Combine as many as you need. No conditions means every order.
Call only cash-on-delivery orders, or any payment method string your store sends.
Compare in rupees with is, is not, >, >=, < or <=, for example only call orders above a set amount.
Target orders by the number of items, for example multi-item orders.
Skip orders already confirmed on the store, so no customer is asked twice.
Leave out orders that are already cancelled.
Match on order tags (contains, doesn't contain) or on the phone number.
Share your use case and volume. We reply within one working day with a setup plan and pricing.
Explore more comparisons, alternatives, and resources
COD confirmation guides
Connect your store, get a number and create your first call rule at orders.edesy.in. Calls are billed per minute from your Edesy wallet.