AI Voice Agent for Insurance: Renewals, Lead Qualification and the IRDAI Rules That Apply

Insurance runs on calendars. Every health, motor and life policy has a due date, and a reminder that goes out late, or never, ends in a lapsed policy. An AI voice agent for insurance can take on this work, but only if it is built around the rules on who may call, from which number, with what consent and what must be on record.

Those rules come from three places. IRDAI's distance marketing guidelines set what a tele-caller must say and record. TRAI's telecom rules decide the number series and consent a call needs. The Digital Personal Data Protection (DPDP) Act and its 2025 Rules govern the personal data a call collects and stores. None was written with synthetic voices in mind. This is an engineering guide, not legal advice, and it flags where interpretation is open.

Three Insurance Call Types, Three Rulebooks

The first design decision is classifying each call by its purpose and content, because it decides the number series, consent and how much the agent may do.

Renewal and premium-due reminders go to existing policyholders. A reminder limited to the due date, expiry date and payment information is the clearest service call. It stops being one once it pitches an upgrade, rider or other product: under TRAI's rules, promotional content mixed into a service call makes the whole call promotional, and promotion must not be disguised as service.

For health policies, IRDAI's Master Circular on Health Insurance Business (29 May 2024) sets a grace period of 15 days for monthly premiums and 30 days for quarterly, half-yearly or annual premiums. When premium is paid in instalments during the policy period, cover continues through the grace period. When a policy has expired, renewing within the grace period protects continuity benefits such as waiting-period credit and no-claim bonus, but the circular does not say a claim in the gap is covered. Never tell a customer they are covered after expiry.

Lapsed-policy revival calls are not automatically service calls. The classification depends on the actual contractual status, purpose and content of the call. A call introducing a new policy or product is promotional where applicable. Send revival scripts to legal review before launch.

Lead qualification calls go to prospects who filled in a quote form or asked for a callback. TRAI's explanatory memorandum to its 2025 amendment treats prospects who showed interest but have not purchased as promotional, so a quote-form callback is not automatically a service call. A conservative design keeps the AI to qualification and booking the follow-up.

What IRDAI's Distance Marketing Rules Require

IRDAI's Guidelines on Distance Marketing of Insurance Products (5 April 2011, applicable from 1 October 2011) list voice mode, including telephone calling, as a distance marketing mode. IRDAI's portal still hosts them and we found no repeal, but we have not confirmed that they apply to every distribution model, so confirm current force with counsel. They cover solicitation and sale and are silent on pure service reminders. For solicitation calls, the text requires:

• the insurer's name and the purpose of the call, such as lead generation or solicitation, highlighted at the start;
• proceeding only on the customer's consent “in explicit terms”;
• the caller's name and a language option, continuing only in the language chosen;
• notice that the call is recorded, and that the client is entitled to a voice copy at any time during the term of the policy or until satisfactory settlement of a claim, whichever is later.

Clause 6 limits who may solicit and conclude a sale, so duties differ between insurers and intermediaries. For corporate agents, regulation 25 of the IRDAI (Registration of Corporate Agents) Regulations, 2015 applies Schedule VII, which IRDAI still lists among its current regulations. Paragraph 7.2 requires the corporate agent's and insurers' names and the purpose of solicitation to be highlighted. Paragraph 7.3 requires explicit consent, an authorised verifier's name and certificate number, language options, a recording announcement and the voice-copy entitlement. These are corporate-agent requirements, so do not assume they apply identically to direct insurers, brokers or other channels.

Translating the disclosures for an AI caller

The text does not say whether a bot satisfies the “name of the caller” requirement, so disclose more than the minimum, before the first question: the insurer, the purpose, that an automated assistant is calling, recording and a language choice.

For example: “Namaste, this is Asha, an automated assistant calling from [insurer] about your health policy renewal. This call is recorded. Would you like to continue in Hindi or English?” Your compliance team owns the approved wording, and the language option has to be real: if the customer replies in Tamil, the agent carries on in Tamil.

The voice copy is a storage requirement

Beyond the voice-copy entitlement, clause 12 requires the insurer to preserve a voice or electronic record of the process from lead generation or solicitation to sale for six months beyond the policy term or until satisfactory settlement of a claim, whichever is later. Paragraph 10 of Schedule VII sets the same period for corporate agents. For a multi-year policy, a recording may need to outlive your default retention setting by years. That sits uneasily with DPDP's data-minimisation principle, so take legal advice on the balance.

Number Series, Consent and the DPDP Clock

