Blog
Why Paithra's outbound calls stop at 9pm
TRAI's Telecom Commercial Communications Customer Preference Regulations set a 09:00–21:00 IST window for any commercial voice call. Paithra enforces that window in the code that places every call, not in a setting a campaign can turn off, and this is what that enforcement actually looks like.
The statutory window, not a house rule
TCCCPR restricts a commercial voice call — the category an AI sales call falls into — to 09:00–21:00 IST, regardless of which state the lead or the caller is in. It is not a courtesy Paithra chose; it is the outer bound Indian telecom regulation sets for this kind of call, and it applies whether the caller is a person or software.
How the code enforces it
The calling-window logic converts the current time to IST minutes past midnight and compares it against two constants: 540 minutes (09:00) and 1260 minutes (21:00). A campaign can configure its own start and end time — a business that only wants to call between, say, 10:00 and 18:00 can set that — and the resolver clamps whatever it is given into the statutory bounds:
const startMinutes = Math.max(requestedStart, TRAI_WINDOW_START_MINUTES); const endMinutes = Math.min(requestedEnd, TRAI_WINDOW_END_MINUTES);
A campaign configured to start at 07:00 is clamped up to 09:00. One configured to end at 23:00 is clamped down to 21:00. A window configured backwards — an end time before its start — is not treated as a licence to call all day; it resolves to a closed window instead.
Why this is worth writing down
A platform that trusts campaign configuration for its compliance boundary is one bad default away from a 6am call. Paithra’s window is the other way round: the statutory bound is the ceiling and floor, and configuration can only make the window narrower, never wider. That is a design decision worth being explicit about, not a claim to take on faith.