Most small businesses do not decide to offer WhatsApp support. Customers simply start messaging the number on the website, and one day there are too many chats for the person holding the phone. The usual fixes, passing the phone around or opening WhatsApp Web on three laptops, keep the chats flowing but lose track of who answered what.
This guide is the operating side: how a team of two to ten people runs support from one WhatsApp number without the Business API. It covers roles, a simple rule for who answers what, response-time targets, after-hours replies, handovers between shifts and what to do when a teammate leaves, and ends with a checklist you can copy.
First decision: do you need the Business API?
For support, usually not. The WhatsApp Business API is built for messages you start at scale: order updates to thousands of customers, one-time codes, template campaigns. It needs an approved business, often a new or migrated number, and Meta charges for the template messages you send.
Support is the other way round. Customers write first, the number is the one they already know, and every conversation is a reply. A team inbox that connects to that number as a linked device, the way WhatsApp Web does, keeps the number and its history and adds the team layer: logins, roles, notes and targets.
- Stay on your current number with a team inbox if customers write to you, your volume is hundreds of chats a day or fewer, and most replies are written by a person.
- Look at the API if you mainly send first (reminders, confirmations, alerts), need thousands of messages a day, or want a verified green-badge sender.
Related: WhatsApp Business API pricing, explained · WhatsApp for teams: one number, your whole team
Keep one number, and make it easy to reach
Customers remember one number. Splitting support across staff phones means history scattered over personal devices, and customers who message whoever answered last time, even after that person has left. Keep support on the business number and put the team behind it.
In Spun the phone that owns the number scans a QR code once. Spun then uses one of the four linked-device slots WhatsApp allows, and every teammate signs in with their own login, in a browser or on their own phone. Nothing changes for the customer.
Then publish the number everywhere a customer might look: a click-to-chat link on the contact page and in the email signature, and a QR code on the counter, packaging and invoices. Pre-fill the first message ("Hi, I have a question about my order") so the chat opens with context.
Related: Free WhatsApp link generator · Free WhatsApp QR code generator · WhatsApp Business on multiple devices, phones and users
Roles: give each person only what the job needs
A support team rarely needs everyone to have everything. Spun has four roles, enforced on the server, and individual permissions can be switched per person. Viewer, Team Member and Manager work inside the saved filters you share with them; Full Control is the whole inbox. A person with no shared filter sees nothing, which is a safe default for someone who has been invited but not yet trained.
| Person on a small support team | Role that fits |
|---|---|
| Owner, or whoever pays for the plan and owns the phone | Full Control: the whole inbox, billing, inviting and removing people, the WhatsApp QR |
| Support lead who sets rules and covers gaps | Manager: messaging, contacts, labels, alarms and payments, plus campaigns, auto replies and the dashboard, inside the shared filters |
| Agent answering customers every day | Team Member: send, schedule, AI replies, saved replies and archive, inside the shared filters |
| Trainee in their first week, or an accountant checking a dispute | Viewer: read-only, no actions |
Partial access cannot be combined with Full Control. A specialist, such as the person who handles refunds, can be a Team Member whose only shared filter is the "Refunds" label.
Related: How to share a WhatsApp Business account with your team, safely
Who answers what: one simple rule
The failure mode of a shared number is not silence, it is two people answering the same customer, or each assuming the other has it. Write down one rule and make the inbox show it. A rule that works for most teams of two to six:
- 1
A new chat goes to the next person in rotation
Spun's rotation puts a teammate's name label on each new incoming one-to-one chat, in the order and weight you set (1 to 20), only while that person is inside their work hours. Someone on leave is paused until a date. Groups and chats you started are left out.
- 2
The name label means "yours until handed back"
This is a team convention, not a lock: the label does not stop anyone else from replying or change who can see the chat. Agree that nobody replies on a chat carrying a colleague's label unless it is flagged or overdue.
- 3
Check presence before you type
Every chat row shows the initials of anyone viewing it, grey while reading and amber while typing, and the composer warns you when a colleague is already typing. It warns, it does not block, so the habit matters.
- 4
Topics go to specialists by label
Keep a short set of topic labels (Order, Refund, Technical). The lead applies them, or an auto-reply rule adds one on a keyword such as "refund". A specialist whose shared filter is the Refund label sees those chats. Team Members cannot change shared labels, so an agent flags a chat for the lead with a note and an @mention. Five topics get used, fifteen get ignored.
Unread, archive, pin and mute are shared: when one person opens a chat, it is read for everyone. Do not use "unread" as your to-do list. Use a "Needs reply" label, or the first-response countdown below, so opening a chat never hides it from the rest of the team.
Related: How rotation labels new chats
Response-time rules the team can actually keep
A response target is only useful if it is visible while people work. In Spun a manager sets a first-response target in minutes, optionally counted in business hours only, with a warning at a chosen percentage. Every member sees a live countdown on waiting chats, and managers see the history of missed targets and a leaderboard: messages sent, conversations touched, average first response and the share answered within target, per person.
Worked example, a four-person team (Ana, Marcus, Priya and Tom) on weekday shifts:
| Situation | Rule |
|---|---|
| New customer message, business hours | First reply within 15 minutes; warning at 80%, so the chat turns urgent at 12 minutes |
| Countdown warning on a colleague's chat | Whoever sees it first posts a note with an @mention to the named person; if no answer in 3 minutes, they reply |
| Question needs someone else (refund, technical) | Reply within the target to say who will answer and roughly when, then @mention the lead in a note to move the label |
| Outside business hours | The away message answers (next section); the countdown restarts at opening time |
The first reply does not have to solve the problem. It has to tell the customer a person has seen it.
After-hours auto replies that do not annoy
An auto reply is the right answer outside business hours and the wrong one during them. Spun's auto-reply rules can fire on "outside business hours", on a customer's first message ever, or on a keyword, and send fixed text or one of your saved replies.
- 1
Say when a person will answer
Example: "Thanks for your message. We are closed now and reply from 9:00 on weekdays. If it is about an existing order, send your order number and we will start there." Promise a time you will keep.
- 2
Set a cooldown
A customer who sends five messages at night should get the away message once, not five times. Rules carry a cooldown (with a minimum even when you set none) and daily and lifetime caps.
- 3
Give holiday rules an end date
A rule can expire on its own, so a holiday closing message switches itself off when you reopen.
- 4
Triage first thing
At opening time, work the chats that arrived overnight before new ones: they have been waiting longest.
Related: AI auto replies and away messages
Handovers between shifts, with summaries
A customer should never have to repeat themselves because the shift changed. Three shipped tools make a handover take a minute instead of a re-read of fifty messages:
- AI summary: open the AI icon in the chat header and choose Summarize. You can ask a specific question ("what did we promise?"), choose how many recent messages it reads and the summary language. It lists voice notes it skipped and offers to transcribe them, and can suggest tasks from the conversation.
- Team notes: a private note on the conversation that every teammate sees and the customer never does. Notes are create and delete only, so write the final state ("Refund approved, waiting for bank details"), not a draft. An @mention in a note sends that colleague a push notification.
- Follow-up alarms and tasks: a Manager can set a follow-up alarm on a chat, private by default or shared with the team, or turn a promise into a task from the conversation, with a due date, so "I will check tomorrow" survives the shift change.
A handover note that works: what the customer wants, what has been done, what is promised and by when, and who picks it up (with an @mention).
When a teammate leaves
This is where shared phones and shared logins hurt most: nobody knows what the departing person can still open. With one login per person, leaving is a short list.
- 1
Remove them from the team
Access ends immediately. Removal also removes the Gmail sending identity, the hosted home connection and the API access set up under that membership. You cannot remove yourself, so the owner stays.
- 2
Take them out of rotation
Turn their rotation row off (or pause it before the last day) so new chats stop getting their name label.
- 3
Re-label their open chats
Chats already carrying their name label keep it. Filter by that label and move each open conversation to a colleague, with a note.
- 4
Reassign their tasks and alarms
Check the task board and shared alarms for anything they were responsible for.
- 5
Check the phone's linked devices
If they ever scanned the business number into WhatsApp Web on their own laptop, log that device out from the phone: Settings, Linked devices.
The customer notices nothing: the conversation history stays in the shared inbox and the number never changes.
The small-team WhatsApp support checklist
Copy this into your team handbook and tick it off once; the daily and weekly lines become the routine.
| When | Check |
|---|---|
| Setup | Number connected once from the owner's phone; each person invited with their own login |
| Setup | Roles set: one Full Control, a Manager for rules, Team Members for agents, Viewer for trainees |
| Setup | Rotation order, weights and work hours set; topic labels limited to five or so |
| Setup | First-response target, business-hours mode and warn-at percentage set |
| Setup | Away message with a cooldown; holiday rule with an end date |
| Setup | Saved replies for the ten most common questions, shared with the team |
| Setup | Click-to-chat link and QR code published with a pre-filled first message |
| Every shift | Overnight chats first; "Needs reply" label cleared; countdown warnings answered |
| Every shift end | Open chats have a handover note or summary; promises are tasks or alarms |
| Weekly | Leaderboard and missed-target history reviewed; saved replies updated |
| Someone leaves | Removed, out of rotation, chats re-labelled, tasks moved, phone's linked devices checked |
Related: WhatsApp for teams in India: rupee prices and Indian workflows