Start with an explicit customer request or a useful connection to a past purchase. Check stock and contact preference, send a specific message, then record the response. A clothing purchase is not a fixed reorder schedule.
Start with why this customer would care
Someone who asked you to call when a size arrives has a clear reason to hear from the shop. A customer who bought a wedding outfit last month may have no reason to buy another now. Put the request or occasion beside the name before deciding whom to contact.
Shopify's customer-segment documentation shows that purchase-related filters and email subscription status can be treated separately. That is a useful distinction: a purchase record explains relevance, while a recorded preference tells you which channel and updates the customer has agreed to receive. An email subscription does not establish agreement to phone or chat promotions.
Build three small lists
| Customer context | Useful follow-up | Check before contacting |
|---|---|---|
| Asked for an unavailable size | The requested size has arrived | Exact style and colour; piece physically available |
| Bought an outfit and asked about matching options | One or two suitable additions | Actual match, price and customer preference |
| Requested new-season updates | A relevant selection from the new range | Category interest and contact preference still valid |
Keep shoppers with an unresolved return or complaint out of an ordinary promotional list. Resolve their service issue first. Do not infer private occasions or personal circumstances from a purchase pattern.
Write the message around the request
For a stock request: “Namaste, aapne blue kurta size M ke liye poocha tha. Woh ab available hai, ₹850. Photo bhej doon?” This example is illustrative. Use the price and availability your staff has just checked.
For a requested matching item: “The plain dupatta you asked about is available in two shades. Would you like photos beside the kurta you selected?” The customer can answer without opening a catalogue or explaining the original request again.
Avoid “You are our valued customer” followed by an unrelated offer. Also avoid claiming a piece is reserved unless your team has actually held it and recorded an expiry time.
Measure what happened, not how many messages went out
Here is a fictional review of one small follow-up batch. Twenty customers had asked for stock updates. Eighteen messages were delivered, six customers replied and four placed orders.
Reply rate among delivered messages is 6 ÷ 18 = 33.3%. Order rate among delivered messages is 4 ÷ 18 = 22.2%. These are example calculations, not benchmarks or expected results. Count each customer once and define the response window.
Record the four orders, but do not assume every rupee was caused by the message. Some customers might have returned anyway. For an early manual trial, the more useful notes may be “wrong colour,” “already purchased elsewhere” or “asked us not to contact again.”
Keep the list small enough to maintain
- Customer reference and agreed contact channel.
- Requested item or reason the recommendation is relevant.
- Availability checked at a recorded time.
- Message date, reply and next action.
- Closure reason, including no further updates requested.
A family-run shop can begin with ten live requests in a register. A larger store can assign the list to a staff member, with ownership for reservations and replies. In both cases, remove stale requests and honour a request to stop.
The useful habit is remembering what the shopper asked for. More frequent messaging is not a substitute for that memory.
Questions you might ask
How often should I message a clothing customer?
Base contact on a request, relevant new availability and the customer’s preference. Do not impose a universal repeat-order interval on apparel shopping.
What should I track after a customer follow-up?
Track delivery, reply, next action, any reservation and resulting order within a defined window. Record requests to stop and reasons the offer was not relevant.