Picture a mid-sized private bank, which we will call Northgate Bank, that hires a BPO to run an outbound campaign. Monday’s list has three kinds of numbers. Some are customers with pending loan documents. Some are customers whose card is due for renewal. Some are existing customers who might like a new insurance product. The agents will call all of them from the same floor, using the same dialler. Under Indian telecom rules, those three groups are not the same kind of call at all.

The regulator and the idea

The Telecom Regulatory Authority of India (TRAI) governs unsolicited commercial communication through the Telecom Commercial Communications Customer Preference Regulations, 2018, often shortened to TCCCP. The central idea is that a consumer chooses what kind of commercial contact she is willing to receive, and businesses must check that choice before reaching out. The older do-not-call register evolved into a preference system where a customer can block all promotional communication or allow specific categories, such as banking or real estate.

The second idea is traceability. Businesses that send commercial messages must register on distributed ledger technology (DLT) platforms run by telecom operators. They register as a principal entity, register their sender headers, and register message templates. A message that does not match a registered header and template should simply not be delivered. For voice calls, registered telemarketers must use number series allocated for the purpose, so that a recipient can recognise and report them.

Sorting Northgate’s three groups

The regulations recognise categories, in broad terms: transactional or service communication, and promotional communication. This distinction decides almost everything operationally.

  • Pending loan documents. This is about a transaction already under way. It is a service or transactional contact. The customer cannot opt out of it through the preference register in the same way, though she can of course tell you to stop and the bank should respect that for non-essential contact.
  • Card renewal. Generally service, as it concerns an existing product the customer holds. Wording matters: the moment the call pivots to “and would you like an upgrade to our premium card”, it has become promotional.
  • The insurance offer. Plainly promotional. Before calling, the numbers must be checked against customers’ registered preferences and against the consent records. A customer who blocked promotional contact, or who did not opt in to the insurance category, cannot be called for this.

Notice what this means for the floor. The same agent, in the same shift, might be making a service call and a promotional call. The compliance obligation travels with the purpose of the call, not with the team’s name.

What the BPO actually checks

Return to Monday morning. Before the list is loaded into the dialler, a compliant process does several things.

  1. Tags each record by purpose: service, or promotional.
  2. Scrubs promotional records against the customer preference data and against the bank’s own internal do-not-call list, which includes people who said “do not call me again” on any earlier call.
  3. Confirms the calling line and number series are the ones permitted for that call type. Rules on which series apply to which category have been revised by TRAI more than once, so this is a point to verify against the current directions, not memory.
  4. Applies calling-time windows. Promotional calls are restricted to daytime hours (commonly cited as 9 am to 9 pm), and a dialler should enforce this automatically.
  5. Keeps records: consent evidence, scrub dates, call logs. If a complaint arrives, the bank must show what happened.

Where things go wrong

The commonest failure is not malice. It is stale data. A customer registers a block on a Friday, the scrub file was refreshed on the previous Monday, and the call goes out on Tuesday. The fix is a short refresh cycle and a rule that agents can mark “do not call” in real time, which feeds the internal list before the next dial.

The second failure is the pivot. A service call that becomes a sales pitch without checking whether the customer is permitted to receive one. Process design can help: the script for a service call can instruct the agent to ask permission before offering anything else, and the quality form can treat an unauthorised pitch as a compliance-critical error.

The third is shared numbers and wrong party contacts. If the person who answers says she is not the customer, the number should be flagged and removed from the campaign, not retried next day.

Consequences, stated carefully

The regulations contemplate action against violators, including warnings, financial disincentives and disconnection of telecom resources used for violations. Specific amounts and procedures have changed over time, so a team should not quote a penalty figure from memory. In practice the sharper risks for a BPO are contractual: a client can terminate or demand indemnity if the BPO’s calling practice exposes the client’s brand, and a bank’s own regulator may take an interest in complaints about its calling.

Finally, the law is only the floor. A customer who says “stop calling” on the third attempt is angry for reasons no regulation captures. Honouring the request on the first attempt, quickly and in the record, is both compliant and plain good practice.

Figures and names in the examples are illustrative. Check current TRAI directions before building or auditing a process.

Leave a Reply

Trending