WhatsApp for SaaS: onboarding, activation and renewals that land

WhatsApp for SaaS means using WhatsApp, with your users' permission, to help them get set up, reach their first result, hear about features that matter to them and renew on time. It works best for short, timely, useful messages. Meta treats account and billing updates as utility and feature news or upgrade offers as marketing, which changes cost and delivery.

This guide is for founders, product marketers and customer success teams at B2B and B2C software companies, whether you sell a payroll tool in Dublin, a CRM in Bengaluru, a fintech app in Lagos or a scheduling product in Austin. It covers where WhatsApp fits, which messages Meta categorises how, six plays with sample copy, and an honest split between what Buddy runs today and what needs the Buddy API.

Why use WhatsApp in a SaaS lifecycle?

Most SaaS lifecycle messaging happens in email and in-app prompts. Both have limits. Onboarding emails compete with everything else in a work inbox, and in-app messages only reach people who are already in the app, which is exactly who you don't need to reach. WhatsApp reaches people outside the product, in a place they check through the day, and they can reply in a sentence instead of opening a support ticket.

That makes it a strong channel for a small number of moments: the day after signup, the point where a trial user gets stuck, the week before a renewal, and a failed payment. It's a poor channel for everything else. If you move your full email drip onto WhatsApp, you'll pay per message for content people didn't want, and they'll opt out. The skill is choosing the few messages that deserve the channel.

It also depends on your market. In much of Europe, Latin America, India, Africa, the Gulf and South-East Asia, WhatsApp is how people expect to hear from a business. In the US it's used less for this, and Meta doesn't currently deliver marketing templates to US numbers at all (more below). Plan by where your users actually are.

Which SaaS messages are utility and which are marketing?

Every message you start outside the 24-hour customer service window uses a template, and every template has a category. Meta's categorisation rules say a utility template must be non-promotional, with no persuasive intent, and must be either specific to or requested by the user, or essential to them. Utility messages are typically triggered by something the user did and relate to their order, account, service or transaction. Anything that mixes utility with promotion is categorised as marketing.

Meta's own examples are very close to SaaS use cases. "Reminder: Your monthly payment for {{service}} will be billed on {{date}}" is listed as utility. "Your subscription will expire on {{date}}! Renew today to save {{discount}}" is listed as marketing. Same moment, different wording, different category. Here's how common SaaS messages usually fall:

Meta makes the final call at review, and it can recategorise an approved template later if it's used promotionally. Meta's utility templates guide and our own WhatsApp message templates guide go deeper. The practical rule: write utility templates like a bank statement, plain and specific, and put anything persuasive in a separate marketing template.

How do categories affect cost and delivery?

• Pricing. Meta charges per delivered template message, at rates set by the recipient's country, as listed on its pricing page. Marketing templates are always charged. Utility templates have been free inside an open 24-hour window, but from 1 October 2026 Meta charges service replies and utility messages inside the window too. Our October 2026 pricing explainer has the detail.
• US users. Meta's per-user limits page says WhatsApp does not currently deliver marketing templates to people with US phone numbers. Utility, authentication and service messages still work, so a renewal notice reaches a US customer but a feature launch won't.
• Per-person marketing caps. WhatsApp limits how many marketing templates each person receives from all businesses, based on engagement. Over the cap, the message isn't delivered and returns error 131049. The cap is about marketing templates, which is one more reason to keep utility messages clean.
• Messaging limits. New business portfolios start with a daily limit on how many unique people you can message with templates, rising as you send well. Meta explains the tiers in its messaging limits guide. If you plan a big announcement to your whole user base, check your limit in Buddy's WhatsApp health page first.

How do SaaS companies get WhatsApp opt-in?

Meta's opt-in guidance requires that people agree to receive messages from your business on WhatsApp, and that the request names your business clearly. A phone number collected for two-factor login is not consent to marketing. Under UK and EU GDPR, consent must also be freely given, specific, informed and unambiguous, and the ICO is clear that pre-ticked boxes don't count.

