Quiet hours in Indian collections: what the rules actually require

The RBI Fair Practices Code expects lenders and their agents to contact borrowers at reasonable times and places. In practice the industry norm is a calling window from morning to early evening, with local sensitivity beyond it. The words are simple; the operational question is where the rule is enforced.

The three places a quiet-hours rule can live

• In training: agents are told the window. Fails on the first hectic day.
• In review: calls outside the window are flagged afterwards. The breach already happened.
• In the dialer: a call outside the window is never placed. The rule becomes physics.

Only the third survives scale. When contact volume is a lakh touches a day across voice, WhatsApp, SMS and field visits, any rule that depends on a person remembering it will be broken daily, and every breach is a complaint waiting to be escalated.

What enforcement-at-dispatch has to cover

• Timezone discipline: windows in IST, not server time.
• Every channel, not just voice - a 2 a.m. WhatsApp reads as harassment too.
• Campaign-level variation: early-bucket reminders and legal-stage notices deserve different windows.
• Evidence: for any contact, the ability to show when it happened and which rule allowed it.

The cases that break a naive window

A single start time and end time handles the easy ninety per cent. The rest is where complaints come from, and each case deserves a decision made once, in the system, rather than argued on the floor every week.

• The borrower calls you at 9 p.m. Answering an inbound call is not the same act as placing an outbound one, and a system that stops an agent picking up is enforcing the wrong rule.
• A promise falls due on a Sunday. Whether reminders go out on rest days is a policy choice; the point is that it should be a setting somebody chose, not an accident of when the batch happened to run.
• A retry is scheduled for 6:55 p.m. and the queue is running late. The window has to be checked at the moment of dispatch, not the moment of scheduling, or the delay itself creates the breach.
• The borrower asks not to be called before noon. A per-borrower preference has to beat the campaign default, and it has to survive the next file upload.
• A field visit is planned for an address two hours away. Visit windows and calling windows are different rules about different things, and deserve separate settings.

Frequency is the other half of the same rule

Contact hours and contact frequency are usually written about separately and experienced by the borrower as one thing. Six compliant calls inside the window, every day for a week, is not a defensible pattern merely because each call was individually within the hours. Caps belong next to windows: per day, per week, per channel, and counted across channels rather than within each one, because nobody on the receiving end experiences SMS and voice as separate relationships.

Proving it afterwards

Enforcement is only half of what the rule asks for. When a complaint arrives months later, the question is not whether the policy was correct but what actually happened on a particular afternoon. That means every contact carries its timestamp in IST, the window that allowed it, the campaign it belonged to and the outcome it produced, and that all of it can be pulled for one borrower across a year without raising a ticket with engineering.

Five questions worth asking a vendor

• Show me a call that the window blocked, not a report saying none were placed.
• Where is the window stored, and who can change it without a deployment?
• Is the window evaluated when the touch is scheduled, or when it is dispatched?
• Does the frequency cap count across channels, or separately within each?
• Can you produce every contact attempt for one borrower for the last twelve months, with times and outcomes?

The test for any collections system is one question: can a call that would breach the window even be placed? If the answer involves the word 'shouldn't', the rule is a hope, not a control.