Personalisation

Why it matters for engagement, cost and deliverability

Relevance is the single biggest lever on WhatsApp performance. A message that names the customer, references their actual order and speaks to their city reads as a service, not spam — so people open it, tap the button, and reply. A generic "Dear customer, check our offers" invites the opposite: it gets ignored, and worse, it gets blocked and reported. That feedback matters because block and report signals feed directly into your WhatsApp quality rating and messaging limits; a run of irrelevant blasts can throttle how many users you're allowed to message per day. Cost is the other half of the story. Since Meta moved off per-conversation billing on 1 July 2025, you pay per delivered message by category — marketing, utility or authentication — so every send you make counts, whether or not the recipient found it relevant. Personalisation is how you make each of those paid deliveries earn its place instead of quietly training your audience to mute you.

How it works at scale — from a spreadsheet row to a merged send

At volume, personalisation is a data-mapping problem. Your platform holds the approved template, and for each recipient it needs a clean value for every variable. Those values come from a CSV upload, a CRM sync, or an API call from your app at the moment an event fires (order shipped, payment due, booking confirmed). The platform substitutes each value in order, validates that no variable is empty, and dispatches the message under the correct category. Utility templates — order updates, OTPs' delivery status, appointment reminders — are usually the richest in personalisation because they're tied to a specific transaction, and they can be sent even outside the 24-hour window because they're template-based. On InfiQ this runs on transparent ₹ pricing (ex-GST), so you can see exactly what a personalised utility or marketing campaign will cost per delivered message before you press send, and size your audience accordingly.

• Map each {{n}} to a specific field in your data source, in order
• Trim, format and sanity-check values (dates, currency, casing) before merge
• Never leave a variable blank — WhatsApp rejects sends with missing values
• Pick the right category (utility vs marketing) — it drives both approval and cost

Common mistakes that break personalisation

Most personalisation failures are avoidable and predictable. The classic one is a mismatched column: your CSV shifts by a field and suddenly {{1}} is an order ID and {{2}} is a phone number, so thousands of customers get "Hi 48213". Another is missing data — a blank name or null city — which either ships an awkward gap or, more often, gets the whole message rejected because WhatsApp does not allow empty variables. Businesses also over-personalise into content that looks promotional inside a utility template (stuffing an offer into an "order shipped" message), which risks rejection and category downgrades. Finally, teams forget that personalising the visible text is not consent: sending a beautifully merged marketing message to someone who never opted in still drives blocks and hurts your quality rating. The fix is boring but reliable — validate your data mapping on a small test segment, add fallback defaults for optional fields, keep utility and marketing content cleanly separated, and only send to an opted-in audience.

• Column drift — variables mapped to the wrong data field
• Empty variables — blanks cause rejection, not just ugly output
• Promo content smuggled into utility templates — rejection and downgrade risk
• Treating merged text as consent — always send to opted-in contacts only