Features for multiple WhatsApp numbers: Everything WavesFlo does, across your numbers and teams.
Link the numbers your stores, branches and teams already use, give every chat an owner, and send with approval and limits.
Numbers
Every number, in one workspace.
- Linked in about a minute: scan a code from the phone’s Linked devices screen.
- The phone keeps working: linked like WhatsApp Web, it carries on as before.
- Room to grow: up to 250 numbers on Growth and 50,000 on Enterprise, subject to plan.
- Access per number: open to everyone, or only to the teams and people you name.
How a number is linked and kept
Stores, branches and teams keep the numbers their customers already know. Each one is linked from its own phone and given a label, such as a store’s name.
Health. A score for each number, with the reason when it drops.
Allowance. Daily and hourly ceilings, set per number.
Separate. Each number has its own connection and allowance, so one can be restarted without touching the rest.
Recovery. Reconnect a number, or run a full automatic recovery.
Linked devices. Each number takes one of the four linked-device places on its WhatsApp account, and WhatsApp logs linked devices out if the phone goes unused for 14 days.
| Team or person | Level |
|---|---|
| North sales | Operate |
| Meera Pillai | Operate |
| Service team | View |
Operate: see its chats and act as it, to reply, send and assign. View: see its chats only.
Shared inbox
One list, an owner for every chat.
- Marked by number: each reply leaves from the number the customer wrote to.
- Assigned your way: round-robin within a team on Growth and Enterprise, or by hand.
- Hand-offs keep notes: managers and team leaders pass a chat on with its notes.
- Typing shows live: so two people don’t answer the same customer.
Inside the inbox
Roles and per-number access decide who can read and answer each chat.
One list. Direct chats and groups from every linked number, newest first.
Filters. By number, unread, assigned to you, the shared queue, label, or chat type.
Replies. Text, photos, documents, video, voice notes, a location or a contact card.
Delivery. Each message’s state, from sending through read and played, with the error when one fails.
Shared queue. Where a chat no one owns waits until it is assigned.
Retention. Choose how long message content is kept, or keep none of it.
CRM. One-to-one chats and opt-outs logged as notes on HubSpot or Zoho CRM contacts, once an Admin switches syncing on.
My service is due. Any slot on Tuesday?
Let me check Tuesday’s slots for you.
Tuesday 11:00 is free. Over to Joseph to book it in.
AI replies
Answers, drafts or off, set per team.
- Automatic answers: keyword replies, a chatbot and AI answer on their own.
- AI drafts: a reply is written for the team to check and send.
- Off: nothing automatic for that team.
On Growth and Enterprise, with AI credits included; more on request.
North sales
AI writes a draft; someone checks it and sends it.
Service team
Keyword replies, the chatbot and AI answer on their own.
Store managers
Nothing automatic for this team.
Campaigns
Campaigns that ask first, then start small.
- Approval: an optional sign-off before the first message leaves.
- A pre-send check: problems that would stop a campaign are reported before anything queues.
- Canary sends: large lists start with about 5%, pausing on failures or STOP replies.
- Lists or groups: message each person on a list, or post into groups.
How a campaign is built
Announcements and follow-ups go out as campaigns, from the numbers your teams already answer on, through the same targeting, scheduling, approval and sending limits.
Push campaign. One announcement, the same for everyone it reaches.
Deal campaign. One message for each row of a Google Sheet, written from that row’s details.
Message sources. Written from your instructions for each row, taken from your saved messages, or typed exactly as it should go out.
Attachments. An image, video, audio file or document, sent with the copy as its caption.
Status. Optionally post the same campaign to your status.
Canary limits. The campaign pauses itself if more than 20% of the first sends fail or 2% reply STOP; the rest wait until someone resumes it.
Lists, segments and opt-outs
Send into WhatsApp groups, or to people one by one from a list you uploaded. Segments are worked out from delivery data rather than kept by hand, so who is reachable never goes stale.
Import. A CSV, with a column-mapping step you confirm before anything is written.
Lists. A fixed set of people, from one import.
Segments. Read or replied, messaged but unread, and every send failed.
Opt-outs. Checked as each message is sent, across every campaign.
CRM import. HubSpot or Zoho CRM contacts with a phone number, on demand or every six hours; consent is never assumed.
Alerts
Alerts in Slack or Microsoft Teams.
- Where your team works: approval requests, campaign results and number alerts, in a channel.
- Approve from Slack: sign a campaign off without opening the dashboard.
- A calendar: scheduled and recurring sends, in one view.
- A live queue: each message’s status as it goes out.
Approvals, schedules and diagnostics
Approvals before a campaign sends, a calendar of what is scheduled, recurring sends, a queue you can watch as it goes out, logs, and diagnostics for when a number’s connection drops.
Approvals. Requested per campaign, and actioned from Slack without opening the dashboard.
Diagnostics. Connection state, last sync, and the groups held in memory.
Festive offers paused itself
Sent to the first 20 of 400 in North region. 2 replied STOP, above the 2% limit.
Sending limits
Limits on every number, on by default.
- Daily and hourly caps: 500 a day and 60 an hour per number, by default.
- A wait per person: 24 hours between campaign messages to the same person.
- Quiet hours: 22:00 to 08:00 by default, in your timezone.
- One emergency pause: halts delivery on every number at once.
Groups
See when a group is busiest, before you post.
- Busiest hours: member activity by the hour, in your timezone.
- Message mix: what members send each other: text, image or video.
- Top senders: who drives the conversation, and when they were last active.
- Membership: joins and leaves, rebuilt into a daily timeline.
Shown for every group your numbers belong to, with delivery and read rates per group, not averaged.
Reports
Eleven reports, counted, not estimated.
Each downloads as CSV and JSON, and conversations can be read through the API.
Campaign results
Targets, sent, failed, delivered and read, with reach counted once per person.
Timing
Time to deliver and to read, at the median and the 75th and 90th percentiles.
Delivery
Volume over time, status split, reactions and status reach.
Audience
Group performance, top groups by sends, sends per number, communities.
Campaigns
Health figures for every campaign you have run.
Compliance
Every send the limits held back or delayed, with the rule that caught it.
What the reports cover
The eleven cover delivery, audience, campaigns, compliance and operations. Every campaign closes with counts that came from delivery receipts, not from an estimate.
Confirmed reach. A floor of distinct people, deduplicated across groups, because the same person is often in several of them.
Surfaces. Direct, group and channel sends, reported separately.
Message log. Per message: status, receipts, the number it went from, the time.
Read rates. A lower bound: recipients can turn read receipts off.
What teams ask about the features.
All questionsHow long does it take to connect a WhatsApp number to WavesFlo?
About a minute. Open WhatsApp on the phone, go to Linked devices and scan the code the WavesFlo dashboard shows, then give the number a label. It joins your workspace with its own health score, its own daily and hourly ceilings, and a connection you can restart without touching anything else. The link takes one of the phone's four linked-device places, and WhatsApp must be opened on the phone at least every 14 days to keep it connected.
Can WavesFlo answer customers automatically for one team and not another?
Yes, on Growth and Enterprise. Each team in WavesFlo is set to automatic answers, where keyword replies, a chatbot and AI answer on their own; to AI drafts, where AI writes a reply for someone on the team to check and send; or to off. AI credits are included on Growth and Enterprise, and more are available on request.
What is the difference between a deal campaign and a push campaign?
In WavesFlo, a deal campaign reads a Google Sheet and writes one message per row, personalised from that row's data. A push campaign is one announcement. Both run through the same targeting, scheduling, approval and pacing, and either can post into WhatsApp groups or message each person on a contact list individually.
How does WavesFlo keep audience segments up to date?
WavesFlo derives engagement segments from delivery data rather than leaving anyone to maintain them by hand, so they keep themselves current. The segments are read or replied, messaged but unread, and every send failed. A contact list is different: a fixed set of people from one CSV import, with a column-mapping step you confirm before anything is written.
What happens when a WavesFlo campaign goes to a large list?
It starts small. A large list campaign goes to about 5% first, and pauses itself if more than 20% of those sends fail or 2% of people reply STOP; everyone else waits until someone resumes it. An optional approval comes before any of that, and every message stays within the limits of the number it leaves from.
What does WavesFlo show about each WhatsApp group?
For every group your connected numbers belong to, WavesFlo shows its busiest hours as a histogram of member activity in your timezone, its message mix across text, image and video, its top senders and when they were last active, a daily membership timeline rebuilt from joins and leaves, and delivery and read rates for that group rather than an average.
What results does a WavesFlo campaign report?
Every WavesFlo campaign closes with counts from delivery receipts: targets, sent, failed, delivered and read. Reach is counted as distinct people, deduplicated across groups; time to deliver and to read is given at the median and the 75th and 90th percentiles; and direct, group and channel sends are reported separately. Read rates are a floor: in one-to-one chats a recipient can turn read receipts off, and WhatsApp does not send a read receipt for every read.
See it on your own numbers.
A walkthrough on two of your own numbers, with your rollout questions answered.