For software, the cleanest pattern is per-category consent at a moment of intent. Offer two separate, unticked choices: "Send account and billing alerts to my WhatsApp" and "Send product news and tips to my WhatsApp". Record each one and tag accordingly. Three ways to collect it with Buddy today:

1. 1Your own signup or settings screen, plus the Subscribers API. Collect consent in your UI, then add the person to Buddy with POST /api/v1/subscribers and tags that say what they agreed to. The Subscribers API is live in early access today.
2. 2Buddy Embed (beta). A one-line script adds a Buddy opt-in form, with name, WhatsApp number and a consent checkbox, to your marketing site or help centre. See our WhatsApp opt-in widget guide.
3. 3Your hosted opt-in page. Link to usebuddy.app/yourname from your onboarding email, docs footer or in-app banner.

curl -X POST https://usebuddy.app/api/v1/subscribers \
  -H "Authorization: Bearer bd_live_YOUR_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "name": "Priya Shah",
    "phone": "+447700900123",
    "tags": ["account-alerts", "product-news", "trial", "trial-2026-w42"]
  }'

Every Buddy contact who replies STOP, unsubscribe or opt out is unsubscribed and suppressed automatically, and the consent event is logged. That covers WhatsApp. Remember to reflect the change in your own product's settings too.

What can you run today, and what needs the Buddy API?

This is the honest part. The most valuable SaaS messages are triggered by product events: a trial about to end, a payment that failed, a user who hasn't logged in for ten days. Buddy's app doesn't listen to your product's events, and its automation triggers today are exactly three: when someone subscribes (through the opt-in page or embed form), when a message comes in, and when a reply is categorised. There's no trial, payment or inactivity trigger.

The workaround that works today is cohort tags plus scheduled WhatsNews. When you add a trial user through the API, tag them with the week they started, such as trial-2026-w42. If your trial is 14 days, schedule a WhatsNew to that tag for day 11. It's not per-user precision, but for a weekly cohort it's close, and it's a real campaign with delivery, read, click and reply tracking. Our API integration guide covers what the public beta adds, and the Buddy API page tracks what's live.

Six WhatsApp plays for SaaS, with sample copy

Each play shows the likely category, how to run it in Buddy today, and what changes with the API. Sample copy is illustrative; write your own templates in Buddy's Message templates builder and submit them to Meta. Review can take up to 24 hours, though it's often minutes.

1. Onboarding confirmation

Category: utility. Sample: "Hi {{1}}, your {{2}} workspace is ready. You chose to get account alerts on WhatsApp; reply STOP to turn them off." Keep it to confirmation. Don't add tips or offers, or it becomes marketing.

Today: if users join through your opt-in page or Buddy Embed, the "When someone subscribes" trigger can send this template automatically. If you add them through the API, send it as a WhatsNew to a daily or weekly new-signups tag. From 12 October: send it from your own code the moment the workspace is created, through the API public beta. Dedicated transactional messaging for utility templates like this one is planned for release 1.1.

2. Activation nudge

Category: usually marketing, because it's persuasive. Sample: "{{1}}, teams that connect their first data source in week one get their first report the same day. It takes about two minutes." Add a link button to the exact setup screen.

This is where replies pay off. Ask a question: "Stuck on anything? Reply and a person on our team will help." Replies open the 24-hour window, land in Buddy's Inbox, and are sorted on the Responses page into Interested, Question, Purchased, Follow up and Not now. An automation on "When a reply is categorized" can notify your customer success team about every Question. Buddy's team inbox guide covers handling this at volume.

3. Feature announcements

Category: marketing. Sample: "New in {{1}}: scheduled exports. Set it once and your report arrives every Monday. See how it works." Target it. Send to users on the plan that includes the feature, or to people tagged with the related interest, rather than your whole base. A few well-chosen announcements a quarter are likely to do more than a weekly changelog, which belongs in email.

