Compliance Guide

The Seven Day Rule: How TRAI's Inquiry Window and Legacy Consent Rules Change Indian Lead Follow-Up in 2026

One sentence in TRAI's 2026 amendment turns a form fill into a seven day licence, and only if you can produce the record afterwards. For every Indian lead generation team running a two week nurture sequence, this is the rule that changes process.

Distk Editorial Nov 2026 15 min read

TRAI's TCCCPR Third Amendment, introduced on 18 September 2026, permits commercial communication on the basis of a customer inquiry for only seven days from the date of that inquiry. The inquiry must be made in writing or through digital means and must be maintained by the sender in a verifiable form. TRAI says the provision is intended primarily to facilitate e-commerce and e-service platforms. The practical effects are three. The window runs from the inquiry date, not from when your team first acted on the lead. Lead sources that leave no digital artefact, such as inbound phone calls and event business cards, need a record created at the time or they cannot support this basis. And anything past day seven needs consent or a fresh inquiry, which means consent has to be requested inside the window rather than assumed after it. Older consent still counts, but only where it was obtained through verifiable means and is registered on the TSP Digital Platform.

What Is the Seven Day Inquiry Rule in 2026?

Under TRAI's TCCCPR Third Amendment, introduced on 18 September 2026, commercial communications may be sent to a customer on the basis of an inquiry the customer made "only for a period of seven days from the date of such inquiry". The inquiry must be made in writing or through digital means, and the sender must maintain it in a verifiable form. TRAI states the provision is intended primarily to facilitate e-commerce and e-service platforms.

Two things are being granted and limited at the same time. An inquiry is now an explicit lawful basis for commercial communication, which is useful. That basis expires after seven days and only exists if you can produce the record, which is the part that rewrites follow-up process for most Indian lead generation teams.

Not legal advice

This guide summarises TRAI Press Release No. 119 of 2026 and the amendments it describes. It is not legal advice. Before you change a consent flow, a dialer configuration or a contract, confirm your own obligations against the text of the Telecom Commercial Communication Customer Preference (Third Amendment) Regulations, 2026 or with counsel. Where the press release does not state a detail, this guide says so rather than filling the gap.

Why Does a Seven Day Window Change Indian Lead Follow-Up in 2026?

Because most follow-up sequences were built around attention, not around a legal clock. A typical Indian lead nurture flow runs for weeks: an immediate response, a reminder at day three, a case study at day seven, a last-chance message at day fourteen, then a reactivation attempt a month later. Everything past day seven now needs a basis other than the inquiry that started it.

The commercial reality is that this mostly affects the tail, not the head, of a sequence. Response rates on inquiry-based follow-up are highest in the first hours and days, which is where the window sits. What it ends is the habit of treating one form fill as a licence to message somebody indefinitely, which was never good practice and is now specifically bounded.

Follow-up stageInside the 2026 inquiry basis?What to do instead
Immediate acknowledgement and responseYesNothing changes. This is the strongest moment anyway.
Day two or three reminderYesNothing changes.
Day seven final touchYes, on day seven from the inquiry dateCount from the inquiry date, not from first contact.
Day ten or fourteen messageNo, the inquiry basis has expiredNeeds consent, or a fresh inquiry from the customer.
Monthly reactivation campaignNoConsent basis, registered appropriately.
A new inquiry from the same personYes, a new seven day windowLog the new inquiry as its own record.

What Counts as an Inquiry You Can Rely On in 2026?

The press release sets two conditions and no more: the inquiry "shall be made in writing or through digital means", and it "shall be maintained in a verifiable form by the Sender". It does not enumerate acceptable channels, prescribe a record format, or specify a retention period. What it establishes is that an inquiry you cannot evidence is an inquiry you cannot rely on.

Read against how Indian businesses actually capture interest, that draws a practical line between two groups of lead sources. One group produces a digital artefact by default. The other depends on somebody remembering a conversation.

Lead sourceProduces a written or digital record?What to fix in 2026
Website form submissionYes, with timestampConfirm the timestamp is stored and retrievable, not just emailed onward.
WhatsApp inbound messageYesMake sure the thread is retained in your platform, not only on a handset.
Chat widget or bot conversationYesCheck transcripts are archived and linked to the contact record.
Email inquiryYesLink it to the CRM record so the record survives staff changes.
Marketplace or portal leadUsually, via the platformConfirm you can export the underlying inquiry, not just the contact.
Inbound phone callNot by itselfCreate a digital record at the time of the call. A memory is not a verifiable form.
Business card at an eventNoTreat as a consent exercise, not an inquiry.
Purchased or scraped listNoNo inquiry exists. This provision does not help you.

