WhatsApp for retail chains: one inbox for every store number
How a retail chain runs WhatsApp across stores: a number per store, region-level oversight, local ownership of chats, store-level access and paced campaigns.
- Written by
- By WavesFlo team
- Published
- Published
- Reading time
- 3 min read
A retail chain's customers already know each store's number. The job is to keep that, while giving the head office a single view and each store control of its own chats. That means a number per store, access set by role and number, a regional layer above the stores, and campaigns that go out from the number a customer knows.
How should the chain be arranged?
| Layer | Who | Sees and does |
|---|---|---|
| Store | Store staff as Agents | Only the chats assigned to them, replying from the store's number |
| Store lead | A Team leader per store or cluster | Their own and their team's chats; hands chats on with notes |
| Region | A Manager per region | Every conversation; works the shared queue; grants number access |
| Head office | Admin | Links numbers, sets roles, connects the CRM, owns the sending limits |
| Quality | Viewer | Reads, never replies |
What does a store do every day?
- Answer the chats on the store's number, from the store's own login, with an owner on every one.
- Pass a chat to a colleague, or to another store, with the notes attached.
- Leave a chat nobody owns in the shared queue for the region to pick up.
- Use saved messages for the questions that come every day: timings, stock, returns.
How do campaigns work across stores?
A campaign can go out from the number each customer knows, spread across numbers with a modest daily share each, under daily and hourly ceilings, a cooldown per person across campaigns and quiet hours. An optional approval means a regional manager signs off before the first message leaves, and a large list starts with about 5% and pauses itself on failures or STOP replies. Campaigns across many numbers covers the pacing.
How do you keep every store's number healthy?
Each number has its own health score with the reason when it drops, and a recovery action if the connection fails. A store phone that sits unused for 14 days is logged out by WhatsApp, so someone owns keeping each phone used. WhatsApp number health lists the warning signs.
What does the first month look like?
- Week 1: link the flagship and one store in each region; set roles and number access.
- Week 2: add the rest by region; name a store lead and a regional manager for each.
- Week 3: set saved messages for the questions every store gets, and the opening hours and replies.
- Week 4: run a first small campaign with approval, from the number each customer knows, and read the report.
What are the usual mistakes?
- Linking every store at once.
- Giving store staff access to every number.
- Sending one campaign from one number to everyone.
- Leaving store phones unused until WhatsApp logs them out.
Every one of those mistakes is easier to avoid when each store keeps its own number and the head office still sees them all, which is how WavesFlo runs a chain of store numbers. The quote is built on the store numbers and staff you connect, billed once a year, and no message is charged on its own.
Questions
Can a retail chain run WhatsApp on a number per store?
Yes. Each store's number is linked from its phone, and every chat lands in one inbox marked with the number it arrived on.
Can store staff see only their own store's chats?
Yes. Access is set per number and per role, so an Agent sees only the chats assigned to them.
Can head office see every store?
Admins and Managers reach every conversation, and a Viewer can read without replying.
How do I stop one store's campaign flooding customers?
Each number has daily and hourly ceilings, and a cooldown per person applies across campaigns.