Quotes, renewals and claims that get finished, inside WhatsApp.
Policyholders skip renewal emails and give up on long web forms. Flowella turns your quote, renewal and claim forms into short WhatsApp Flows, then passes every answer to HubSpot and, through the API, to your policy and rating systems.
Read our guide to WhatsApp Flows for insurance
- Built for
- Insurers, MGAs and brokers
- Opens from
- Renewal notices, ads and QR codes
- Answers land in
- Your HubSpot contact properties
- Setup
- Live in 30 minutes
From an ad to a policy, in one chat.
A driver taps your ad and WhatsApp opens. Two short forms later they have chosen their cover, paid on your own secure page and received their certificate. Tap the ad and buy the policy as Maya: each step shows which system does the work.
Covered, with the certificate in the chat.
Tap the ad, the way a driver would. No landing page. The chat is the shop. One reg number, and your systems do the rest. Three real prices, from your own rating engine. Payment stays on your page, never in the chat. Covered, with the certificate in the chat.
Today
The chat opens here when someone taps the ad.
Hi, I’d like a car insurance quote.
Secure payment
Your own payment page. Card details never enter the chat.
-
Ad tappedMeta
Click-to-WhatsApp ad, chat opened Done
-
Details collectedFlowella
WhatsApp Flow: registration, name, date of birth Done
-
Car looked upYour vehicle lookup
Ford Fiesta 1.0 Zetec Done
-
Prices returnedYour rating engine
Three levels of cover, priced for AB12 CDE Done
-
Cover chosenFlowella
Comprehensive, £451.60 Done
-
Payment takenYour payment page
£451.60 paid Done
-
Policy issuedYour policy system
Policy AC-204817, certificate sent as a PDF Done
7 of 7 steps done
Flowella runs the chat and the forms. Your own systems price, take payment and issue the policy, connected through the Flowella API.
Done. Maya went from an ad to a paid policy in one chat, and the certificate arrived as a PDF.
Tap Send message on the ad to start, as a driver would. WhatsApp opens with the ad’s message already typed. Send it. The business replies with a Flow button. Tap Get my quote. The Flow asks for a registration number, a name and a date of birth. Nothing you type leaves this page. Your vehicle lookup finds the car and your rating engine prices it. This takes your systems a few seconds, between two messages. The prices are back in the chat. Tap Choose my cover to see them. Pick a level of cover and any add-ons. The total updates as you choose. The choice is on the record. Tap Pay securely to open the payment page. This stands in for your own payment page, opened from the link in the chat. Done. Maximiliana-Wolfgang went from an ad to a paid policy in one chat, and the certificate arrived as a PDF. Form closed. Tap its button in the chat to open it again.Where WhatsApp Flows help in insurance.
From the first quote to a settled claim, each touchpoint becomes a short conversation whose answers fill a HubSpot property and can go on to your policy system.
-
Quotes
The opening questions of a quote as taps, sent to your rating API, with the price back in the same chat. Try it above
Lands in HubSpot as
cover_type -
Renewals
Three weeks before the date: the premium, a check on what has changed, and one tap to renew or talk to someone.
Lands in HubSpot as
renewal_choice -
First notice of a claim
What happened, when and where, with photos, while it is still fresh. Your handler opens the claim with the facts.
Lands in HubSpot as
claim_type -
Mid-term changes
A new car, a new address or another driver, sent as a structured change request and not left in a phone queue.
Lands in HubSpot as
change_type -
Missing documents
Proof of no claims, a V5C or a photo of the damage, uploaded in the chat and filed against the record.
Lands in HubSpot as
document_type -
Feedback after a claim
A two-question check-in when a claim closes, with anyone unhappy passed to a person the same day.
Lands in HubSpot as
claim_rating
Connect it to your policy system.
Your policy admin, rating or claims system calls the Flowella REST API to send a renewal, a quote or a claim update, and Flowella posts signed webhooks back as the customer reads, replies and completes. Send a renewal, then follow the events back.
Queued in a blink. The events follow.
Send the request, then watch the events come back. Queued in a blink. The events follow. Same key, same job. Nobody gets it twice. A reply brings ids, not the words. No answer? Three tries in all, then I stop.
POSThttps://api.flowella.io/v1/templates/send
Headers
- Authorization
Bearer flo_••••••••••••Your API key, masked- Content-Type
application/json- Idempotency-Key
renewal-2026-11-30-1Repeats of this key within seven days return the same job.
Body
{
"templateId": "cltemplate00000001",
"whatsappChannelId": "clchannel000000001",
"recipients": [
{
"phone": "+447700900123",
"bodyParameters": ["Maya"]
}
]
}
{
"templateId": "cltemplate00000001",
"whatsappChannelId": "clchannel000000001",
"recipients": [
{
"phone": "+447700900123",
"bodyParameters": ["Maximiliana-Wolfgang"]
}
]
}
{
"id": "v1ts-3f9a07c2b1d4e6a8",
"status": "accepted"
}
{
"id": "v1ts-3f9a07c2b1d4e6a8",
"status": "accepted"
}
Queued. Flowella sends it in the background.
Queued. Flowella sends it in the background. Same key, same job: nothing was sent twice. Accepted, but Maximiliana-Wolfgang has opted out on this channel, so Flowella won’t send it.Today
Deliveries
POSThttps://example.com/webhooks/flowella
- Content-Type
application/json- X-Flowella-Signature
5c2e91…a07f3bValid
{
"id": "evt_9a4f1d06c3e84b27a5d9e2b70c6f8d14",
"type": "message.read",
"created_at": "2026-10-16T09:14:21.000Z",
"payload_version": "1",
"data": { … }
}
{
"id": "evt_5b0e2c7d91f64a38b2c6d0e4f7a19c53",
"type": "message.delivered",
"created_at": "2026-10-16T09:14:03.000Z",
"payload_version": "1",
"data": { … }
}
In data: the message’s messageId.
Not in data: the phone number or the message text.
In data: messageId, conversationId, contactId, direction, type and metaMessageId.
Not in data: the phone number or the message text.
In data: the message’s messageId.
In data: the phone number and the reason.
Flowella waits up to 10 seconds for a 2xx and tries each delivery at most 3 times, 1 and 2 seconds apart.
message.sent, message.delivered and message.read reached your endpoint, each one signed.
Change the first name if you like, then send the request. Sending the request. 202 Accepted: Flowella queued the send and returned a job id straight away. message.sent, message.delivered and message.read reached your endpoint, each one signed. Same Idempotency-Key, so Flowella returned the same job and sent nothing twice. Maximiliana-Wolfgang’s reply arrived as message.received: ids, direction and type, not the words. STOP opted Maximiliana-Wolfgang out: message.received arrived, then optout.created with the phone number and the reason. Your endpoint isn’t answering, so Flowella tries again after 1 second, then after 2. Flowella stopped after 3 attempts. Turn your endpoint back on, then send with a new key. Your endpoint answered, so the delivery went through on a retry. 202 Accepted, but Maximiliana-Wolfgang opted out with STOP, so Flowella won’t send the template.Subscribe to any of 12 events.
Pick the events you need in Settings, Webhooks. Each one arrives as a signed POST with its own id, its type, when it happened and its data.
Messages
message.received- An inbound WhatsApp message arrives from a contact
message.sent- Flowella has accepted your message and submitted it to Meta
message.delivered- Meta confirmed delivery to the recipient’s device
message.read- The recipient opened the message
message.failed- Meta returned a failure for the message
Conversations
conversation.opened- A conversation moved into the open state
conversation.closed- A conversation was closed
Opt-outs
optout.created- A contact opted out on a channel
Templates
template.status_updated- Meta changed a template’s status: approved, rejected, paused or disabled
Contacts
contact.created- A contact was created
contact.updated- A contact was updated
contact.deleted- A contact was deleted
Plus webhook.test, sent only when you press Send test.
Or ask your AI assistant to build the journey.
Connect Claude, ChatGPT or Cursor to Flowella through the MCP server, then describe the journey you want. The assistant drafts the templates, the WhatsApp Flow and the follow-ups in your account, and nothing is submitted or sent until you say so.
How to connect an AI assistantDrafts only. Nothing sends yet.
Pick a request and send it. Watch it appear in Flowella. Drafts only. Nothing sends yet. Off to Meta for review. Approved. Switch it on when you’re ready. Still drafts. Nothing was sent.
Flowella is connected. What would you like to build?
You: Build a renewal journey for home insurance. Twenty-one days before the renewal date, send the premium and a WhatsApp Flow that asks whether anything has changed. Remind once after a week, and stop when they renew.
Working in Flowella
- Done: Found the renewal date property
- Done: Drafted the renewal notice
renewal_notice - Done: Built the WhatsApp Flow from your renewal form
renewal_check - Done: Added a seven-day wait
- Done: Drafted the reminder
renewal_reminder - Done: Set the goal on the renewal status
Your renewal journey is in Flowella as drafts: two templates, a WhatsApp Flow and the steps that send them. The templates need Meta’s approval before anything can go out. Shall I submit them?
Message Claude
- 21 days before the renewal dateHubSpot date property
-
Renewal noticeMarketing · premium and date · Review button
renewal_noticeDraft -
WhatsApp Flow for renewalsWhat has changed and how to renew, from your form
renewal_check - Wait 7 daysSkipped once they answer
-
ReminderMarketing · reopens the WhatsApp Flow
renewal_reminderDraft - Goal: policy renewedStops the reminders for that contact
Everything is a draft. Nothing is submitted or sent until you confirm.
Sample data. The assistant works through the Flowella MCP server, with the access you approve.
Building the customer journey in Flowella, one step at a time.
Everything is a draft. Nothing is submitted or sent until you confirm.
Templates submitted to Meta for review.
Templates approved. The workflow stays off until you switch it on.
Kept as drafts. Nothing was submitted or sent.
Built for forms, not chatbots.
Flowella brings the forms your insurance team already relies on into WhatsApp, and keeps your CRM and policy systems as the places your data lives.
-
Forms-first design
Start from the quote, renewal and claim forms you already use and bring them into WhatsApp as Meta’s native Flows, so every answer arrives structured.
-
Answers land in HubSpot
Each answer fills a contact property, so your lists, workflows and reports work as they do for web forms.
-
Open to your own systems
A REST API, signed webhooks and an MCP server connect Flowella to your policy, rating and claims systems, directly or through a tool such as n8n.
-
Opt-in that names your firm
Collect WhatsApp consent inside the Flow, naming your firm, and every opt-out is honoured on every send.
-
Stored in the UK
Flowella runs on Microsoft Azure in London, with your data encrypted in transit and at rest.
-
Where your policyholders already are
Ofcom’s Online Nation 2025 found that 90% of UK online adults use WhatsApp.
In our customers’ words.
Exceptional engagement platform that transformed our student conversion with 160% increase in same-day applications and 90% WhatsApp response rates.
Peter HudsonDirector of Admissions, Brand & Customer Innovation
Game-changing donation campaign tool that delivers personal WhatsApp engagement with seamless automation and dramatically better completion rates.
Lawrence Tribe-EndtCommercial Director, Countryside Alliance
Playbooks for insurance teams.
Working blueprints that fit an insurance team, each with its Flow, its message templates and its HubSpot workflow.
-
Web Contact Follow-up
A short form on your website, then the rest of the proposal questions on WhatsApp.
- Marketing
- Communication
-
KYC Onboarding
Customers send ID and proof of no claims through a secure upload page, and the details land on their record.
- Onboarding
- Support
-
Lead Capture & Qualify
Two quick questions sort every quote enquiry before a broker picks up the phone.
- Sales
- Marketing
- Communication
-
Contact Data Refresh
Once a year, ask policyholders to confirm the details you hold and write corrections back to the record.
- Support
- Retention
- Communication
-
NPS / CSAT
A one-tap score when a claim closes, with a person for anyone unhappy.
- Support
- Retention
- Communication
-

Appointment Reminders
A reminder before a loss adjuster’s visit or a review call, with one tap to rearrange.
- Sales
- Support
- Communication
Bring your next renewal into WhatsApp.
Book a 30-minute demo on Microsoft Teams with Adam, our founder. We’ll show you a working quote or renewal Flow mapped to your own form, and how it connects to your policy system.
Or start a free 14-day trial