On 16 December 2025, TRAI directed access providers that IRDAI-regulated entities must adopt the 1600 series by 15 February 2026, and may not initiate service or transactional voice calls from other numbers after that date, “even with the explicit or inferred consent of customers”. That deadline has passed.

TRAI's press release of 10 July 2026 clarifies the split. 1600xx numbers are for service and transaction calls to existing customers by BFSI regulated entities, including IRDAI-regulated ones, and by government entities. 140xx numbers are for promotional calls by any sector, and those callers must register with telecom service providers under the TCCCPR framework. TRAI's documents do not define the “xx”, so confirm your exact numbers with your telecom provider.

The table is one reading, not a legal classification; call content can change the answer.

Call type	Likely category	Number series	Consent basis
Renewal reminder: due date, expiry, payment information only	Service	1600xx	Existing policy relationship
Renewal call that adds an upsell or cross-sell	Promotional	140xx	Prior promotional consent
Revival call explaining how to restore a policy	Depends on contract status, purpose and content	1600xx only if classed as service	Legal review before launch
Revival call introducing a new policy or product	Promotional	140xx	Prior promotional consent
Quote-form callback or lead qualification	Promotional	140xx	Promotional consent, or a verifiable enquiry

Consent and A2P declaration under the amended TCCCPR

TRAI's February 2025 and September 2026 (Third Amendment) TCCCPR amendments matter here. The Third Amendment Regulations 2026 are printed in the Official Gazette dated 18 September 2026. Under Regulation 1(3), the general provisions commence after 30 days from publication and Regulation 4, which introduces advance declaration of A2P calling use and CLI ranges, after 60 days. Counting from the printed issue date gives 19 October and 18 November 2026. However, the electronic Gazette record indicates a later upload on 28 September 2026, and the legal significance of that difference needs confirmation. The general provisions have commenced on either reading, and the declaration takes effect no earlier than 18 November 2026. Insurers and their calling partners should prepare to complete the declaration by 17 November 2026, or immediately if that date has passed, and confirm the applicable commencement date with their legal or telecom compliance team.

• Explicit consent obtained to facilitate a commercial transaction involving the ongoing purchase or use of the sender's product or services is valid for seven days or until revoked, whichever is earlier, renewable by the customer. It is not a general service-call or promotional-consent period.
• The amendment deletes the former proviso that tied deemed (inferred) consent to the duration or discharge of the contract, and revises “Relationship”: a prior or existing commercial relationship, a qualifying enquiry within the preceding seven days, or a qualifying application within the preceding three months. In the notified text we reviewed, the contract-duration limit is not clearly carried into that definition. Whether a lapsed policyholder still qualifies, and whether a given renewal or revival call is permissible, depends on the facts, the call's purpose and the applicable service or promotional consent rules, so have legal or compliance review your workflow.
• The seven-day explicit-consent period for service calls is a separate rule from these Relationship windows. An enquiry must be made in writing or digitally and kept in verifiable form, and the windows cover customer-initiated enquiries and applications, not cold lists or every promotional call.
• TCCCPR consent is distinct from DPDP consent; DPDP duties remain.

Four obligations are separate. Promotional senders register with their telecom provider, providers assign number series, every sender must declare A2P use in advance to its originating access provider with the CLI ranges (Regulation 4), and consent is independent of all three. An A2P call is a voice call initiated by an application or automated platform without direct human dialling, including autodialling, robo-calls and pre-recorded or artificial voice, so an outbound AI campaign will likely qualify. The definition is among the general provisions, but the advance declaration is in the later group. Once it applies, an undeclared A2P call is treated as unsolicited commercial communication. The 2025 amendment already required advance written notice of auto-dialler or robo-call use and its objective.

For violations, action escalates from warnings and usage caps to disconnection of all telecom resources for up to two years and blacklisting, aimed at unregistered or non-compliant senders. AI is not itself a violation, but AI calls are not exempt.

The DPDP timeline

The DPDP Rules, 2025 (G.S.R. 846(E), printed in the Gazette dated 13 November 2025) apply in stages under Rule 1. Rules 1, 2 and 17–21 have applied since 13 November 2025. Rule 4, on Consent Manager registration, is scheduled for 13 November 2026. Rules 3, 5–16, 22 and 23, which include Rules 6, 7 and 8, are scheduled for 13 May 2027, so most substantive obligations are not yet in force. The eGazette record is dated 14 November 2025. Corrigendum G.S.R. 892(E) of 10 December 2025 replaces “date of publication of this Gazette” in Rule 1(3) and 1(4) with “date of publication in the Official Gazette”. That clarifies the wording but does not by itself resolve whether the printed date or the date the Gazette became publicly available controls, so confirm the date with counsel.

