Schedules, Caps and Calling Hours

How Edesy Collect schedules each debtor - attempts per day, total attempts, minimum gap between attempts, calling hours in IST, and the server-side limits that cannot be exceeded.

3 min read

Collect schedules every debtor separately. The first call is at the next calling-window open after upload; each later attempt waits at least the gap you set, moves to the next morning once the daily cap is reached, and stops at the total cap. Calling hours default to 09:00 to 20:00 IST; the server never calls before 09:00 or after 21:00.

Settings#

Setting API field Default Allowed
Attempts per day max_attempts_day 2 1 to 3
Total attempts max_attempts_total 6 Any positive number
Gap between attempts (minutes) min_gap_minutes 180 60 or more
Calling window start (minutes after midnight, IST) call_window_start 540 (09:00) 540 or later
Calling window end (minutes after midnight, IST) call_window_end 1200 (20:00) 1260 (21:00) or earlier
Stop after an answered call stop_on_connect false true / false

The portal's New campaign form sets attempts per day, total attempts and the gap. Calling hours and stop_on_connect can be set through the API when you create the campaign.

Values outside the allowed range are corrected on the server, not rejected: asking for 5 attempts a day stores 3, a 30-minute gap stores 60, and a window of 07:00 to 23:00 stores 09:00 to 21:00. If the end is not after the start, the window resets to 09:00 to 20:00.

How the ladder runs for one debtor#

  1. Upload: the first attempt is set to now if you are inside the window, otherwise to the next window open.
  2. After each attempt: the next attempt is the gap later. If that falls outside the window, it moves to the next window open.
  3. Daily cap reached: the next attempt moves to tomorrow's window open. The daily count resets each day in IST.
  4. Stop: no more calls when any of these is true:
    • the debtor is marked paid, promised or stopped (always applies)
    • stop_on_connect is on and the debtor answered
    • the total cap is reached
    • with a number pool, every active number in the pool has already been used for this debtor (see Number Pools and Rotation)

Example with the defaults: a debtor uploaded at 10:00 is called at 10:00 and 13:00, then at 09:00 and 12:00 the next day, and so on until six attempts, unless they are marked paid first.

Other things that are always on#

  • Do-not-call screening on upload.
  • KYC gate on upload and start.
  • Concurrency: up to 5 calls at a time per campaign by default.

FAQ#

Can I call on Sundays? The window applies every day. To skip a day, pause the campaign with POST/v1/campaigns/:id/pause and resume it with POST/v1/campaigns/:id/resume.

Why did my 07:00 start time change to 09:00? Reminder calls are limited to 09:00 to 21:00 IST and the server clamps any wider window.

Can I schedule calls by due date, for example 3 days before? Not yet. Reminders start from upload. Upload a debtor when you want reminders to begin.

Was this page helpful?