The WhatsApp workspace, feature by feature.

A shared Super Inbox for official Cloud API conversations, with status, priority, notes, and message history.

• Inbound WhatsApp messages arrive through Meta's official webhook path and stay scoped to the connected business.
• Agents can organize threads with open, pending, and resolved statuses, plus internal notes that are never sent to WhatsApp.
• When a workspace is connected in live Meta Cloud API mode, authorized users can reply through the official Graph API. WhaOne does not invent provider message IDs.

A tenant-scoped contact record for every customer, with tags, custom fields, consent, and CSV import.

• Contacts are unique per organization by normalized phone number and can be archived without deleting message history.
• Tags, custom fields, notes, and messaging consent live inside the workspace and are not sent to WhatsApp automatically.
• CSV import and export are available for authorized roles, with validation and bounded job sizes.

Assign conversations to people or teams, with role-based views for My Inbox, My Team, and Unassigned.

• Owners, admins, and managers can assign conversations to members or teams in the same organization.
• Agents can work unassigned threads and conversations on their own teams, and cannot open another agent's assigned thread.
• Assignment is workspace state. It does not transfer WhatsApp numbers or Meta assets between users.

Create local WhatsApp template drafts and submit or sync them through Meta's official template APIs when live.

• Draft templates are stored in the workspace with Meta-compatible categories, languages, and variables.
• Submit and sync call Meta only when the workspace is connected in live Cloud API mode. Drafts are never presented as Meta-approved.
• Templates are prepared for later campaign and conversation use; creating a draft does not send a message.

Plan audiences, map template variables, preview eligibility, and run dry-runs before an official send.

Live sending requires a connected Meta Cloud API workspace.

• Campaign planning includes audience definition, consent-aware eligibility, template selection, and recipient snapshots.
• Dry-run execution validates the plan without calling Meta send APIs.
• Live campaign send uses Meta's official Cloud API only when the workspace is connected in live mode. Delivery metrics are recorded from real provider events, not estimates.

Workflows that tag contacts, update fields, and assign or update conversations from workspace events.

Workspace actions are available. WhatsApp send steps are not available yet.

• Triggers include contact and conversation events such as created, updated, tagged, or status changed.
• Actions today update CRM and inbox state: tags, fields, assignment, status, priority, and internal notifications.
• WhatsApp send, webhook, HTTP, and AI agent nodes are reserved and cannot be activated in the current product.

Date-range reports from live workspace data for conversations, contacts, teams, and agents.

• Reports are tenant-scoped and built from existing WhaOne tables, not from guessed totals.
• Conversation, contact, team, and agent activity can be reviewed over selected date ranges.
• WhatsApp sent, delivered, and read counts are shown only when real provider events exist. Missing delivery data is not displayed as zero.

Session-based access, role permissions, PostgreSQL row-level security, encrypted WhatsApp tokens, and audit logs.

• Each request resolves the signed-in user to their active organization. Tenant data is not selected from a client-supplied organization header.
• Roles (owner, admin, manager, agent) are enforced on the server. Platform administration is a separate operator layer.
• WhatsApp access tokens are encrypted at rest. Session tokens are opaque and stored only as hashes.

A documented public API for third-party integrations is not available yet.

• WhaOne currently exposes an authenticated product API for the web workspace. That API is not a published public integration platform.
• A developer API with customer-facing keys and public integration docs is planned, not shipping in this website.

Assisted replies and AI workflow steps are not part of the current product.

• No AI agent, suggested reply, or model-backed automation step is enabled.
• If AI features are added later, they will be labeled clearly and will not send unofficial WhatsApp traffic.