How Should You Rebuild a Sequence for the 2026 Rule?

Split the sequence at day seven and give each half its own basis. The first half runs on the inquiry and needs the inquiry record attached. The second half runs on consent, which means you have to earn that consent during the first seven days rather than assume it.

  1. Stamp the inquiry date on the record, not the date your team first got to it. The window runs from the inquiry.
  2. Make day one to seven do the work. If a sequence needed fourteen days to land, the problem is usually the offer or the routing speed, not the number of touches.
  3. Ask for consent inside the window, clearly and separately, if you want to keep communicating after it. An inquiry is not consent, and the amendment treats them as different bases.
  4. Move long nurture onto the consent basis, with whatever registration your operator requires, rather than running it off an expired inquiry.
  5. Handle repeat inquiries as new events. A returning visitor who submits again opens a fresh window, and the new record is what supports it.
  6. Make expiry automatic. A rule in your CRM or automation platform that stops inquiry-based messaging at day seven is more reliable than a policy document.

What Does This Mean for Real Estate, EdTech and Insurance in 2026?

These sectors feel it most, because their sales cycles are far longer than seven days while their lead capture is inquiry-driven. A property inquiry might convert over three months. An insurance comparison might convert at renewal. The seven day window does not shorten the sales cycle, it shortens how long you can pursue it on the inquiry alone.

The workable pattern is to treat the first seven days as the period in which you convert an inquiry into either a conversation or a consent. A prospect who replies and engages is in a conversation, which is a different thing from unsolicited commercial communication. A prospect who goes quiet needs a consent you obtained while you still had a basis to ask. Our lead nurturing guide covers the mechanics of shorter, denser sequences, and the full amendment guide sets this rule in context with the other changes.

What the press release does not say

It does not define how long the verifiable record must be retained, what format qualifies as verifiable, or whether a reply from the customer inside the window extends it. It also does not state a separate commencement date for this provision. Those are questions for the regulation text or counsel, and this guide does not guess at them.

How Does the Seven Day Rule Interact With the Complaint Trigger in 2026?

Directly, and this is the part worth understanding. Messaging outside a valid basis is what generates complaints, and under the same amendment, action triggers against a sender at three or more unique complaints in ten days where the sender's CLI is also flagged by the operator's AI or ML system. A sequence that runs past day seven is manufacturing exactly the complaint pattern that now triggers action sooner than it used to.

The inverse is also true and more useful: tight, well-evidenced, in-window follow-up produces fewer complaints, and fewer complaints keeps you below a threshold that has become easier to cross. Compliance and deliverability point the same direction here, which is not always the case with regulation.

How Do You Evidence an Inquiry Months Later in 2026?

By storing the artefact, not the interpretation of it. A verifiable form means something a third party could examine: the submitted form data with its timestamp, the message thread, the chat transcript, the email. What will not serve is a CRM field reading "enquired about pricing" typed by a salesperson, because that records a conclusion rather than the customer's act.

Most Indian marketing stacks fail this quietly. A form posts to an automation tool, which creates a contact and fires a notification, and the original submission is never persisted anywhere durable. The contact survives, the inquiry does not. The fix is usually a configuration change rather than a new system: persist the raw submission against the contact, keep the timestamp, and make sure both are exportable by someone who is not the person who built the flow.

What to storeWhy it matters in 2026
The inquiry date and timeThe seven day window is measured from it, so it is the operative fact.
The channel the inquiry arrived throughEstablishes that it was written or digital.
The content the customer submitted or sentEvidences that an inquiry about goods, products or services was actually made.
The identifier the inquiry was made toTies the inquiry to your business as the sender.
Any consent captured separatelyKeeps the two bases distinguishable, which matters once the window closes.

Does the Seven Day Rule Apply to WhatsApp and Email Too?

The amendment regulates commercial communication under the TCCCPR framework, which governs telecom resources: SMS and voice calls placed through Indian telecom operators, with headers and templates registered on the DLT platform. The press release addresses commercial communications, senders, telemarketers and access providers in that context, and does not extend its stated scope to over-the-top messaging or email.