Today: a WhatsNew to a tag, sent now or scheduled, using Buddy's Announcement campaign type. Remember it won't reach US numbers as a marketing template.

4. Trial ending

Category: a plain notice can be utility; any offer makes it marketing. Utility sample: "Your {{1}} trial ends on {{2}}. Your data stays safe, and you can choose a plan in Billing." Marketing sample: "Your trial ends Friday. Upgrade this week and your first month is half price." If you want both, send them as two templates.

Today: cohort tag plus scheduled WhatsNew, as above. From 12 October: trigger it per user from your billing system via the API.

5. Renewal and payment reminders

Category: utility, if kept factual. Samples: "Reminder: your {{1}} plan renews on {{2}} for {{3}}." and "We couldn't take your payment for {{1}}. Please update your card to keep your account active." For most customers, a reminder is far better than a surprise charge or a suspended account.

Today: annual renewals are predictable, so tag by renewal month and schedule. Failed payments aren't predictable, so they genuinely need an event-triggered send: the API from 12 October, with dedicated transactional messaging planned for release 1.1. Until then, handle failed payments by email and in-app.

6. Feedback and win-back

Feedback (utility): "You spoke to our team about {{1}} this week. How did it go? Reply with a number from 1 to 5." Meta lists feedback on a recent interaction as utility, though its example is about an order, so expect Meta to judge your wording at review. Keyword automations on "1" and "2" can tag low scores and notify your team; they match any message containing that character, so ask for a single number and check the tagged replies.

Win-back (marketing): for churned users who stayed opted in to product news, one message when something they asked for ships: "You asked for Xero sync when you left. It's live now." Specific beats generic. Don't send win-backs to people who only agreed to account alerts.

How should SaaS teams measure WhatsApp?

Buddy shows delivery, reads, clicks, replies and failures for every WhatsNew, with the top failure reason explained, plus opt-in growth over time. Those tell you whether the message landed. The number that matters for SaaS lives in your product: did the cohort that got the activation nudge activate more than the one that didn't?

• Hold out a slice. Campaigns go to one tag, so give most of a cohort a send tag, keep a small group out of it, then compare activation or conversion in your own analytics.
• Track link clicks to the exact screen. Add UTM parameters to template link buttons so your product analytics can attribute the visit.
• Watch opt-outs after each send. Buddy's Consent page shows opt-out totals and recent consent activity. If opt-outs climb after product-news sends, you're sending too much of it.
• Don't trust read rates alone. People can turn off read receipts, so reads undercount. See our WhatsApp marketing metrics guide.

Mistakes SaaS companies make with WhatsApp

• Messaging every user because you have their number. Numbers collected for login or billing aren't WhatsApp consent.
• Sneaking offers into utility templates. Meta recategorises them as marketing, which changes cost and delivery.
• Copying the email drip. Twelve onboarding emails don't become twelve WhatsApp messages. Pick two or three moments.
• No human behind the replies. If you invite replies, staff the inbox. Meta's policy also expects a route to a person when you automate.
• Ignoring number health. A big announcement from a new number can hit the messaging limit or dent your quality rating. Check first.

How to get started

1. 1Create a Buddy workspace and connect your own WhatsApp Business number through Meta's Embedded Signup. Your number and templates stay in your own Meta business portfolio.
2. 2Add per-category consent to your signup or settings screen, and create an API key for the Subscribers API.
3. 3Write two utility templates (setup confirmation, renewal reminder) and one marketing template (feature announcement), and submit them to Meta.
4. 4Tag users by consent type and by signup week, and schedule your first cohort message.
5. 5Staff the inbox, and plan which messages move to event-triggered API sends once the public beta opens on 12 October 2026.

For the complete picture of how Buddy runs WhatsApp, read our WhatsApp marketing platform guide. For the SaaS view, see Buddy for SaaS, and for building on Buddy, the developers page. Plans are on the pricing page.

WhatsApp for SaaS: frequently asked questions