Using WhatsApp as a Client Service Channel Without Breaching IRDAI Conduct Rules

A point of sales person in India does almost nothing on a desktop. The client book lives in a phone: a renewal reminder typed at 9 pm, a policy PDF forwarded to a client's brother, a voice note in Bhojpuri explaining an add-on. None of the instruments governing the POSP channel mention chat. The non-life and health guidelines (Circular No. IRDA/Int/GDL/ORD/183/10/2015), the two November 2016 life guidelines and the life master circular (IRDAI/LIFE/CIR/MISC/215/12/2019) were drafted around proposals, POS Codes, training hours and product lists. They say nothing about a broadcast list.

That silence is not permission. The conduct requirements those instruments impose (ethical selling, no push-selling, proper disclosure, no misleading representation of the policy) are written about your behaviour, not your medium. A statement that would be misleading on a printed leaflet is misleading in a chat bubble. The medium changes two things, both for the worse: chat is faster than judgement, and chat is a permanent, timestamped record held by the other party.

The useful model is not "is WhatsApp allowed." It is: every message you send is either servicing an existing contract, or it is sales material. Servicing is free. Sales material is not. Almost every advisor who gets into trouble here does so by drifting from one into the other inside the same thread, without noticing the moment it happened.

The operative constraint is stricter than most advisors assume. A POSP may not issue or publish any advertisement or sales material without the prior approval of both the engaging entity and the insurer. Not one of them. Both.

Read that as written. It does not say "advertisements in newspapers," and it carves out nothing for digital, informal or small. If what you are about to send solicits business, it needs clearing first, by the entity that engages you and by the insurer whose product it describes. If you are tied to an intermediary, that is two approvals travelling at two speeds, which is why advisors stop asking and start improvising.

Where judgement lives:

• A client asks when their motor policy expires and you reply with the date. Servicing. No approval question arises.
• You design a poster comparing three insurers' term plans, add your number, and put it on your WhatsApp Status. Sales material. Unapproved, and it spans insurers you are not tied to.
• A client asks "what does zero depreciation cover," and you paste three paragraphs you wrote yourself describing the add-on's benefits. This is the ambiguous middle, and it is the most common exposure in the channel.

The safe resolution of the middle is structural rather than clever: do not write product descriptions. Send the insurer's approved language, and use your own words only for facts specific to that client's contract (their expiry date, their sum insured, their pending document, what their endorsement will cost). Your own words about the product need clearing. Your own words about their policy are servicing.

Advisors treat these as four ways to send the same text. They differ in how easily servicing turns into publishing.

One-to-one messages are the lowest-risk surface, because the content is naturally specific to one contract. "Your policy 3401xxxxxx expires 22 August, premium INR 14,320, shall I send the renewal link" cannot easily be called an advertisement.

Broadcast lists are where the drift happens. The interface feels private (the recipient sees a direct chat) while the content is necessarily generic, because it must apply to 200 people at once. Generic content that solicits business, sent to a list, is publishing wearing a private-message costume. A broadcast reading "August is renewal month, message me for the best rates" is unapproved sales material sent to 200 people, regardless of how it renders on their screen.

Groups add other people's content on top. A client group you admin accumulates forwards from members: competitor material, half-remembered claim advice, rate rumours. You cannot approve what other people post, and your silence beside a wrong statement in a group you run is a poor position to defend later.

Status is unambiguously publishing: an audience, one-to-many, tied to no contract, designed for promotion. Everything there is sales material and needs approval on the same terms as a hoarding.

The rule that survives a real working day: one-to-one for anything specific to a client's contract, approved material only for anything generic that mentions a product, benefit, rate or invitation to buy, and nothing on Status or in groups that was not cleared. Operational notices with no product content ("I am travelling 12 to 14 August, claims intimation is still 1800-xxx-xxxx") can go by broadcast.

The habit that removes most of the risk here costs nothing: stop writing your own creative.

Insurers produce approved collateral in volume, in multiple languages, sized for chat: product one-pagers, benefit-illustration templates, claim-intimation cards, renewal notices. Every one has already passed the approval your own poster has not. Forwarding it is a different act, legally and practically, from designing something similar.

The temptation runs the other way because insurer creative is often bad: too long, too English, too corporate, and it does not carry your name. Advisors respond by rebuilding it in Canva with their photo, their number and a punchier line. That single act converts approved material into unapproved material, and makes you the issuer of a piece nobody has cleared.

Three failure patterns:

• Cross-insurer comparisons. You are tied to one principal at a time. A POSP tied to an insurer can market only that insurer's approved POS products; a POSP tied to an intermediary works within the products that intermediary is authorised to place. A self-made comparison chart across insurers is unapproved by definition, since nobody who could approve it has authority over the whole chart.
• Off-list products. You may solicit only products approved as POS products, so a forwarded message about anything outside that set is a problem before the approval question arises. The operative list sits on IRDAI's POS page, and has expanded beyond the original motor, travel, personal accident and home set to include certain health and rural covers. Check it against what your principal has authorised for you, not what you remember.
• The forwarded-forward. Material that reached you through three advisor groups is not approved material, it is material that looks like it. If you cannot say which insurer released it and when, do not send it.

