ConvoTide user guides — start here

Sign in to your workspace and select your business. Your role and enabled products determine which screens you can open.

These guides explain how to use ConvoTide (the WhatsApp business workspace) in plain, everyday language: what you will see, what to click, and what to do when something refuses. They are organized by who you are — pick your role below and start with its guides.

Everything here is written only from qualified evidence of the real application: every button name, message and screen in a guide was actually seen during an accepted or lane-recorded passing test run of the product. Guides state plainly which kind of evidence stands behind them, and what is not yet available.

All screenshots come from isolated, synthetic test businesses used for product acceptance testing. They show simulated test data — no live customer traffic, and no live WhatsApp/Meta message was sent in any of the runs behind these guides.

Find your guides by role

For everyone who signs in

No special permission needed — this is the workspace itself.

For the business OWNER

For customer ADMINISTRATORS

You manage the business's settings, people and content.

People and roles:

Messaging content:

Bots (need a plan that includes bots — Basic is messaging-only):

Numbers, moves and money:

Security and integrations:

For EMPLOYEES (teammates who work the inbox)

For VISITORS and prospective customers (no sign-in)

For PARTNERS (resellers and affiliates)

For the PLATFORM OWNER side (operators)

The other product: SMS CRM

Plan note that affects several guides

The Basic plan is one person including the owner, one WhatsApp number, messaging-only — no bots and no AI, and changing a seat's role cannot unlock them. Guides that need a second seat (campaign approval) or bots say so at the top.

Not yet covered — missing evidence

The guides below do not exist yet, because qualified journey evidence for them has not been recorded or accepted. They are named here so nobody mistakes silence for coverage. No placeholder or claimed-complete guide is offered for any of them:

How these guides are kept honest


Evidence standing of the chapters (internal record, kept verbatim)

The full per-chapter evidence map (acceptance files or lane ledgers, source commits, screenshots used, link-check status) is in source-evidence.json. The full asset tree with SHA256 checksums for every screenshot is in assets-index.json.