WavesFlo FAQ: What large teams ask, answered.

WavesFlo is WhatsApp software for large consumer businesses: every number their stores, branches and teams use, in one shared inbox, with an owner for each conversation, access set by role and number, and notes in HubSpot or Zoho CRM. AI replies, a chatbot and round-robin assignment come on Growth and Enterprise. The name is sometimes written Waveflo or Waves Flo; it is the same product, made by Eclipse Private Limited. See every feature.

Large consumer businesses whose customers write to their stores, branches, dealers and sales teams on WhatsApp: dealer and showroom networks, real estate, lending and insurance distribution, admissions, retail and travel. Each keeps the numbers its customers know, in one workspace, with an owner for every chat. Sales teams sharing several numbers use it too. See WavesFlo Enterprise and WhatsApp for sales teams.

Yes. Each campaign either posts into the WhatsApp groups you pick or messages each person on a contact list individually.

Yes. Preview the messages against your data, run the pre-send check, and send a test to your own phone before anything is queued.

Yes. An optional approval step holds the campaign until a person signs off.

Book a demo: a walkthrough on two of your own numbers, with your rollout questions answered. We send an enquiry from a phone in the room, assign it, answer it from the shared inbox and show it logged in HubSpot or Zoho CRM. If campaigns matter too, bring a spreadsheet and we build one during the call.

Yes. Every conversation from every connected number arrives in one list, and a reply goes out on the number that conversation came in on. See how the inbox works.

Yes. Conversations are assigned by round-robin within a team or by hand, or left in a shared queue; a colleague typing in the same thread is shown live, and each conversation carries internal notes the customer never sees.

Yes. Direct chats and groups from every linked number are in the same list, and either can be filtered to on its own.

Yes. A number is either open to the whole workspace or restricted to the teams and people you name, at one of two levels: see its conversations, or operate as it. A conversation outside somebody's reach is not returned to them at all.

Admins and Managers reach every conversation, and Managers manage the inbox's own settings; only Admins link numbers, connect a CRM, change workspace settings or change roles. A Team leader reaches their own and their teams' chats. An Agent reaches only what is assigned to them. A Viewer reads everything and changes nothing.

Invite each person in the role you choose: Admin, Manager, Team leader, Agent or Viewer. You share each invitation link yourself; it works once and expires in seven days.

As long as your workspace chooses: a year by default, or thirty, ninety or a hundred and eighty days, forever, or not at all. When content expires the message stays as a record that it happened. Turning storage off stops new content being kept and does not delete what is already stored.

No. Search matches a conversation's name, its number and its latest message, not every message ever sent. It is for finding the conversation, not for finding a phrase inside one.

Partly, and deliberately. A reply passes the opt-out register, the emergency pause, the number's daily ceiling and the circuit breaker. It skips quiet hours and the per-recipient cooldown, which exist to stop a campaign arriving at the wrong moment — answering somebody who just wrote to you is not a campaign.

Yes, in six states rather than two ticks: sending, sent, delivered, read, played for a voice note that was listened to, and failed with the error that caused it.

Yes. Enquiries from every connected number arrive in one inbox. Round-robin hands each new chat to the next person in a team, or a manager or team leader hands it on by hand or leaves it in the shared queue, and an agent sees only the conversations assigned to them. See WhatsApp for sales teams.

Yes, on Growth and Enterprise: round-robin gives each new chat to the next person in the team, in turn. Managers and team leaders can still hand a chat on with its notes, or leave it in the shared queue, and a live typing indicator stops two people answering the same customer. See how to assign WhatsApp chats.

Yes, on Growth and Enterprise. Each team chooses automatic answers, AI drafts for someone to review, or off. AI credits are included on Growth and Enterprise; more on request.

Yes, on Growth and Enterprise. Keyword replies send a saved answer when a message matches, and a chatbot takes customers through the steps you set. Both answer for teams set to automatic answers, and a person can always take over the chat.

Yes. HubSpot and Zoho CRM connect natively: once an admin switches syncing on, each one-to-one chat and opt-out is added as a note on the matching contact. For other CRMs or a sheet, the signed message.received webhook sends each new chat to your systems, and n8n or Power Automate connect through the REST API and signed webhooks. WavesFlo is not itself a CRM. See WhatsApp to Google Sheets.

