A WhatsApp Business label system that survives a busy week
Most people make a dozen WhatsApp labels and abandon them in a month. Here's a small label system built around pipeline stages that you'll actually keep using.
Almost everyone who discovers WhatsApp Business labels does the same thing: makes fifteen colourful labels in an excited half hour, uses them for a week, and quietly abandons them. A month later the labels are a mess — some chats have three, most have none, and the whole thing tells you nothing.
The problem isn't labels. It's that most label setups are too detailed to maintain. A system that only works when you're calm is useless, because the whole point is to survive the busy days. Here's a smaller system built to do exactly that.
The rule: labels are pipeline stages, not descriptions
The mistake is labelling what a customer is — "VIP", "wholesale", "Instagram", "interested in facial". Those pile up, overlap, and never tell you what to do next.
Instead, label where a customer is in the process. A good label answers one question: what needs to happen with this person now? That means a customer sits in exactly one stage at a time and moves forward as things progress. It's a pipeline, built from labels.
The five labels that are enough
You need fewer than you think. Five stages cover almost any small business:
| Label | Means | Your next action |
|---|---|---|
| New | Just messaged, not yet handled | Reply and qualify |
| Quoted | Got a price, deciding | Follow up in a few days |
| Follow up | Went quiet, still warm | Reach out, continue their sentence |
| Closing | Ready to buy, sorting details | Remove obstacles, get it done |
| Customer | Bought | Nurture, ask again later |
That's it. Resist adding more. Every extra label is another decision during a busy afternoon, and decisions during busy afternoons are exactly what don't happen. Five stages you always apply beats fifteen you apply sometimes.
How to actually run it
The system only works if moving a customer between stages becomes a reflex. Two habits make that happen:
Re-label when you act. Every time you deal with a chat, update its label before you close it. Answered a new enquiry with a price? Move them from New to Quoted. They said "let me think"? They're Follow up now. The label always reflects the last real thing that happened.
Work by label, not by inbox. Once a week, open the Follow up label and go down it — that's your list of warm people to re-contact, already gathered. Open Closing and push each one over the line. This is the payoff: instead of scrolling a chaotic inbox hoping to spot who needs attention, you open a stage and everyone in it needs the same thing.
The honest limit of any manual system
Here's the catch, and it's the same catch every label article skips. This works right up until the day you're slammed — and that's the day it matters most. On the busy afternoon when thirty chats land at once, nobody re-labels anything. The system falls behind precisely when you needed it, and a pipeline that's a week out of date is barely a pipeline.
Labels are a real improvement over nothing, and if you run them by the rule above you'll lose fewer people. But be clear-eyed that they depend on your discipline in the exact moments you have least of it. The reason Dokwise reads your chats and surfaces the follow-ups automatically is to remove that dependency — so the "who's gone quiet" list is always current, whether or not anyone had a free hand to tag it. Until then, five labels, applied every time, is the version most likely to survive contact with a real week.
Set it up in ten minutes
Delete whatever labels you have now. Create five: New, Quoted, Follow up, Closing, Customer. Go through your last thirty active chats and put each into exactly one.
Then, for one week, follow the one rule: re-label a chat whenever you touch it. If the system is still intact after your next busy week, it's the right size. If it fell apart, it was never the labels — it was that maintaining any manual pipeline by hand is the hard part, and worth solving properly.