WhatsApp for insurance agencies: renewals, queries and consent
How an insurance agency can use WhatsApp across agents: renewal reminders from a CSV, queries as tickets, and opt-outs enforced at send time.
- Written by
- By WavesFlo team
- Published
- Published
- Reading time
- 3 min read
An agency's WhatsApp work is renewals, queries and new enquiries, and all three involve people's personal details. So the order of work is consent first, then ownership, then speed. This guide covers the mechanics. It is general guidance and not legal advice, and your regulator's rules on insurance communication apply on top.
What comes first?
- Only message people who agreed to hear from you about the thing you are sending. A policy on file is not consent to marketing.
- Carry your opt-out list into the tool before any send. The register is checked at the moment each message goes, so someone who opted out last week is skipped this week.
- A CRM import never records consent, so contacts brought in from HubSpot or Zoho arrive with consent unknown.
- Keep retention in mind: message content can be kept for a period you choose, or not at all.
The DPDP Act and WhatsApp covers consent, notice, opt-outs, retention and breach reporting.
How do renewal reminders work?
Export the renewal list as a CSV and import it as a contact list, confirming the column mapping. Columns such as name, policy type and due date become merge fields, so each reminder is personal, and a field with no value stops the send instead of going out blank. Reminders run under quiet hours, a cooldown per person and the approval step if you use one. See payment reminder messages for wording.
How do you handle queries?
| Work | Handled as | Why |
|---|---|---|
| Claim or policy query | A ticket with first-reply and resolution targets | A question cannot sit unanswered in a long chat |
| New enquiry | An opportunity in a pipeline | Stages, tasks and a forecast on the conversation |
| Renewal due | A campaign from a CSV, plus a task for the agent | Reminder out, follow-up scheduled |
| Agent leaves | Chats stay with the business | Their notes and labels remain |
What should you not automate?
Advice, claims decisions and anything that depends on a person's circumstances. Keyword replies and a chatbot suit opening hours and simple status questions, and a person can always take over a chat.
What does the first month look like?
- Week 1: audit consent. Which customers agreed to hear from you, about what, and when.
- Week 2: load the opt-out list and set retention.
- Week 3: import the renewal list from CSV and send a first reminder to a small group.
- Week 4: route queries as tickets with targets, and review the report.
What are the usual mistakes?
- Treating a policy on file as consent to marketing.
- Automating advice.
- Importing contacts from a CRM and assuming consent came with them.
For an agency where each adviser works a book of renewals, WavesFlo gives every renewal conversation an owner and can log one-to-one chats as notes in HubSpot or Zoho CRM once an admin switches syncing on. WavesFlo for sales teams shows how renewals and new enquiries can share the agency's numbers without sharing one queue.
Questions
Can an insurance agency use WhatsApp for renewals?
Yes, to people who agreed to hear from you, with a list imported from CSV and personalised reminders sent under pacing limits.
Does importing a CRM list record consent?
No. A CRM import never records consent; contacts arrive with consent unknown.
Are opt-outs enforced?
Yes. The opt-out register is checked at the moment each message is sent, across every campaign.
Is this legal advice?
No. It is general guidance. Check your regulator's rules on insurance communication and take advice on consent.