Yes. Quick replies are saved once for the whole workspace and recalled by typing a slash and the shortcut. Where a team turns on AI drafts, AI writes a draft and someone checks it and sends it.

The same way WhatsApp Web is linked: open WhatsApp on the phone, go to Linked devices, and scan the code the dashboard shows. The connection guide walks through it.

Up to 250 connected numbers on Growth and up to 50,000 on Enterprise, subject to plan.

Yes. Work is spread across your connected numbers instead of queueing behind one, and each number keeps its own limits.

A score kept for every connected number, with the reason shown when it drops, beside that number's daily allowance.

How many messages a number may send in a day. The default is 500, with 60 an hour, and reaching it takes the number out of rotation until the window resets.

You are told, and campaigns continue on the numbers that remain. The dashboard has reconnection and full-recovery tooling, so one number dropping does not stop the others.

From the dashboard: reconnect the number through Linked devices, or run the full automatic recovery.

Each number has its own connection, limits and health score, so a disconnect or a reached limit on one does not stop the others. Whether WhatsApp restricts a number is WhatsApp's decision.

In India, unless your agreement says otherwise, and always scoped to your workspace. You choose how long message content is kept: 30, 90, 180 or 365 days, forever, or not at all. We keep a current list of sub-processors, give notice before adding one, and send the list on request.

Contacts, lists, campaign definitions, message bodies and the delivery and read receipts they produced, plus group membership data. Reporting is computed from those source records.

Yes. Every query is scoped to one workspace, and no workspace's data informs another's.

Error reports are scrubbed of phone numbers, tokens and keys before they are stored.

Who changed roles, members, teams, number access, campaigns, settings, API keys and CRM connections, and when.

With personal logins: passwords of at least 12 characters, a lock after 5 failed attempts, and sessions that end after 24 hours. Each person signs in with a username of the form name@workspace.

Eleven reports download as CSV and JSON, covering delivery, audience, campaigns, compliance and operations, and a signed webhook sends each incoming message to your systems as it arrives. When the agreement ends, we return or delete your recipient data on request, and keep the opt-out records so nobody who opted out is messaged again.

Developer is ₹1,999 per session and Growth is ₹2,999 per session a month, each including one team member and one connected number. On Growth, each additional team member is ₹499 a month; each additional number is ₹999. Enterprise is priced on quote. AI credits are included on Growth and Enterprise; more on request. See pricing.

A session is one login to your account, with access to one product category. It includes one team member and one connected number. On Growth, each additional team member is ₹499 a month; on either plan, each additional number is ₹999 a month. Add a session for each further product category.

No. Developer starts at ₹1,999 per session a month with one team member, one connected number, the full API and the campaign builder. The shared inbox, roles, approvals, schedules, segments, the chatbot, AI replies and round-robin start on Growth. Book a demo for a walkthrough on two of your own numbers first.

Developer is ₹1,999 and Growth ₹2,999 per session per month, each with one team member and one connected number. On Growth, each additional team member is ₹499 a month; each additional number is ₹999 a month. Enterprise is quoted on volume. Messages, groups, members, API calls, webhook deliveries and exports are not metered.

Developer and Growth are monthly, per session; Enterprise is billed annually.

It is the platform ceiling on how many WhatsApp numbers one workspace can have connected at the same time: up to 250 on Growth and up to 50,000 on Enterprise, subject to plan. Each number keeps its own connection, its own health score, its own daily and hourly allowance and its own sending limits.

With AI credits, included on Growth and Enterprise; more on request. Each team chooses automatic answers (keyword replies, the chatbot and AI replies), AI drafts for someone to review, or off.

₹999 a month for each additional connected number, on Developer and Growth. Connected numbers are subject to plan.

Yes. Add numbers whenever you need them. Reductions take effect at the next renewal.

No. Enterprise is an annual agreement with the data processing addendum. We answer your security questionnaire in writing and sign an NDA on request.

Developer has email support, Growth a named support contact, and Enterprise a direct line to our engineers, who also run your onboarding. On any plan you can write to hello@wavesflo.com.

Talk to us. It is a conversation about your requirements rather than a checkout option, and the answer depends on how many numbers you run.

Yes. A Google Sheet can feed a campaign: WavesFlo reads it as the campaign's source and writes one message per row, personalised from that row's data. See Google Sheets to WhatsApp.

Yes. Write instructions once and a message is drafted for every row of your sheet.

