Skip to content
OmniChannels.ai
Menu

WhatsApp for Insurance: Use Cases, Templates and Rollout

WhatsApp for insurance: quotes, renewals, premium reminders, claims first notice with photos and status updates, with template categories and a rollout plan.

Updated 11 min read

By OmniChannels.ai Editorial Team · Reviewed by BroadNet Messaging Solutions Team

Marketing

Short answer

Insurers and brokers use WhatsApp for quote follow-up, policy documents, renewal and premium reminders, claims first notice of loss with photos, claim status updates and OTP. Send each through the right template category: premium due and claim status are usually utility, renewal offers and cross-sell are marketing, codes are authentication. Never ask for full card or ID numbers, and keep consent and data handling documented.

On this page
  1. Why do insurers use WhatsApp?
  2. Which template category fits each insurance message?
  3. How do you handle quotes and lead follow-up?
  4. How do renewal and premium reminders work?
  5. How do claims first notice of loss and status updates work?
  6. How do you use OTP and fallback in insurance?
  7. How do you protect customer data?
  8. What does it cost?
  9. Worked example: a regional broker
  10. Rollout checklist
  11. How OmniChannels.ai helps

Key takeaways

  • Match each insurance message to a Meta template category: payment reminders and claim updates tied to a customer's policy are utility candidates, while anything that promotes, upsells or seeks a renewal is marketing.
  • Meta's documentation says order and account alerts that promote, cross-sell or seek renewals are not utility, so plan renewal prompts as marketing and keep pure information separate.
  • WhatsApp's business policy prohibits asking people to share full payment card numbers, financial account numbers or personal ID card numbers, so claims flows should use secure links or agent calls for sensitive data.
  • A customer's message opens a 24-hour window for free-form replies, which suits first notice of loss: the customer can send photos and you can answer in the same thread.
  • Roll out in stages, starting with one utility use case, one opt-in source and one human escalation path.

This guide is for insurers, brokers and agencies that want to use WhatsApp for sales and service without creating compliance problems. It maps the main use cases to Meta's template categories, gives sample templates, explains what not to ask for in chat, and ends with a rollout plan. It is general information, not legal advice; insurance communications are regulated differently in each country, so involve your compliance team.

Why do insurers use WhatsApp?

Customers already use WhatsApp daily, and insurance has natural moments that need a message: a quote to follow up, a payment due, a policy to renew and a claim to track. WhatsApp supports text, documents, images and buttons in one thread, and a person can answer when it suits them.

It does not replace everything. Contracts, medical files and identity checks belong in secure systems. WhatsApp is the front door that starts, reminds and updates. For comparable patterns in banking see banking and fintech customer messaging, and for health-related messaging see healthcare patient messaging.

Which template category fits each insurance message?

Use the category that matches the message's purpose; Meta reviews and can change it. There are three categories for messages you start: marketing, utility and authentication. Inside the 24-hour customer service window after a customer's message, you can reply with free-form messages.

Meta's categorization documentation describes a utility template as non-promotional and either specific to or requested by the customer, or essential to them. Its examples include payment reminders, account updates and follow-ups on a support request if the user asked to move the conversation to WhatsApp. It says mixed content is not utility, and that alerts which promote, recommend, upsell, cross-sell or seek renewals are not utility either. Marketing covers awareness, sales and relationship-building. Authentication is for one-time passcodes. Our guide to template categories and approval explains the review process.

Use case Typical message Likely Meta category Notes
Quote follow-up requested by the customer "Your quote is ready" Utility candidate Only if the customer asked for it and the text is not promotional
Lead nurture and offers "Add family cover" Marketing Needs marketing opt-in
Policy document delivery "Your policy document is attached" Utility candidate Tied to a purchase or account
Renewal notice with an offer or renew prompt "Renew now and keep your discount" Marketing Meta: seeking renewals is not utility
Premium due reminder "Your premium of [amount] is due on [date]" Utility candidate Payment reminders appear in Meta's examples
Claim first notice of loss Customer starts the chat Free-form in the window Template needed only to restart after 24 hours
Claim status update "Your claim [number] moved to [stage]" Utility candidate Tied to the customer's open claim
Login or approval code "[code] is your verification code" Authentication Preset text, see the OTP guide
Satisfaction survey after a claim "How was your claim experience?" Utility only if tied to a specific interaction Meta: generic surveys are not approved as utility

"Utility candidate" is deliberate. Meta makes the final classification, and a template Meta judges promotional is approved as marketing and billed accordingly. Never promise yourself a category.