Rule 3 requires standalone, plainly worded consent notices itemising data and purposes, with a way to withdraw consent. Rule 7 requires a breach to be reported to affected people without delay, to the Data Protection Board without delay, and in a detailed report within 72 hours unless the Board allows longer. Three retention and erasure provisions are separate. Rule 6(1)(e) is a security safeguard: retain logs and personal data for one year to detect, investigate and remediate unauthorised access and continue processing after a compromise, unless another law requires otherwise. Rule 8(3) requires personal data, associated traffic data and processing logs to be kept for at least one year from processing “for the purposes as specified in the Seventh Schedule”, which are State-use purposes such as the security of the State, functions under law and Significant Data Fiduciary assessment, then erased unless another law or a Government notification requires more. The rule’s own illustrations apply it to ordinary commercial records such as an e-book order, so its reach to insurer call data is unsettled and needs counsel. Rule 8(2), a 48-hour erasure notice, applies only to the classes in the Third Schedule: e-commerce entities with at least two crore registered users, online gaming intermediaries with at least 50 lakh and social media intermediaries with at least two crore. It does not automatically apply to insurers. None of these is a rule to keep every insurance call recording for one year.

Configuring an AI Voice Agent for Insurance

On Zoice, outbound voice agents capture a yes/no confirmation to continue the conversation in the first five seconds and record it against the call, which supports configurable consent capture and call-level records. That confirmation is neither TRAI promotional consent nor DPDP consent, and promotional calls still need prior consent in place before dialling. These features are configurable, depend on your setup and available regions, and do not by themselves make a campaign compliant. Recording redaction strips selectable patterns such as Aadhaar, PAN and OTP before transcripts reach storage.

Retention windows are set separately for conversations, recordings and audit logs, so the recordings window can follow your voice-copy period; confirm with Zoice that the window you need is supported. The security page covers data residency; confirm which regions are available.

Your telecom provider assigns number series, not the AI platform. SIP/BYOC trunking lets you run calls over your carrier's trunk. Confirm with your carrier and Zoice that outbound calls present the 1600xx number as caller ID, and keep service and promotional traffic on separate trunks.

During the call:

• Language per contact: each contact in a CSV upload can have their own language, and agents detect a switch mid-call and reply in the customer's language.
• Grounded answers: attach policy wordings as a knowledge base so answers carry source references, and switch on hallucination detection so unsupported answers are flagged for review.
• Human hand-off: the transfer_number tool moves the call to a human phone number with an optional announcement. Trigger it for advice, purchase or complaints, routed to a suitably authorised and trained human representative, as your distribution model requires.
• Structured outcomes: define extraction fields such as renewal_intent and objectives such as “recording announced” or “language offered”, for auditable results.

Call analytics reports each conversation's objective results, and the compliance use case checks calls against your compliance script, flags deviations and produces timestamped transcripts and downloadable audit reports.

Frequently Asked Questions

Is it legal to use AI voice agents for insurance renewal calls in India?

We found no IRDAI rule that specifically addresses AI callers, and TRAI's A2P rules expressly cover artificial voice calls. This post does not settle the legal question. Assume duties for any tele-caller also apply to an AI agent, and have counsel sign off before launch.

Which number series should renewal reminders and lead calls use?

Per TRAI, 1600xx is for service calls to existing customers and 140xx for promotional calls, and AI campaigns likely need an A2P declaration to your provider once Regulation 4 takes effect, which counting from the printed Gazette date is 18 November 2026; counsel should confirm the controlling date. A renewal reminder with only due date, expiry and payment information is typically a service call. Upsell, cross-sell and lead qualification are promotional. Confirm your numbers with your telecom provider.

Can a customer ask for the recording of an insurance call?

For solicitation calls under the 2011 guidelines, yes: for the policy term or until satisfactory claim settlement, whichever is later, and the caller must say the call is recorded.

Can an AI telecaller sell a policy, or only qualify leads?

The guidelines are silent on automated agents completing a sale and restrict who may solicit and conclude one. Conservatively, let the AI handle reminders, qualification and scheduling, and transfer advice or purchase to a suitably authorised and trained human representative, as your distribution model requires. That is a recommendation, not a legal prohibition.

When do the DPDP Rules start applying to insurance calling programmes?

Some already do; Rule 4 is scheduled for 13 November 2026, and Rules 3, 5–16, 22 and 23 (including Rules 6, 7 and 8) from 13 May 2027, as set out above and per the MeitY-hosted Gazette. Most substantive obligations are not yet in force.

To check your call flows against these rules, talk to our team.