That distinction is worth stating precisely rather than confidently. What the press release does not do is carve out other channels or make any claim about them. Separately, WhatsApp's own platform rules and its opt-in requirements govern business messaging there, and email marketing in India sits under different law again. The safe operating position for a marketing team is to treat the seven day discipline as good practice everywhere, because a lead who has gone cold responds no better on WhatsApp than on SMS, while confirming the legal scope of each channel against its own rules. Our WhatsApp Business API guide covers the platform side.

Conditionally, yes. TRAI's TCCCPR Third Amendment, introduced on 18 September 2026, expands the definition of consent to include legacy consents already available with entities, and the framework is being amended to enable their recognition and digitisation. The condition is strict: legacy consents "shall be considered valid only where they have been obtained through verifiable means and are subsequently registered on the Digital Platform of the TSPs".

This is one of the few genuinely permissive changes in the amendment, and it is also the one most likely to be misread as easier than it is. Recognition is not automatic. It depends on two tests, and most brands can pass neither without work: proving how the consent was obtained, and registering it on operator infrastructure.

Not legal advice

This guide summarises TRAI Press Release No. 119 of 2026 and the amendments it describes. It is not legal advice. Before you change a consent flow, a dialer configuration or a contract, confirm your own obligations against the text of the Telecom Commercial Communication Customer Preference (Third Amendment) Regulations, 2026 or with counsel. Where the press release does not state a detail, this guide says so rather than filling the gap.

What Are the Two Conditions for Legacy Consent?

Obtained through verifiable means, and subsequently registered on the Digital Platform of the TSPs. Both must hold. A consent that was captured properly but never registered does not qualify, and a consent registered without a verifiable capture record does not qualify either.

ConditionWhat the press release saysWhat it asks of a brand
Verifiable meansLegacy consents are valid only where "they have been obtained through verifiable means"Evidence of how each consent was captured, not just that it exists.
RegistrationAnd "are subsequently registered on the Digital Platform of the TSPs"Getting the records onto operator infrastructure, which is a process question for your TSP.
ScopeThe consent definition is "expanded to include legacy consents already available with the entities"It applies to consent you already hold, not to consent you can reconstruct.
Mechanism"The framework is being amended to enable the recognition and digitization of such legacy consents"The route exists in principle; the operational detail sits with the regulation and your operator.

What Counts as Verifiable Means?

The press release does not define the term, and that matters enough to state plainly rather than fill in. What it does establish is the direction of the test: the question is how the consent was obtained, which means the evidence has to describe the act of consenting rather than merely record a conclusion.

Applied to how Indian businesses actually hold consent, that separates records that carry their own evidence from records that depend on somebody's word. A database column reading "opted in: yes" is a conclusion. A stored submission with a timestamp, the wording the customer agreed to, and the channel it came through is closer to evidence of the act.

How consent was capturedDoes it carry its own evidence?What to check in 2026
Web form with stored submission and timestampUsually yesConfirm the raw submission and consent wording are retained, not just the contact record.
App onboarding with logged acceptanceUsually yesCheck the log ties the user, the timestamp and the version of the wording.
Signed contract or form with a consent clauseOften yesMake sure the document is retrievable and linked to the phone number, not filed by customer name alone.
Double opt-in email or SMS confirmationUsually yesRetain the confirmation event, not just the resulting status.
CRM checkbox ticked by a staff memberNoRecords a conclusion, not the customer's act. Treat as unevidenced.
Verbal consent noted on a callNot by itselfUnless there is a retained recording or logged confirmation, there is no record of the act.
Consent inferred from a past purchaseNoA transaction is not a consent to commercial communication.
Imported or purchased listNoNo consent was obtained by you, verifiably or otherwise.

How Should a CRM Owner Approach This?

As a data project with a triage step at the front. The instinct is to treat the whole database as one question, but the useful first move is to sort the records by how they were captured, because that determines whether a record is a candidate at all.

  1. Segment by capture method, not by recency. Age is irrelevant to the test. How the consent was obtained is the whole question.
  2. Find out what your systems actually retained. Many Indian stacks keep the opt-in status and discard the submission that produced it, which leaves you with a conclusion and no evidence.
  3. Separate the evidenced from the unevidenced. Be honest in this step. A large unevidenced segment is better known now than discovered during an enforcement question.
  4. Ask your TSP about the registration route. Registration on the Digital Platform is an operator process, and the press release does not describe its mechanics.
  5. Plan re-consent for the unevidenced segment. Where no verifiable record exists, the realistic path is to obtain fresh consent rather than to argue for the old one.
  6. Fix capture going forward. Every new consent should produce a retained artefact: the wording, the timestamp, the channel and the identifier it was given against.
