WhatsApp post-purchase messages: what to send after the sale and what to leave out

WhatsApp post-purchase messages are the communications you send after a sale to confirm the order, report its progress, answer usage questions and ask for feedback. They do three concrete jobs: the customer never has to ask “where is my order”, they learn to use the product properly, and when things go well they leave a review or buy again.

Post-purchase is not marketing in disguise. A customer who has just paid is watching their order and open to hearing from you, but that goodwill is short. If the first thing they get is an offer, they learn your number is advertising and stop reading it exactly when it could be most useful. The rule underneath is simple: useful information first, conversation second, commercial last.

There is a less obvious benefit: good post-purchase work lightens your team's load. A large share of the inbound messages in an online store are questions the customer would not have asked if the right information had arrived on time. Each proactive notice prevents several reactive tickets, and that frees hours for the cases that really need a person.

The minimum sequence has four moments: an immediate confirmation, a shipping notice, a check-in after delivery and an invitation to review. Everything else is optional and gets added only once those four work.

The confirmation goes out the moment payment clears. Its job is to set expectations: what they bought, when it should arrive and where to write if something changes. Klaviyo, for example, recommends sending the first WhatsApp right after purchase to confirm the order. The shipping notice goes out when the parcel leaves the warehouse and includes tracking. For more on how order data reaches the chat, see our page on AI agent for Shopify, which explains how order data reaches the conversation without the customer having to ask.

The third message arrives a day or two after delivery and asks something simple: did it arrive in good shape? Nothing more. The fourth, the review invitation, goes out once the customer has had time to use what they bought; the exact timing depends on the product and we cover it in our article on when to ask for a product review.

Picture a specialty coffee shop selling 250-gram bags. A customer pays on a Tuesday and immediately gets a message with the order summary and the estimated date. When the courier picks up the parcel, a notice arrives with the tracking link. Two days after delivery, another message asks whether the coffee arrived properly sealed and offers a short guide to grinding it for their brewing method.

Ten or twelve days later, when the bag is nearly empty, the review invitation shows up, asking for a photo, along with an optional restock reminder. That is four or five messages in total, each with a reason the customer understands. None is a sales pitch. The reorder happens because the experience was good and the reminder landed at the right time, not because a discount was pushed.

Notice the tone: every message names the actual product and the customer's situation instead of a generic line. It is the difference between “your order has been processed” and “your Huila coffee ships today; we will tell you when it lands.” The second reads in two seconds and feels written by someone who knows what they sold.

It is too many when customers stop opening them or start blocking your number. There is no universal figure, but there is a practical test: every message should be justifiable with a sentence like “I am writing because they need to know X.” If you cannot finish that sentence, the message goes.

Two mistakes are common. The first is doubling channels: sending the same notice by email and WhatsApp at once. Klaviyo warns that overloading customers can raise unsubscribes and suggests alternating channels. The second is chaining reminders when the customer does not answer: an unanswered review invitation is let go, not repeated three times. Also, only message people who gave consent, and check that each send uses the right template category; our guide to marketing vs. utility templates explains the difference.

Automate anything driven by an event with a predictable answer: payment confirmed, order shipped, order delivered. Anything that needs judgment, such as a complaint, a damaged product or an upset customer, should go to a person with the full context.

This is where a rigid flow falls short, because customers rarely answer the way the tree expects. With heysteff automation flows, steps are triggered by events in your business, wait for a reply or a set amount of time and, if the customer writes something unexpected, the agent converses toward a clear goal instead of repeating a menu. If the person describes a problem, escalation rules route it to your team.

Post-purchase works when repeat questions go down and reviews and reorders go up, not when messages sent go up. Track three things: how many “where is my order” questions you get before and after, what share of customers answer your check-in and how many reviews arrive per hundred deliveries.

Read the negative responses too. A message that draws complaints or awkward silence is badly framed or badly timed. Change one thing at a time so you know what caused the shift. And remember that a small sequence that gets maintained beats a huge one nobody reviews.

One last habit worth keeping: review the sequence every quarter starting from the same question, which questions are still arriving that a timely message would have prevented? Those questions are your list of missing messages, and they also tell you which current ones you can drop without anyone noticing.

When should the first post-purchase message go out? Right after payment. Its job is to confirm the order and say when it should arrive, so the customer does not have to ask.

Can I offer a discount in post-purchase? Yes, but not as the first or second message. Do it after the customer has received and used the product, and only if it fits their purchase history. Before that, the experience comes first.

What if the customer replies with a problem? Route the conversation to a person with the full order history. Automating the notice is fine; automating the resolution of a complaint without judgment is not.

• Automation flows for WhatsApp
• When to ask for a product review
• heysteff Reviews: reviews over WhatsApp
• AI agent for ecommerce