How do you handle quotes and lead follow-up?

Reply fast in the thread where the lead asked, then keep follow-ups relevant. The first minutes matter, and a person who messaged you (from a website button, an ad or a QR code) has opened the 24-hour window, so you can answer freely.

  1. Capture the lead with opt-in: a click-to-chat link or QR code with a clear statement of what you will send. Our WhatsApp link generator builds links with a prefilled message.
  2. Ask three questions only: type of cover, rough details, best time to talk. Do not collect ID or card data.
  3. Hand to an agent with the details, or send a quote link.
  4. Follow up with a template if the window closes. A customer-requested quote reminder is a utility candidate; "last chance to save" is marketing.

Sample templates (label shown for each; submit with realistic samples):

  • Quote ready (Utility candidate): "Hello {{1}}, the quote you requested for {{2}} cover is ready. Tap the button to view it, or reply here and an adviser will walk you through it."
  • Offer for lapsed leads (Marketing): "Hello {{1}}, you asked about {{2}} cover earlier. If you would like to talk it through, reply YES and an adviser will contact you. Reply STOP to unsubscribe from offers."

See the lead generation guide for more on capturing leads.

How do renewal and premium reminders work?

Separate information from offers. A premium reminder tells the customer something they need; a renewal campaign asks them to buy. Treat them as two templates with two consents.

Suggested schedule: an early renewal notice, a payment reminder before the due date, and a final reminder after the due date. Keep it to a small number of messages and stop as soon as the customer pays or replies.

  • Premium due (Utility candidate): "Hello {{1}}, a reminder that the premium for policy {{2}} is due on {{3}}. Tap the button to pay securely or reply here for help." Use a URL button to your own domain, not a shortener.
  • Renewal offer (Marketing): "Hello {{1}}, your {{2}} policy ends on {{3}}. You can review and renew your cover here. Reply STOP to unsubscribe from offers."
  • Payment received (Utility candidate): "Hello {{1}}, we received your payment for policy {{2}}. Thank you. Your documents are available in your account."

Never put the full policy number, card details or personal health information in a message if your compliance team has told you not to; show a masked reference instead. Add an opt-out path for marketing templates, and process it quickly.

How do claims first notice of loss and status updates work?

The customer starts the claim in WhatsApp, and you answer in the same thread. Because the customer messaged first, the 24-hour window is open and the conversation can include free-form text, photos and documents.

A claims flow that works:

  1. Greeting and menu (auto): "Hello, I can help you report a claim. What happened?" with buttons for motor, home, travel, health.
  2. Basic facts: date, place, short description, whether anyone is hurt. If there is danger, show your emergency instruction first.
  3. Photos and documents: the customer sends pictures; the bot or agent attaches them to the claim record.
  4. Reference number: "Your claim reference is [number]. An adviser will contact you within [your service time]."
  5. Identity and sensitive data: use a secure link or a call. Do not ask for card numbers, bank account numbers or ID card numbers in chat; WhatsApp's business policy prohibits that, and it also says not to send or request health information where regulations prohibit it.
  6. Status updates: after the window closes, send updates with a utility candidate template.

Status update template (Utility candidate): "Hello {{1}}, your claim {{2}} is now {{3}}. {{4}} Reply here if you have questions."

Use buttons and list messages to keep inputs short; see our guide to WhatsApp interactive messages and WhatsApp Flows for structured forms. Handover to a person matters most here: a stressed customer needs a human quickly, so read our chatbot human handoff guide.

How do you use OTP and fallback in insurance?

Use authentication templates for login or approval codes and SMS as a fallback. Meta requires one-time passwords to use the authentication category, with preset text and a copy-code or one-tap button. For policy portals or claim approvals, send the code on WhatsApp first and fall back to SMS if it is not delivered within your time limit. Details are in our guides to WhatsApp vs SMS OTP and channel fallback.

How do you protect customer data?

Collect less, mask more and document everything. Insurance chats hold personal and sometimes health information, so design the flow to move sensitive steps elsewhere.

  • Opt-in: Meta requires the recipient's permission and leaves the method to you. Record source, time and scope.
  • Opt-out: honour requests, including those made off WhatsApp.
  • Data minimisation: ask only for what the step needs; mask policy numbers where possible.
  • Access control: assign conversations to named agents, restrict who sees attachments, and keep an audit trail.
  • Retention: define how long chats and attachments are kept, with legal input.
  • Vendor security: review your provider. BroadNet holds ISO/IEC 27001:2022, ISO/IEC 27018 and SOC 2 Type II attestations and states GDPR compliance; see our security page and the guide to WhatsApp Business API security and privacy.