What the press release does not say

It does not define verifiable means, does not describe the registration process on the TSP Digital Platform, does not state a deadline for registering legacy consents, and does not say what happens to unregistered legacy consents in the interim. It also publishes no retention requirement for the underlying evidence. These are questions for the regulation text, your telecom provider, or counsel.

How Does Legacy Consent Differ From the Inquiry Basis?

They are separate bases with different lifespans, and conflating them is a common error. Consent, once validly held and registered, is not time limited in the way the inquiry basis is. The inquiry basis under the same amendment permits commercial communication for only seven days from the date of a customer inquiry, and requires the inquiry to be made in writing or digitally and kept in verifiable form.

That difference shapes sensible process. A form fill gives you seven days. Consent gives you an ongoing basis. The practical move for most Indian teams is to use the seven day window to ask for consent explicitly, so a short-lived basis converts into a durable one. Our seven day rule guide covers that mechanic, and the full amendment guide places both inside the wider framework.

Notice also that both provisions use the same word. Verifiable form for an inquiry, verifiable means for a consent. Whatever the regulation settles on as evidence, a business that retains the artefact behind every customer action satisfies both tests, and one that stores only outcomes satisfies neither.

What Are the Common Mistakes?

What Are the Common Mistakes in 2026?

Key Takeaways for 2026

The seven day rule is a narrow permission with a hard edge, and the record keeping matters as much as the timing.

Distk rebuilds inquiry-based follow-up for Indian teams so the cadence fits the window, the records survive scrutiny, and consent gets asked for while there is still a basis to ask. If your nurture sequence runs longer than a week off a single form fill, that is the first thing we would look at.

Sources

TRAI Seven Day Inquiry Rule: FAQs

How long can I message a lead after they inquire in India in 2026?

Seven days from the date of the inquiry, under TRAI's TCCCPR Third Amendment introduced on 18 September 2026. The window runs from the inquiry itself, not from when your team first responded, so a lead that waited three days in a queue has four days of the basis left.

What counts as an inquiry under the TRAI 2026 rule?

The press release requires that the inquiry be made in writing or through digital means, and be maintained by the sender in a verifiable form. It does not enumerate acceptable channels or prescribe a record format. In practice, form fills, WhatsApp messages, chat transcripts and emails produce a record by default, while an inbound phone call does not unless you create one.

Is an inquiry the same as consent under the 2026 amendment?

No. The amendment treats them as separate bases. Consent, including recognised legacy consent, does not expire after seven days, whereas the inquiry basis does. If you want to keep communicating after day seven you need consent, and the sensible time to ask for it is inside the window while you still have a basis to make contact.

Does a customer replying to my message extend the seven day window?

The press release does not say that it does. It states the basis lasts seven days from the date of the inquiry and sets no extension mechanism. Do not build a process on an extension the source does not provide; check the regulation text or take advice if this matters to your flow.

Can I use the inquiry rule for a purchased contact list?

No. The basis exists only where the customer made an inquiry to the sender, evidenced in writing or digital form. A purchased or scraped list contains no inquiry, so this provision does not apply to it.

What happens if I keep messaging after seven days?

The press release does not publish a specific penalty for this provision. What it does establish elsewhere in the same amendment is that action triggers against a sender at three or more unique complaints within ten days where the sender's CLI is also flagged by the operator's AI and ML system, so out-of-window messaging feeds the mechanism that now acts sooner.

Is existing customer consent still valid in India in 2026?

Conditionally. TRAI's 2026 amendment recognises legacy consents already held by entities, but states they are valid only where they have been obtained through verifiable means and are subsequently registered on the Digital Platform of the TSPs. Both conditions must be met.

Fit the cadence to the window, not the other way round

Distk rebuilds inquiry-based follow-up for Indian teams: cadence that lands inside seven days, inquiry records that survive scrutiny, and a consent ask placed while there is still a basis to make it.

Start the conversation →