Caller ID rotation spreads payment reminder calls across a small pool of 2 to 4 numbers instead of calling every debtor from one number. Each attempt picks a number by rule (least recently used, or sticky-then-rotate), and numbers flagged as spam-blocked are skipped. It keeps any one number from being overused and gives repeat attempts a better chance, within the same daily caps and calling hours.
Set up a reminder pool: Open Edesy Collect, add your numbers to a pool and choose a rotation rule.
Why one number isn't enough for reminders
A payment reminder campaign is different from a one-off broadcast. You call the same people again and again: before the due date, on the day, and after it. That has side effects on a single caller ID:
- Volume on one number. Many calls from one number in a short time is the pattern spam filters look for.
- Ignored numbers. A customer who has decided not to pick up that number will keep not picking up.
- One flag stops everything. If the number gets a spam label or is blocked, the whole campaign is hit.
A small pool fixes all three without changing who you call or how often.
How rotation works in Edesy Collect
| Part | What it does |
|---|---|
| Number pool | Caller ID numbers you own, grouped for reminder campaigns (up to 6; 2 to 4 recommended) |
| Rotation rule | Least recently used, or sticky-then-rotate |
| Per-contact memory | A contact's attempts prefer a pool number they haven't been tried on yet |
| Health tracking | Each number is active or flagged; you flag a number manually and rotation skips it |
| Reactivate | Put a flagged number back into service when it's fixed |
Least recently used picks the pool number that has been idle the longest. Load spreads evenly across the pool, and repeat attempts to the same person tend to come from different numbers.
Sticky-then-rotate keeps using the same number for a contact while it works, and moves on only when it has to (for example, when that number is flagged). Customers see one consistent number most of the time.
| Rule | Customer sees | Best when |
|---|---|---|
| Least recently used | Different numbers across attempts | High volume, you want even load and fresh attempts |
| Sticky-then-rotate | Mostly the same number | You want customers to recognise and call back one number |
Keep the pool small
It's tempting to think more numbers means more answers. It doesn't. Large, constantly changing pools are a pattern associated with spam, and they make it hard for customers to recognise you or call back. Edesy Collect pools are deliberately small: a pool holds at most 6 numbers, and 2 to 4 is the recommended range.
Every number in the pool should:
- belong to your business and pass KYC,
- be routed for inbound calls (forwarding to your collections team, an IVR or a missed-call capture),
- be consistent with your brand, so a customer who searches the number finds you.
Health: flag and reactivate
If customers or your team report that a pool number shows as spam, or answer rates on one number drop sharply compared with the others, flag it as spam-blocked in the pool. Rotation stops using it straight away. Once the problem is dealt with, reactivate it.
Compare answer rates by number in your results. One number with a much lower answer rate than the rest is the earliest warning sign.
Rotation is not a way to call more
Rotation changes which number calls, not how often. Collect keeps campaign settings inside these limits no matter how big the pool is:
| Limit | Value in Edesy Collect |
|---|---|
| Attempts per debtor per day | At most 3 |
| Minimum gap between attempts | 60 minutes |
| Calling window | Default 09:00 to 20:00 IST, never outside 09:00 to 21:00 (set through the API) |
| Stop rules | Stop on payment; mark paid, promised or stopped through the API |
If you're a regulated lender or work for one, your own rules may be stricter than these. See calling hours rules for collection calls.
What it costs
Collect plans include one number. Extra caller ID numbers for the pool cost about Rs 500 a month each.
| Plan (monthly, plus 18% GST) | Included calls | After that |
|---|---|---|
| Starter: Rs 1,499 | About 1,000 | Rs 0.90 per connected call |
| Growth: Rs 3,499 | About 4,000 | Rs 0.75 per connected call |
| Scale: Rs 10,499 | About 16,000 | Rs 0.60 per connected call |
Unanswered calls are free. A pool of three numbers on Starter is Rs 1,499 plus about Rs 1,000 for the two extra numbers, plus GST. See payment reminder call pricing.
Setting it up
- Sign up on Edesy Collect and complete KYC.
- Choose a plan. One number is included; add one to three more for the pool.
- Create a number pool, add the numbers and choose least recently used or sticky-then-rotate.
- Create a reminder campaign with one message (typed as text, rendered by TTS and cached) and pick the pool. Calling hours are set through the API; the default is 09:00 to 20:00 IST.
- Paste debtors as lines of
phone,name,due_date,amount, or add them through the API. - Have your server call the payment webhook (
POST /v1/collect/webhooks/payment) when a payment lands, so paid contacts stop being called. For Razorpay, forward events from your own Razorpay handler. - Start, and check answer rates per number in the results.
Pools can also be managed through the API (/v1/collect/pools). See the Collect docs.
Related
- Payment reminder call schedule by due date
- Promise-to-pay tracking
- Fallback caller ID for voice campaigns, which is a different feature for broadcast campaigns
- EMI reminder IVR calls
More on the product: payment reminder calls.