How to Send Personalized WhatsApp Campaigns in India

A personalized WhatsApp campaign is not a broadcast with a first name at the top. It is a message that goes only to the customers it is about, and uses details they already gave you: the saree they asked about, the locality they want to buy in, the date of their daughter's wedding.

That difference matters more on WhatsApp than it does on email. WhatsApp may limit how many marketing messages a person receives based on how often they read the ones they already get. Every blast that gets ignored makes the next campaign harder to deliver.

This guide shows how to build a personalized campaign in Querygen, one step at a time: store what customers say as profile fields, turn those fields into an audience, write a message that fills itself in, and plan for the replies.

What personalization means on WhatsApp

There are three levels, and most campaigns stop at the first one.

1. Name. "Hi Priya" instead of "Hi there." Every tool can do this, and customers stopped noticing it years ago.
2. Context. The product they asked about, their city, their budget, what they bought last time. This needs a stored fact about each person.
3. Timing. Sending because something happened: they asked for a price three days ago and haven't ordered. This needs a record of when things happened.

Most Indian businesses already have levels two and three sitting in their chats. A customer who writes "Do you deliver to Nashik? Need 2 kg kaju katli for the 12th" has told you her city, the product, the quantity, and the date. The problem is that those facts live in a chat bubble, not in a field you can filter on.

Step 1: Decide which customer facts matter

Before you open a campaign, list the three to five facts that would change what you say to someone. Keep the list short. A field nobody uses in a campaign is a field nobody keeps accurate.

In Querygen these are profile attributes. You create them in Settings, choose a type (text, number, yes or no, date, or a single choice from a list), and write one line telling Querygen when to update the value. For example: "Preferred locality: the area in Pune the customer says they want to buy in. Update it if they name a different area."

Querygen then reads your direct-message conversations and fills the values in. Your team can check or correct any value from the customer's profile or the Inbox, and your website or billing system can update them through the API. If you already use WebEngage, CleverTap, or MoEngage, the same attributes can sync to those tools.

Step 2: Record the moments that matter as events

Attributes describe who someone is. Events record what happened and when: asked for a price, requested a quote, placed an order, raised a complaint. Each event appears on the conversation's timeline.

Events are what let a campaign arrive at the right moment. "Asked for a price in the last seven days and has not ordered" is an event rule. So is "ordered 30 days ago and nothing since," which is how a hardware shop reminds regular buyers to restock without messaging everyone. Querygen can detect events from what customers write, and your own systems can send them through the API.

Step 3: Build the audience from rules, not a spreadsheet

Querygen campaigns can use six kinds of audience: individual contacts, WhatsApp groups (on a personal number), a CSV with a phone column, conversation labels, rules, and saved segments. Rules are where personalization starts.

A rule can require an event to have happened, or not happened, within a time window. It can match a stored attribute, exclude a value, or check whether an attribute has been filled in at all. You preview the matching customers before you use the audience.

Save a set of rules as a segment when you'll use it again. Rule and segment audiences use their current members at the moment the campaign runs, and a saved segment refreshes at the time and timezone you set. That is the part a spreadsheet can't do: the customer who ordered this morning is not in tonight's "still thinking about it" campaign.

Step 4: Write a message that fills itself in

In the campaign editor, type {{ to insert a field: the customer's name, their phone number, or any profile attribute you created in Step 1. Add a fallback in quotes for customers whose value is empty, so nobody receives "Hi ,":

On an official WhatsApp Business API number, a message to someone who hasn't written to you in the last 24 hours has to use a template that Meta has approved. Querygen shows your approved templates in the editor, and you fill the template's variables with the same fields: name, phone, or any profile attribute.

A few rules make the difference between a message people answer and one they mute:

• Name the exact thing. "The 3 BHK in Baner" beats "our new project."
• Give one true reason to reply now. A restock, a price change, a batch that starts on a date. If there is no reason, wait until there is one.
• Ask a question they can answer in one word."Saturday 11 or 4?" gets more replies than "Let us know if interested."
• Write like the salesperson, not the brand. Customers reply to people. They ignore posters.

Step 5: Choose a broadcast or a sequence

A broadcast sends one message to the whole audience. You can send it now, schedule it once, or repeat it daily, weekly, monthly, or on a custom interval with an end date. Use it for news that is true for everyone in the segment: a restock, a new batch, an event. For when a plain broadcast is the better choice, see WhatsApp broadcast vs targeted campaigns.

A message sequence sends several messages with growing gaps between them, and stops for a customer the moment they reply. Use it when the decision takes a few days, like a course admission or a home purchase. Nobody who has already said "yes, book it" gets a "just checking in" message two days later. Querygen lets you test the whole timeline before you switch it on.

Step 6: Send from the right number

Querygen can send campaigns from a personal WhatsApp number your team already uses, or from an official WhatsApp Business API number. They suit different jobs.

If you're sending to more than a few dozen people who don't talk to you every week, use an API number. Read why WhatsApp numbers get banned before you run a campaign from a personal number, and how to set up the WhatsApp Business API in India if you don't have one yet.

Step 7: Plan for the replies

A good campaign creates conversations. If 38 people get the Kanjeevaram message and 12 of them reply "photos pls" at 10 pm, somebody has to answer, and the ones who don't reply need a second nudge.

• Autopilot answers product and price questions from your catalog and hands discounts or custom requests to your team. See how to automate WhatsApp replies.
• A lead tracker adds everyone who shows buying intent to your sales board, linked to the chat.
• A follow-up nudges customers who stop replying, and stops when they answer. See how to automate lead follow-up.

What it costs in Querygen

The Querygen plan is ₹9,900 + GST a month and includes 9,900 credits. Each campaign message Querygen sends uses 1 credit, which is ₹1 on the INR plan. On a WhatsApp Business API number, Meta also charges you directly for each delivered marketing template at its published rate for India.

Personalization saves money here too. The 38-person Kanjeevaram campaign uses 38 credits. The 4,200-person Diwali blast uses 4,200, plus Meta's fee on every one.

Before you press send

Consent is not optional on the Business API. WhatsApp's Business Messaging Policy requires permission before you message someone, and an imported contact list does not prove that permission on its own.

Frequently asked questions