The 8-to-7 window — what we hear when the dialer bleeds past seven o'clock

Most calling-hour violations are not decisions. They are drift.

Nobody on a collections floor decides to call a borrower at 7:40 PM. The dialer was set to stop at seven, a campaign ran long, and twenty numbers got dialled into the dark. An agent took a “quick follow-up” from a personal phone after the shift ended. A borrower’s own callback at 8:15 PM got logged as an outbound attempt. None of it was a policy choice. All of it is a violation — and almost none of it shows up in random QA sampling, because sampling pulls calls at random and off-hours calls are a thin slice of the day. The one category that is trivially detectable is the one nobody surfaces.

That gets more expensive next week.

The rule was always 8 to 7. From July it grows teeth.

RBI’s permitted contact window for recovery agents is 8 AM to 7 PM. That is not new. What is new is the draft recovery-agent framework — proposed to take effect 1 July 2026 — that turns a guideline into something logged. Under it, the 8-to-7 window applies across every channel: calls, messages, visits. Repeated calls and calls from unidentified numbers are barred. And lenders must keep records of the number and timing of calls, with mandatory recording.

Read that last part slowly, because it is the whole issue. Until now, “we stopped at seven” was a claim. From July it is a timestamp. The window stops being a line in a policy document and becomes a column in a log that a lender’s audit team — and a regulator — can sort by.

What the logs say that the floor doesn’t

Across our audit network, the off-hours call almost never sounds like a violation. It sounds like diligence. The agent is calmer at 7:30 than at 3 PM — fewer calls in the queue, more time per borrower. The conversation is often better. That is exactly why the floor doesn’t flag it: it doesn’t feel like a breach, it feels like good service.

The patterns that recur:

• Dialer drift. A campaign set to end at 19:00 keeps connecting calls that were already dialling at 18:59. The setting says seven. The connect-timestamps say 19:03, 19:06, 19:11.
• The personal-phone follow-up. The official line stops at seven; the agent’s own number doesn’t. These calls never touch the recording system, so they are invisible to QA and radioactive in a complaint — an off-hours, unrecorded call the floor cannot even produce.
• The misclassified callback. A borrower rings back at 8:20 PM. The CRM logs an “outbound contact” at 20:20. On paper the agency called a borrower after hours. The truth — that the borrower called first — lives in nobody’s report.
• The weekend “courtesy” call. A Sunday reminder that felt helpful, placed without the consent that would make it permissible.

Each of these is a single field — a timestamp, a channel, a number — that the floor never looks at and a complaint goes straight to.

Three controls, before the rule does it for you

None of these needs a policy review. They need someone to look at a column nobody currently sorts.

1. Enforce the window at the dialer, not the script. A hard stop that refuses to connect a call after 19:00 — not one that asks agents to wind down by seven. If enforcement lives in a human’s judgement at the end of a long shift, it will drift. Put it where it can’t.
2. Run a weekly off-hours pull. Don’t sample randomly for this one. Filter every call with a connect-timestamp before 08:00 or after 19:00 and review the whole set. It is a small list. It is the exact list a regulator would build first.
3. Reconcile inbound vs outbound at the edges. Spot-check the calls logged in the first and last hour against who actually dialled. The misclassified-callback error only appears when you check direction against the carrier record, not the CRM label.

A floor that audits its off-hours calls knows its own timestamps before anyone asks for them. A floor that doesn’t will learn them the week a borrower complains — read back from a log it never opened.