TRAI DND and consent basics for commercial calls

Commercial calling and messaging in India is governed by the Telecom Commercial Communications Customer Preference Regulations, 2018, made by the Telecom Regulatory Authority of India. The regulations set up a preference register — formally the National Customer Preference Register, universally called the DND registry — where the holder of a phone number can record that they do not want commercial communication.

Two features of it are commonly misunderstood. First, the preference can be full or partial: a number can opt out of everything, or opt out by category, so that a person might block promotional calls about property while remaining open to those about banking. Second, what the register governs is unsolicited commercial communication. It is a default, not an absolute prohibition, and consent can override it for the category consented to.

Registration, deregistration and complaints are handled through the telecom operators, including the 1909 short code and operators' own apps and portals. The exact process changes from time to time, so it is worth checking the current route rather than relying on a remembered one.

A number appearing on the register does not mean it can never be contacted, and the two routes that permit contact are distinct in kind.

Inferred consent arises from an existing relationship. Someone who holds a service contract with a business can reasonably be contacted about that relationship, and this basis lasts for the duration of the relationship rather than indefinitely. It does not extend to promoting unrelated products.

Explicit consent is a separate track with heavier requirements. Under TRAI's framework it must be verified directly with the recipient and recorded through a registered Consent Registrar on the telecom operators' Distributed Ledger Technology platform, tied to the specific customer, the specific category, and the specific registered sender. A note in a business's own system is not explicit consent in the regulatory sense, however honestly it was obtained.

There is a further point worth knowing: a 2025 amendment addressed how long explicit consent lasts when taken for fulfilling a commercial transaction. The detail is covered separately in the article on explicit consent and its expiry.

Most disputes about commercial calling come down to a business believing it had consent and the framework disagreeing about what consent is.

The distinction that matters is between an agreement a business records for itself and a permission registered on the infrastructure the regulations rely on. Several things people treat as consent are not: a verbal yes noted in a spreadsheet, a tick box on a form the business keeps its own record of, a number given for one purpose then used for another, and a general willingness to hear from the business at some point.

Specificity is the other half. Consent under this framework attaches to a purpose or category and to a registered sender, so consent to be contacted about a service is not consent for promotional calls about something else.

The practical implication is that consent has to be checked at the point of use rather than assumed from collection. Businesses that treat it as a permanent property of a contact record are the ones that discover the problem only when a complaint arrives.

The most common misapprehension in small-business calling is that a purchased or shared list transfers permission along with the numbers. It does not, and the reasoning is worth understanding rather than memorising.

Consent under this framework is a relationship between a specific person and a specific registered sender, for a specific category. It is not a property of the phone number that travels with it. A vendor cannot pass on something they hold in their own name, and in the ordinary case there was no consent to pass on: the numbers were collected for something else, or scraped, or assembled from sources nobody can now identify.

So a business calling from a bought list has, for each number, either no consent basis at all or one belonging to someone else. Where the number is also on the preference register, the call is straightforwardly unsolicited commercial communication.

The assurance that a list is opt-in or DND-cleaned is not verifiable by the buyer and does not transfer responsibility. The obligation sits with whoever makes the call.

The regulations provide for real consequences, and it is worth describing their shape while being careful about specifics.

The framework operates largely through the telecom operators. Senders and telemarketers must be registered, complaints are attributed to a sender, and repeated violations lead to escalating financial disincentives and ultimately to blacklisting and disconnection of the resources used to make the calls. For a business that depends on a number its customers know, losing it is a more serious outcome than a monetary penalty.

The specific monetary amounts, the number of complaints that triggers each stage, and the current escalation schedule are set out in TRAI's own regulations and amendments and have been revised more than once. Figures circulating in secondary summaries are frequently out of date, and this article deliberately does not repeat any of them. A business that needs the current numbers should read TRAI's published regulations directly.

There is also the non-regulatory consequence, which for a small business is often larger: a local reputation for calling people who did not want to be called.

Most small businesses calling their own customers, about their own relationship, on numbers those customers gave them for that purpose, are in a straightforward position. The problems arrive with prospecting.

A defensible practice has a few elements. Record how each number was obtained, and when, alongside the number itself — this single habit answers the question that matters when anything is disputed. Record what the person agreed to, in specific terms. Honour a request to stop immediately and permanently, and keep that record too. Avoid purchased lists, on the grounds above. And where consent has to meet the explicit standard, understand that this involves registration on the DLT platform rather than an internal record.

For anything at scale, this is a matter for someone with telecom compliance expertise and TRAI's current published regulations, not an article. The framework is amended periodically and the details change.

Automix's Wani is a planned voice follow-up agent, documented at /docs/wani. It is not available to customers, and no calls are placed by it today.