Customer conversation operations

Every customer conversation has context. Every action has an owner.

Connect a customer-controlled WhatsApp account, coordinate the shared inbox, launch consented campaigns and automate bounded workflows from one accountable workspace.

Start with a test workspace See how it works

Unofficial linked-device transport · Consent required · Account restrictions remain possible

**Operational overview** Connection health, workload and plan usage in one frame

One operating model

From first connection to measurable response.

The public story mirrors the product: connect safely, work together, scale deliberately and retain only what the plan allows.

Connect with disclosure

Pair a customer-controlled account through a short-lived QR or code and keep linked-device risks visible.

Coordinate the inbox

Assign owners, preserve contact context and move conversations through explicit states.

Campaign with consent

Snapshot eligible audiences, exclude suppressions and inspect recipient outcomes.

Automate bounded work

Publish versioned rules with test traces, handoff and operational logs.

Product proof

The interface—not a stock illustration—is the hero.

Current product screens demonstrate the real interaction model customers will use.

**Shared inbox** Ownership, thread and contact context

**Automation builder** Versioned rules with explicit paths

Trust through clarity

What the product does—and what it will never claim.

Built forCustomer-owned accounts and consented messaging

Designed aroundWorkspace isolation, auditability and predictable retention

Not promisedOfficial Meta approval, ban-proof operation or guaranteed delivery

Plans

Capacity and retention grow with the workspace.

Commercial amounts are not invented here. Final values come from the SaaS plan catalogue.

Start

Test one operating flow

Plan-defined account, message, contact and retention capacity.

Coordinate

Bring the team into the inbox

Plan-defined seats, campaigns, webhooks and media retention.

Scale

Govern higher-volume operations

Plan-defined capacity, controls, exports and support.

Review the complete plan structure

Common questions

Understand the operating boundary before signing up.

Is this an official WhatsApp API provider?

No. Release one uses an unofficial WhatsApp Web linked-device connection to a customer-controlled account. The connection may be logged out, restricted or require re-pairing.

Can I message any phone number?

No. Customers must have a valid lawful basis and recipient consent. Suppressions and opt-outs are enforced before campaigns.

Where do plans and billing live?

Plans, subscriptions, transactions and account management remain in the separate SaaS member portal. The product application consumes plan entitlements.

Can the WhatsApp engine change later?

Yes. Product contracts are engine-neutral, but a future engine may require account re-pairing or a separate credential migration.

A deliberate first step

Start with one customer-controlled account.

Create a workspace, read the connection disclosure and send a safe test before inviting your team.

Create test workspace Read the quick start