Personalising customer conversations without pretending to be human

Most personalisation is a merge field. "Hi Rajesh," followed by the same paragraph everyone else received. Customers worked out that trick years ago, and a message that pretends to be personal while obviously not being so costs more trust than a plainly generic one.

Relevance beats familiarity

What customers respond to is not being addressed by name. It is receiving something that could only have been sent to them: the status of their order, a reminder for their appointment, a reply that refers to what they asked last week.

That kind of relevance is a data problem, not a copywriting one. If the message can be assembled from what you already know about this person’s situation, it will land. If it cannot, no amount of warmth in the template will rescue it.

Three things worth personalising

• Timing — an appointment reminder the evening before, not a batch send on Monday morning.
• Channel — reach people where they already read. In India that is overwhelmingly WhatsApp.
• Content that is specific to their record — the order, the application stage, the report that is ready.

Say what you are

Automated messages should read as what they are. A clear "this is an automated update about your order" respects the reader more than a message engineered to feel hand-written. Keep the automated channel for things that are genuinely useful to know, and let a person handle the conversation when it becomes one.

This is why Vaarto tracks the 24-hour customer service window rather than hiding it. Inside that window you are in a conversation and can reply freely. Outside it, you are sending a notification and should be honest that you are. The distinction matters to the person on the other end.

The test

Before sending anything, ask whether this message could have been sent to anyone else on the list. If it could, it is not personalised, whatever the first line says. If it could not, you probably do not need to dress it up.