One pattern is not a grey area at all, and advisors cross it weekly.

"Sir, book through me and I will give you 15% off the first-year premium."

That is rebating. Section 41 of the Insurance Act, 1938 prohibits offering, as an inducement to take out or renew a policy, any rebate of the commission payable or of the premium shown on the policy, except where the insurer's published prospectuses or tables expressly allow it. A "first-year premium discount" funded out of your own remuneration is exactly what the section names. The maximum fine is INR 10 lakh, raised by the Insurance Laws (Amendment) Act, 2015, and the section reaches the policyholder who knowingly accepts the rebate, not only the person offering it.

What makes chat dangerous is not that the offer is more illegal in writing. It is that a spoken offer evaporates and a typed one does not. A rebate pitch in a thread is a dated, attributed, forwardable admission that sits on the client's phone for years and reaches your principal's compliance team the first time that client disputes a claim and starts sending screenshots.

The related prohibition is just as firm: a POSP may not pay any fee, commission or incentive, by whatever name, to any person or entity for sale, introduction, lead generation, referral or finding of business. "Bhai, send me 5 names and I will give you INR 500 each" in a group is exactly that arrangement, and every message is evidence of it. Each policy placed under it can count as a separate instance.

Advisors often read the liability structure as protection. It is the opposite.

The framework puts responsibility for a POSP's conduct on the entity that engages them. Under the life master circular, the life insurer is responsible for the conduct of the POSP representing it, and misconduct makes the insurer liable to penalty under Section 102 of the Insurance Act, 1938. Where you are engaged by an intermediary, the intermediary carries that responsibility and exposure.

Follow the incentive. Your principal is exposed to a penalty for something you typed at 11 pm on your own phone, in a language their compliance team may not read, in a thread they cannot see. There is one way to manage that risk, and it is contractual: prescribe what you may send, require approved material, reserve the right to inspect, terminate on breach. That is why your engagement contract, not the guidelines, is where your day-to-day WhatsApp rules live. Read it. Most advisors have never opened theirs past the remuneration clause.

So the enforcement to plan for is not a regulator at your door. The visible Section 41 and conduct penalties land on insurers and intermediaries, because they are the ones the framework holds responsible. Your realistic downside is your principal terminating the engagement and your POS Code going dark, which for a POSP tied to one principal at a time means the book stops earning that week.

Client data deserves a line. When you hold a client's Aadhaar photo, PAN and claim documents in a chat backup, you are handling personal data on behalf of the insurer or intermediary that engages them. That entity carries the data-protection obligations, and will push consent, retention and breach-notification requirements down to you through the same contract, ahead of the November 2026 and May 2027 enforcement dates under the Digital Personal Data Protection Act, 2023 and its 2025 Rules.

Record-keeping is framed to advisors as a burden. Here it is the opposite: the thread is the only evidence you will ever have that you sold properly.

A POSP is required to collect and maintain KYC documentation and product sales records, and to submit KYC documents and declarations truthfully and promptly to the engaging entity. Note what that means on a phone. If the client's proof of identity arrived as a WhatsApp image and was never moved anywhere else, your KYC record is a chat backup that vanishes when you change handsets and that your principal cannot produce on demand.

Worth keeping, in a form that survives your phone:

• The disclosure moment. The message where you sent the approved benefit illustration or one-pager, with its timestamp. This answers a mis-selling allegation two years later. "The client saw the exclusions on 14 March" is an assertion; the forwarded PDF with a read receipt on 14 March is a record.
• What material you sent, and which version. Approved collateral gets revised. Keep the file you sent, not a link that now resolves to a newer version.
• KYC documents, moved out of chat storage into wherever your principal requires them, on the day they arrive.
• Client instructions. "Do not renew the Bajaj one, I sold the car" protects you when that renewal lapses and they say nobody told them.

On retention, be precise about what is actually specified. The POSP framework fixes five years for training and examination records, which is your principal's obligation for your certification file. That figure does not automatically transfer to KYC or sales records; the period for those sits in your engagement contract. Ask your principal for the number rather than assuming five.

None of this needs software. Run the book from a WhatsApp Business account on a separate number, with a labelled catalogue of approved collateral and quick replies built from your principal's approved language, in the languages your book speaks. The temptation to author product prose disappears when the approved version is two taps away. Ask your principal once a quarter which collateral is current, which products you are authorised on, and what may go on Status, so the answers sit on record.

An advisor who can produce the file, the date and the approved wording for any policy is a different counterparty to their principal than one who says "it is somewhere in my phone." That difference decides who gets the better terms when principals start choosing.