WhatsApp CSAT Feedback Template for SaaS

Why utility, not marketing

This template asks about a real interaction the customer just had — it is transactional, informational, and carries no promotion, so it correctly qualifies as Utility. That matters for two reasons. First, Utility templates are meant for exactly this kind of post-event, service-oriented message, so they clear Meta review cleanly when kept promotion-free. Second, since Meta moved off per-conversation billing on 1 July 2025, WhatsApp charges per delivered message by category — and utility messages are priced lower than marketing. Keeping this CSAT ask strictly in the Utility lane means you pay the utility rate rather than the marketing rate. The instant you add a discount, an upsell, or a 'come back and see what's new' line, it becomes Marketing — a higher rate, a stricter review, and a required opt-out line.

Personalising the variables

The two variables are what turn a generic blast into a 1:1 message. {{1}} carries the user's first name so the greeting feels human, and {{2}} names the exact thing you want feedback on — not your company, but the specific product surface, ticket, or session. Being concrete in {{2}} ('your recent support ticket', 'the AnalyticsPro dashboard', 'yesterday's onboarding call') does two jobs: it reminds the user precisely what they are rating, and it keeps the message unambiguously transactional. Pull both values live from your product database or CRM at send time so every recipient sees their own context.

• {{1}} — the customer's first name (e.g. Priya)
• {{2}} — the specific product, feature, ticket, or session being rated
• Keep {{2}} factual and event-specific — never a promotion or product pitch
• Map both fields from your CRM/helpdesk so they populate automatically per user

Approval and compliance tips

Submit this as a Utility template and provide realistic sample values for both variables so Meta's reviewers can see the message reads as a legitimate post-event check-in. Keep every word informational: no offers, no 'limited time', no marketing language anywhere in the body or buttons — a single promotional phrase is the most common reason a would-be utility template gets bumped to marketing or rejected. Consent still applies even for utility and authentication messages, so only send to users who have opted in to WhatsApp communication from you. If you localise the wording or tweak the phrasing later, re-submit the edited version for approval before sending — approved templates are locked to their approved text.

Variations you can copy

The base template works as-is, but you may want lighter or localised versions for different segments of your SaaS user base. Each variation stays within Utility rules as long as it remains purely a rating request tied to a real event. If you genuinely want to attach an incentive to boost response, treat that as a separate Marketing template — different category, higher rate, and a required opt-out line.

• Shorter: 'Hi {{1}}, how was {{2}}? Tap to rate.' plus the three buttons for fast sends
• Numeric scale: swap the emoji buttons for a follow-up asking a 1–5 or 1–10 rating in the reply flow
• Regional language: create a Hindi or vernacular version of the body and re-submit for approval
• With incentive: as a Marketing template only, add a thank-you reward and the mandatory opt-out line