Onboard, notify and retain users from your backend
Trigger onboarding sequences, billing notices and product alerts straight from your own systems, on a channel with far better reach than email.
- verified Secure API & webhooks
- lock Event-driven messaging
- how_to_reg Billing notifications
Event received
Template sent automatically
Onboarding sequences
Built in
The channel your customers already use
3.3Bn+
Monthly active users
180
Countries served
100Bn+
Messages sent daily
Free
Replies within 24h of a customer message
WhatsApp platform figures, Q1 2026. Free service replies per Meta’s per-message pricing rules.
Lifecycle messaging that actually gets read
Activation happens in the first week and churn often starts with a failed payment. Both are reach problems.
Onboarding sequences
Guided setup, one step at a time.
Billing notices
Renewals, card expiry and failed payments.
Product alerts
Releases, usage thresholds and job completions.
Event-driven
Fired from your own backend via API or webhook.
Five flows across the user lifecycle
Activation, billing, alerts, retention and support – all triggered by your own events.
Get more accounts to the point the product proves itself
Onboarding nudges that reach users, rather than sitting unopened in an inbox, get more of them through setup and into the moment where the product actually delivers.
- One step per message
- Branches on what they’ve done
- Stops once activated
Product Updates
Onboarding sequence
Recover the payments that quietly fail
Card expiry and dunning notices on a channel people read recover revenue that would otherwise disappear as involuntary churn – usually the cheapest revenue you’ll ever win back.
- Card expiry warnings
- Dunning sequence on failure
- Update link in the message
Template preview
check_circle ApprovedUtility template
Hi {{first_name}}, We couldn’t process your payment for {{plan_name}}. Your account stays active until {{grace_end}}. Update your card below and nothing changes.
Variables in {{ }} are filled per recipient at send time.
Messaging driven by your own events
Post an event to the API and the right approved template goes out. Signup, threshold reached, export finished, payment failed – all from the systems you already run.
- Any backend event
- Approved templates only
- Per-environment API keys
Event to message
-
1
Your app emits an event
Signup, usage threshold, job complete, payment failed.
-
2
Posted to the API
One call with the event name and template variables.
-
3
Template resolved
The matching approved template is populated and sent.
-
4
Reply lands in the inbox
Any response is free to answer for 24 hours.
Notice accounts going quiet before they leave
Usage drops before a cancellation does. Behavioural segments let you reach out while there’s still something to save, with a message that references what they were actually doing.
- Behavioural segmentation
- Triggered on usage decline
- Routes to CS for high-value accounts
Activation by cohort week
- Event-driven
- Triggered
- Segmented
- By behaviour
- Attributed
- To revenue
First-line support from your own docs
Setup, billing and feature questions answered from content you control. Bugs and account problems open a ticket with the whole conversation attached.
- Answers from your documentation
- Ticket created with context
- Plan and billing lookups
Support request
Collected inside the chat
What went wrong?
Workspace
Screenshot
Ship a feature and have people notice
Release notes to the segment that actually uses the area you changed. Far better reach than an in-app banner nobody scrolls to.
- Segment by feature usage
- Marketing category, so opt-in matters
- Click-through to the changelog
Release announcement
SendingSent only to accounts that used the affected feature in the last 30 days.
Catch the accounts hitting their ceiling
Usage thresholds fire a message before the limit bites, so the conversation is about upgrading rather than apologising for a blocked export.
- Triggered on usage threshold
- Routes to CS for larger accounts
- Attributed to expansion revenue
For product and growth teams
Wire it in once and let the lifecycle run.
Webhooks in and out
Both directions, so replies reach your app.
Secure API access
Scoped, per-environment keys with audit logs.
Behavioural segments
Build audiences from product events.
Lifecycle reporting
Activation, expansion and churn signals.
First-line support, automated
Point it at your docs and let it handle the common cases.
Setup and configuration expand_more
Walk users through onboarding steps from your documentation.
Billing and plans expand_more
Current plan, next charge and how to change tier.
Feature questions expand_more
What’s included where, answered from your own content.
Escalate to support expand_more
Bugs and account issues open a ticket with full context.
Why teams choose us
Official Business API
Built on the official WhatsApp Business API, so delivery and policy compliance are predictable.
Privacy-first design
Opt-in enforcement, role-based access and audit trails as standard on every plan.
Fits your systems
Google Calendar sync, plus HubSpot, Zoho, Salesforce, Shopify and your own tools via webhooks and a secure API.
Template approval support
Help getting templates approved, and a team that knows your sector.
How do we trigger messages from our product? expand_more
Post the event to our API or fire a webhook. The matching approved template is populated with your variables and sent.
Are billing notices cheaper than product marketing? expand_more
Yes. Payment and renewal notices qualify as utility templates, which Meta prices well below marketing. Feature announcements are marketing.
Can replies reach our own systems? expand_more
Outbound webhooks push inbound messages to your backend, so a reply can create a ticket or update a record automatically.
Is WhatsApp better than email for onboarding? expand_more
For reach, generally yes – but the honest answer is it’s a complement. Use it for the steps where a missed message costs you an activation.
Do we need a developer to set this up? expand_more
For event-driven messaging, someone needs to post events to the API or point a webhook at us – usually an afternoon. Everything else, including templates and segments, is configured in the dashboard.
Is WhatsApp appropriate for B2B SaaS? expand_more
It depends on your market. In regions where WhatsApp is the default business channel it outperforms email badly; in others email still wins for B2B. Start with billing and incident notices, where a missed message actually costs something.
Explore other industry use cases
Automobile
Service booking, reminders and test drives.
Explore arrow_forward shopping_bagE-commerce
Cart recovery, order updates and repeat sales.
Explore arrow_forward schoolEducation
Admissions, fee reminders and student support.
Explore arrow_forward eventEvents & Webinars
Registration, tickets and attendance.
Explore arrow_forward account_balanceFinance & Insurance
Lead routing, renewals and payment reminders.
Explore arrow_forward fitness_centerGyms & Fitness
Trial conversion, schedules and renewals.
Explore arrow_forward medical_servicesHealthcare
Appointments, reminders and 24/7 patient support.
Explore arrow_forward groupsHR & Recruitment
Screening, scheduling and internal comms.
Explore arrow_forward developer_modeIT Services
Brief capture, onboarding and deployment alerts.
Explore arrow_forward apartmentReal Estate
Listings, viewings and a visible pipeline.
Explore arrow_forward restaurantRestaurants
Reservations, menus and delivery orders.
Explore arrow_forward storefrontRetail & Offline
Promotions, stock checks and collection.
Explore arrow_forward spaSpas & Salons
Confirmations, gap-filling and rebooking.
Explore arrow_forwardReady to wire it into your product?
See onboarding, billing and retention messaging triggered from your own events.