No. You can send a saved message from your library, or type a message and send it exactly as written.

Yes. Schedule campaigns, set recurring sends on a calendar, and limit sending to a posting window and allowed weekdays.

Yes. A campaign can carry an image, video, audio file or document, with your copy as its caption.

Yes. Posting the same campaign to your status is optional on each campaign.

An automatic check that runs before a campaign is queued and reports any problem that would stop it, so you fix it before anything leaves.

A list campaign to 200 or more people goes to about 5% first, and pauses itself if more than 20% fail, or if at least two people and more than 2% reply STOP.

Yes. The queue shows live, per-message status, and the message log records each message's status, receipts, number and time.

In WavesFlo, 500 a day and 60 an hour per number by default. Both are configurable. See all the sending limits.

Yes. A randomised delay of 30 to 300 seconds by default, so sends never arrive on a fixed rhythm.

No. A 24-hour cooldown per recipient applies across campaigns, not only within one.

Yes. Quiet hours (22:00 to 08:00 by default) and allowed weekdays apply in your timezone; a campaign scheduled outside them waits.

Yes, two. In the shared inbox, when a colleague is typing in the same chat it shows live, so two people do not answer one customer. In a campaign, the recipient sees the number typing, briefly, before each message; it is on by default.

Use the emergency pause. One switch halts delivery across every campaign and every connected number.

Opt-outs are enforced by the delivery engine at send time, across every campaign, so a person who opted out is skipped.

Not under the acceptable use policy, and the delivery engine enforces opt-outs at send time across every campaign. Imported lists you did not collect consent for are the fastest way to lose an account.

No tool can promise that a number will never be restricted, and WavesFlo does not. It gives you randomised gaps, per-number caps, cooldowns, quiet hours, health scores and an emergency pause, so every campaign can be sent carefully.

Yes. The limits are enforced in the delivery engine, so a message sent through the API passes the same checks as one sent from the dashboard, the per-recipient cooldown included.

Create a campaign, choose WhatsApp groups as the audience and select the groups. Sends are paced per number. The step-by-step guide covers it.

When that group's members are most active. Each group shows a busiest-hours histogram in your timezone, so you can schedule into its peak.

No. A message posted to a group reaches everyone in it. When some members should not receive a message, send to a contact list instead.

Yes. Each group shows its top senders and when they were last active.

Yes. Delivery and read rates are reported per group rather than averaged across a campaign.

Yes. Joins and leaves are rebuilt into a day-by-day membership timeline for every group.

Each group shows its message mix across text, images and video, so you can match the format members already use.

Delivery and read counts are read from delivery receipts, not estimated from sends.

No, and the reporting is explicit about it. Read information comes from delivery receipts, and recipients can turn read receipts off in their own settings. Read rates are reported as a floor rather than a census.

Distinct people, deduplicated across every group and list a campaign touched, because the same person is often in several groups.

Yes. Direct messages, group posts and channel posts are reported separately.

Reports give time to deliver and time to read at the median and the 75th and 90th percentiles.

Yes. Eleven reports across delivery, audience, campaigns, compliance and operations, each as CSV and JSON.

Yes. Every send that was delayed or blocked is counted and exportable, with the rule that caught it.

Yes. A REST API with scoped keys. Sends and other create actions accept an Idempotency-Key: a retry with the same key within 24 hours returns the first result instead of repeating the action. See the developer reference.

Yes. The full REST API, the 20 published, signed webhook events and the agent server are on every plan, Developer included. The API is not an upsell.

Yes. 20 published, signed webhook events across messages, groups, consent, campaigns and numbers, delivered at least once and retried with backoff.

Compute an HMAC-SHA256 over the X-Wavesflo-Timestamp header, a dot and the raw body, compare it with the X-Wavesflo-Signature header in constant time, and reject stale timestamps. The webhooks guide has code.

Yes. Connect n8n through the REST API and signed webhooks, so a workflow can send a message or start from any webhook event.

Yes. Power Automate connects through the REST API and signed webhooks, so a flow can send a message or start from a webhook event. See WhatsApp with Power Automate.

Yes, both. Approval requests, campaign results and number alerts, such as a disconnected number or a blocked send, arrive in the Slack or Microsoft Teams channel you choose.

Yes. An agent server exposes tools to list numbers and groups, draft, preview, run the pre-send check, send one test and read results. There is no tool that launches a campaign.