Regulators set their own rules for insurance advertising, record keeping and complaint handling. We do not summarise them here; ask your compliance or legal team which apply in each country.

What does it cost?

Meta charges per delivered message by category and recipient market, and BroadNet passes WhatsApp through at Meta's rate with zero markup. Meta's pricing documentation says that from 1 October 2026 service messages and utility templates sent inside the customer service window are charged, with each business phone number receiving 1,000 free service messages a month. We do not print rates; see WhatsApp pricing by country, the WhatsApp pricing calculator and Meta's rate card.

Worked example: a regional broker

"Gulf Shield Brokers" (synthetic) sells motor and home cover and wants to cut missed premium dates and slow claims updates.

  1. Month 1: premium reminders only (utility candidate), with a URL button to the payment page, an SMS fallback after a set time, and opt-in captured at policy issue.
  2. Month 2: claims status updates. The adviser changes the status in the CRM; a webhook sends the template.
  3. Month 3: claims first notice of loss in WhatsApp with photo upload, a human handover, and secure links for sensitive documents.
  4. Month 4: renewal campaigns as a separate marketing template to customers who opted in to offers.

The team tracks reminders delivered and read, payments after reminder, claims opened through WhatsApp, time to first reply and opt-out rate. Because each step has its own template and consent, one problem cannot spoil the others.

Rollout checklist

  • Compliance has reviewed message types, retention and opt-in wording.
  • Opt-in captured at quote, purchase or servicing, with separate marketing consent.
  • One use case live first, with utility candidate templates submitted and approved.
  • Marketing templates kept separate, with an opt-out path.
  • No requests for card, account or ID numbers in chat.
  • Human handover tested, with named owners and service hours shown.
  • SMS fallback configured and tested.
  • Reporting on delivery, read, replies, opt-outs and template quality. See messaging limits and quality rating.

How OmniChannels.ai helps

OmniChannels.ai is built on BroadNet's WhatsApp Business API, with Meta Embedded Signup, templates for marketing, utility and authentication, a phone preview and approval tracking. Conversations land in the Omni Inbox with assignment and tagging, chatbots and AI agents hand over to a person, and channel fallback can route from WhatsApp to SMS. Our team prepares and files WhatsApp onboarding with you; approval decisions stay with Meta. See the WhatsApp channel or book a demo.

Frequently asked questions

Can insurance companies use WhatsApp to talk to customers?

Yes, through the WhatsApp Business Platform, with the customer's opt-in and Meta-approved templates for messages you start. Inside the 24-hour window after a customer message you can reply freely. Regulators in your country may set rules for insurance communications and record keeping, so involve compliance before you launch.

Is a renewal reminder a utility or marketing template?

It depends on the content, and Meta decides. Meta's categorization documentation says order and account alerts that promote, cross-sell or seek renewals are not utility. A plain notice of an expiry date with no promotion is closer to utility, but a message that invites the customer to renew or shows an offer should be planned as marketing.

Can customers send claim photos over WhatsApp?

Yes. When a customer messages you, a 24-hour window opens and they can send images and documents, which your agents or bot can attach to the claim. Do not ask for card numbers, bank account numbers or ID card numbers in the chat. WhatsApp's business policy prohibits that, so collect such data through a secure channel.

Do we need opt-in to send premium reminders?

Yes. Meta requires opt-in from the recipient before you message them on WhatsApp, and you decide the method. Capture it at quote, purchase or policy servicing, record the source and time, and offer separate choices by message type. Honour opt-out requests, including requests made outside WhatsApp.

How do we handle sensitive health or personal data?

Keep chats light on sensitive details. WhatsApp's policy says not to send or request health information where applicable regulations prohibit it. Use the chat to start a claim and share status, and move detailed medical or identity data to a secure portal or an agent call. Check data protection law and your regulator's guidance.

What happens if the customer does not reply on WhatsApp?

Use channel fallback. If a WhatsApp template is not delivered or read in the time you set, send a short SMS with a link. The order is set per use case. Keep the SMS free of sensitive details and give an opt-out where your market requires one.

Sources

  1. Template categorization, WhatsApp Business Platform, Meta for Developers
  2. WhatsApp Business Messaging Policy
  3. Send messages and the customer service window, WhatsApp Business Platform, Meta for Developers
  4. WhatsApp Business Platform pricing, Meta for Developers

Keep reading

More guides