Skip to content

WavesFlo Enterprise: Every number and every team, in one WhatsApp workspace.

For consumer businesses that sell through stores, branches, dealers and sales teams, each answering customers on its own number.

Who it is for

For businesses that answer customers from many numbers.

  • Automotive dealer and showroom networks

    Sales and Service desks at every showroom.

  • Real estate developers and brokerages

    A team per project, and an owner for every buyer.

  • Lending and insurance distribution

    Branch teams that see only the numbers they work.

  • Education and admissions

    An Admissions desk per campus; counsellors see their own chats.

  • Retail and consumer brands with store networks

    Every store’s number in one inbox.

  • Travel and holiday sales

    Holiday desks that hand a traveller on, notes and all.

Shared inbox

Every number, one workspace.

  • Phones keep working: numbers link from WhatsApp’s Linked devices screen.
  • Marked by number: each chat shows the number it came in on.
  • Replies match: answers go out from that same number.
How the inbox works
Illustration

Ownership

An owner for every conversation.

  • Assigned your way: round-robin within a team, or by hand.
  • Hand-offs keep notes: managers and team leaders pass chats on.
  • Typing shows live: see when a colleague is already answering.
  • People leave, chats stay: with their notes and labels.
How to assign chats
Illustration

Automation

AI replies, team by team.

  • Set per team: automatic answers, AI drafts for review, or off.
  • Keyword replies: a set answer whenever a keyword arrives.
  • A chatbot: for the set flows you choose.
  • AI credits included on Growth and Enterprise; more on request.
How AI replies work
Illustration

Access

Control by role and by number.

  • Five roles: Admin, Manager, Team leader, Agent and Viewer.
  • Open or restricted: each number open to all, or to named teams.
  • View or operate: see a number’s chats, or reply and assign too.
  • Admins only: linking numbers, connecting a CRM and changing roles.
Who sees what
Illustration

Controls for sending at scale

  • Approval before sending

    An optional sign-off before a campaign’s first message leaves.

  • Canary sends

    About 5% go first. It pauses itself if more than 20% fail or 2% reply STOP.

  • An emergency pause

    One switch halts delivery across every campaign and every number.

  • Slack or Microsoft Teams alerts

    Approval requests, campaign results and number alerts.

CRM

Your CRM stays the record.

  • Built in: HubSpot and Zoho CRM connect natively.
  • Off until switched on: nothing syncs until an Admin turns it on.
  • Chats become notes: one-to-one chats and opt-outs, on the matching contact.
  • n8n and Power Automate: through the REST API and signed webhooks.
How the CRM connection works
Illustration

Security

Made for your security review.

access
Roles and number access, enforced on the server.
audit trail
Who changed roles, members, teams, number access, campaigns, settings, API keys and CRM connections, and when.
sign-in
Personal logins, passwords of at least 12 characters, a lock after 5 failed attempts, and sessions that end after 24 hours.
retention
Content kept 30, 90, 180 or 365 days, forever, or not at all; when it ends, the message record stays.
data
Processed in India, unless your agreement says otherwise.
separation
Each workspace’s data kept apart, and covered by automated tests.
opt-outs
Checked before every send. CRM imports never count as consent.
dpa
Notice before a new sub-processor, the list on request, and your data returned or deleted at the end.
procurement
Your security questionnaire, answered in writing.

Buying

How Enterprise is bought.

  1. A walkthrough on two of your own numbers

    With your rollout questions answered.

  2. A quote set on numbers and team members

    Volume pricing, with no minimum.

  3. An annual agreement, the DPA, and an NDA if you need one

    Reductions take effect at the next renewal.

  4. Onboarding with our engineers

    Numbers linked, teams and access set, HubSpot or Zoho CRM connected.

Limits, stated plainly.

Three things to know before you plan a rollout.

restricted chats
Chats with WhatsApp’s Restricted chat setting turned on stay on the phone.
history
Starts when a number is linked.
sending limits
On every number, with floors no setting removes.
See the full list

Questions

What buyers ask before a rollout.

  • How many numbers can we connect?

    Up to 50,000 on Enterprise and up to 250 on Growth, subject to plan. Messages are not metered.

  • Does every agent see every chat?

    No. An Agent sees only the chats assigned to them, and a Team leader sees the chats of their own teams.

  • How do people join the workspace?

    By invitation, in the role you choose. You share each invitation link yourself; it works once and expires in seven days.

  • What support comes with Enterprise?

    A direct line to our engineers. Growth has a named support contact, and Developer has email support.

Plan your rollout with us.