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.
- Finding your way around — the full map: signing in, choosing your business, the home screen, links and sign-out.
- Choosing a layout design — the five looks the workspace can have, and the fact that the design resets each sign-in.
- Using the product dock — the product switcher: position, size, hiding, and what is remembered.
- Which product owns which screen — one account, two products (SMS and WhatsApp); why buttons can be greyed out.
- Checking your plan and your phone numbers — two read-only screens any member can open at any time.
- Reading your data-retention policy and rate limits — what the platform keeps, for how long, and the request limits in force.
- Reading your analytics reports — open a report, change what it covers, trust what the numbers mean (needs the analytics-read permission).
- Reading the Spend insight card — monthly category changes, anomaly flags and the assumption-labelled projection (counts messages only, never money; the route is not yet mounted on Main-built stacks).
For the business OWNER
- A day in the owner's seat — one continuous owner journey: drafting a campaign, the two-person approval rule, sending, the report and CSV, and drafting a template up to (never past) the Meta submission form.
- Appearance and dock preferences, with pictures — the same controls as the portal guides, illustrated.
For customer ADMINISTRATORS
You manage the business's settings, people and content.
People and roles:
- Inviting a teammate and withdrawing the invitation — the invite form and the one-time invite code shown exactly once.
- Setup and administration areas — the WhatsApp numbers screen, the full seat/invite life, custom roles (with the either/or role switch), and the billing hub.
Messaging content:
- Campaigns — the full life, the report and the CSV export — guard rails, approval, sending states, the honest report and the identity-protected export.
- Adding recipients to a campaign — the queue journey — the Queue button, the API-owned refusals (403/409/202) and the report that counts what actually happened.
- The consent gate on campaign recipients — the CONSENT_REQUIRED refusal, the recorded opt-in that recovers it, and the queue that still says "Delivery is not confirmed."
- Message templates — versions, editing and retirement — every edit is a new version; retirement is one-way; approval belongs to Meta.
- Creating a template in the studio — the create form, buttons, the version history that never rewrites, and the wizard's audience step (nothing submitted to Meta in the runs behind it).
- Importing contacts from a file — the header-row rule, the counted result receipt, and where contacts land.
Bots (need a plan that includes bots — Basic is messaging-only):
- Bot guides front door — the five bot guides: building a flow and the no-match fallback, capacity, saved versions and rollback, publishing, simulator and rollback, copying a bot, and export/import of flows.
Numbers, moves and money:
- Planning a move with the Migration readiness assistant — the readiness checklist inside your business (planning only; it moves no number).
- What the analytics numbers mean — the questions behind each report, for team leads who compare dashboards.
Security and integrations:
- Rotating credentials — your API key's
one-time
ctk_secret (Part 1, administrators) and the operator's provider-token drill (Part 2, operators). - Replaying a webhook delivery — consent rechecked before anything is sent; every refusal explained.
- The developer command line (CLI) — nine terminal commands with honest receipts, for technical teammates.
For EMPLOYEES (teammates who work the inbox)
- What a limited-role employee can and cannot do — the navigation as the permission map, reads that stay open, writes refused with the missing scope named, and tenant boundaries that hold against crafted requests.
- The customer drawer — record deals, follow-ups and internal notes that can never reach the customer.
- Handing a conversation to a teammate — claim, transfer and release, with the guard-rail messages.
- Finding your conversations — search, the All-mine filter, and the assignment-routing rule (the routing part is for administrators).
- Inbox guides front door
For VISITORS and prospective customers (no sign-in)
- Sending an enquiry from the public website — what the pricing-page enquiry form and the partner intake form send and never send, the honest received/already-received/refused answers, and the no-form shipping default until the intake endpoint is deployed.
For PARTNERS (resellers and affiliates)
- The affiliate program — frozen terms — the frozen commercial terms verbatim, and how every rupee is counted.
- Releasing a sub-organization, and recovering its first-customer invitation — end a reseller relationship without touching the customer's data or earned shares; re-arm the one-time invitation.
For the PLATFORM OWNER side (operators)
- Checking job health across all businesses — the read-only cross-business queue view that ranks every business worst-backlog-first, with counts and ages only (never message content).
The other product: SMS CRM
- SMS CRM guides — status index — the SMS CRM product has its own guide front door, which today is an honest status index, not chapters: no qualified, executed SMS CRM journey evidence is retained anywhere, so the page records exactly what exists and which journeys await evidence.
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:
- Campaigns — creating, sending and tracking a campaign — the owner journey records the browser legs (create → self-approval refusal → second-seat approval → scheduled-to-sending → honest report/CSV; Chief acceptance open), and the campaign lifecycle guide documents the server-side state machine, report funnel, searches and audited CSV from API-seam evidence (Chief acceptance open). Still with no journey evidence in this tree: seed acts, and anything after the honest report — the queue journey and the consent gate are now carried as their own chapters (queue, consent gate), lane-recorded with Chief acceptance open. The crosswalk's campaign-dashboard captures are reference images only and grant no runtime acceptance.
- Message templates — creating, editing and approving templates — the
owner journey shows the real Submit-to-Meta
form opened and then cancelled (status stayed "Draft", no Meta call;
Chief acceptance open), and the
version family guide
documents editing-as-new-immutable-version, the versions list, RETIRE and
the
META_APPROVAL_REQUIREDboundary from API-seam evidence (Chief acceptance open). Studio authoring itself is now carried as its own chapter (lane-recorded, Chief acceptance open; nothing in its runs was submitted to Meta). Still with no journey evidence: an actual submission to Meta, the live approval round-trip, and the rejections surface. - Contact management — adding, editing, importing and tagging contacts — the import journey (header-less refusal → counted recovery receipt → contacts-management listing) has lane-recorded passing evidence in the contacts import guide, pending Chief acceptance, now extended with the API-seam facts (guidance contract, XLSX first-worksheet validation, tenant-pinned import lists); the cohorts (segments) card there is a journey observation only, no feature claim. Still with no journey evidence: adding, editing, tagging or deleting individual contacts.
- Settings, seats and role management — the admin side has the
invite → one-time-token → revoke journey in the
seat invite/revoke guide (Chief
acceptance open), and the destinations guide
documents invite acceptance and seat deactivation plus custom
roles CRUD, the
ROLE_IN_USErefusal and either/or role assignment from API-seam evidence (Chief acceptance open). Still without a documented journey: changing a seat's role from the UI, the LAST_ADMIN guard, and every other settings surface — the employee limited-role experience is now carried as its own chapter (lane-recorded, Chief acceptance open). - Whole-SMSCRM/ConvoTide full guide — a single guide covering the complete product and all functional journeys. Still pending; no accepted whole-product evidence exists. The SMS CRM side has an honest status index naming exactly which journeys await qualified evidence.
- Live messaging-provider connection and genuine number cutover — no accepted evidence. The migration guide covers readiness planning only; using it moves no number and connects no provider.
- Live WhatsApp/Meta message delivery — no accepted evidence. All screenshots in the current guides are simulated test data.
How these guides are kept honest
- Each guide identifies its supporting evidence — a Chief acceptance file or a completed lane ledger — including the exact run, result and source revision, and states plainly when Chief acceptance is still open.
- Screenshots are copied byte-exact from the evidence; every image's SHA256 is recorded and re-verified.
- A local link check verifies every relative link and image reference in this tree resolves; its latest output is in LINK-CHECK.txt.
- Functions the evidence did not exercise are named as missing, never invented.
Evidence standing of the chapters (internal record, kept verbatim)
- The portal chapters are source-verified against the live static
portal deployed on Main383 (
5d939d74, verified 25 October 2026): every control, persisted key, default and behavior they describe was read from that commit's actual deployed source. They contain no screenshots — the pending live captures are listed in source-evidence.json (portal area entries; the portal area's earlier separate registry was merged into it on 25 October 2026). Journeys that need the API/WS application pair (session exchange, business resolution, entitlement answers, SMS CRM data) are marked pending app-pair there and are not claimed as live runtime. - The migration, flow import/export, capacity/versions/rollback
and analytics chapters are backed by Chief-accepted evidence sets
(
CT-MIGRATION2992,CT-FLOW3002,CT-BOT3021,CT-ANALYTICS3022/CT-ANALYTICS3044). - The inbox chapters are backed by the completed ZC-3132 INBOX-CRM-CONT
lane, run O4 (17/17 passed, single clean run). At authoring time Chief
acceptance was open (historical status, preserved); independent review
CT-INBOX-REVIEW3143 has since
accepted the inbox local candidate at HEAD
85bf2a878df1e2430354910e9718c3ed62a2c05b— a bounded local-candidate acceptance covering these journeys. Main PR #336 is Chief-reported source integration, not independently verified Main-built or live evidence here. - The publish/simulator and copy bot chapters are backed by the
completed ZC3132 BOT-CONT lane, runs publish-run2 (1/1), browser-run4
(3/3) and api-pg-run1 (2/2). At authoring time Chief acceptance was open
(historical status, preserved); independent review
CT-BOT-REVIEW3144 has since accepted
the bot local candidate at HEAD
23aecb51afdac01e67ae25d5e07f76c432ed8d07for the F1–F3 remedies and the bounded copy/simulator/D17.F01 journeys, keeping full frozen-snapshot and rollback graph fidelity OPEN. A later source-lane remedy (fe0d2b8ea) addressing that gap is received for separate review and is not retrospectively accepted here. - The security, developers, partners and platform chapters
(added 25 October 2026) are backed by the completed FULL3747-PG lane: the
mounted, executed surfaces of the combined candidate — 14/14 packet
suites plus the channel-halt re-qualification, all green on two
independent fresh-PG cycles (cycle 1 receipts recorded per-suite in the
lane ledger, cycle 2 green per its 2026-10-24T23:44:30Z state; one fix,
c2b87090, with the failing P19 original preserved verbatim). These chapters document API- and database-seam behavior with verbatim TAP receipts. Chief acceptance and publication are OPEN for all of them; the routes are mounted in the combined candidate only — no live or Main-built runtime is claimed. A sibling guides branch (codex/zcode-3456-guides) separately documented browser-journey chapters; the FULL3747-GUIDESREC reconciliation (25 October 2026) first folded in that branch's three BATCH3456-GUIDES-2 chapters (registered below), and the GUIDECOMPLETE carry (26 October 2026) then brought in that branch's remaining six chapters — registered in their own standing bullet below — so nothing qualified now lives only on the sibling branch. For the webhook-replay and disclosure topics this tree's newerwebhook-replay-consentanddata-classes-and-rate-limitschapters remain the standing evidence (the sibling variants were superseded, not carried). - The developer CLI chapter (added 25 October 2026) is the corpus's
first chapter backed by a Chief-accepted and Main-merged (PR #361)
contract suite:
CHIEF-P15-CLI-ACCEPTANCE3692.jsonrecords an independent execution ofnode --test integrations/cli/cli.contract.test.mjson 2026-10-24T20:22:29Z — 25/25 tests, exit 0 — scoped to Node, injected HTTP doubles and a loopback server through the real entrypoint (no live deployment, remote API, database or provider). The three source files on this branch were re-verified byte-identical to the receipt's sha256 pins at authoring time, so the chapter documents the exact accepted bytes. Live-origin behavior, the deployment base URL and a pre-created API key remain named dependencies, not claims. - The plan chapter and the browser sections folded into the
security/rotation, partners and platform chapters (25 October
2026) are backed by the completed FULL3747-BROWSER lane (ledger
C:/CT-ZCODE-FULL3747/lane-browser-ledger.json, final suite result2026-10-25T00:10:00Z): real Chromium over the composed candidate on a throwaway PostgreSQL database, SHA-bound spec91525180213363c87101971381d00502cd2b17600d5f66fa97782ea3edfba181. Journey 1 (entitlement + number-allocation reads: responsive 320/768/ 1440, axe clean, zero non-GET requests — attempt-1's fixture-gap failure preserved honestly) and journey 2 (the real rotation screen: cancel inert, one rotate POST,ctk_shown once, never re-revealed) PASSED. Journeys 3/4/5 FAILED at their entry-expectation (the mounted candidate raises no entry-time factor prompt on the member-scope partner/affiliate reads, and no platform MFA step-up exists on the platform orgs/job-health reads); their substance is proven only by the lane's supplementary SUP-J3/J4/J5 runs, labeled as such in the chapters, with backend defects FULL3747-B-01 (missing platform step-up) and FULL3747-B-02 (partner-read scope design decision) left OPEN. The lane's UI fix46fb35c8lives oncodex/zcode-full3747-browser, not on this branch's base. All captures are byte-exact with SHA256 in the per-treeASSETS-MANIFEST.json; Chief acceptance and publication are OPEN. - The campaigns, templates, bots flows/fallback, analytics
endpoints and destinations chapters, plus the contacts-import
API-seam section and the SMS CRM status index (added 25 October 2026),
are backed by the completed FULL3747-O14EV lane
(
C:/CT-ZCODE-FULL3747/lane-o14ev-ledger.json, window started 2026-10-24T23:41:34Z): four suites — S1 analytics 14/14 (commit808f4d3e), S2 bots 26/26 (commit3f49f092), S3 inbox/CRM/import 12/12 (commite4ba94b6), S4 campaigns/templates/destinations 24/24 (commit18d61080) — 76/76 cases executed green, 0 failed, as the real compiled application over real loopback HTTP against ordinary throwaway PostgreSQL 16 clusters (app roleNOBYPASSRLS, row security forced, verified inO14EV-HTTP-ROLE-RLS.json). Verbatim per-suite case receipts are retained underC:/CT-ZC-FULL3747/tools/zcode-integration3723/runtime/FULL3747-O14EV/evidence/(S1–S3) and…/runtime/evidence/o14ev-s4/(S4). Of the O14 matrix's 62 rows, the lane executed 61 green; 1 row (O03.22) is carried open to the browser lane and no content claim is made for it. These are combined-candidate, local evidence; Chief acceptance and publication are OPEN — no live or Main-built runtime is claimed, and the template SUBMIT/provider-status surfaces were exercised only to their provider-gated refusals (Meta submission is provider-gated; any APPROVED truth in the runs was seeded SQL). - The owner journey, contacts import and seat invite/revoke
chapters (folded in from the sibling
codex/zcode-3456-guidesbranch by the FULL3747-GUIDESREC reconciliation, 25 October 2026; originally added by the BATCH3456-GUIDES-2 fold-in from the BATCH3456 journeys lane final passing run — journey A owner legs, journey B contacts legs B3/B4/B5, and journey A seats leg A4 — three journeys in one chromium run, exit 0, 2026-10-24T12:29Z,codex/zcode-3456-journeys @ 9d2136cb) are lane-recorded candidate evidence with exact receipts. Chief acceptance and Main integration are open. Their honest boundaries are part of the chapters: the Submit-to-Meta form was opened and cancelled, never submitted (status stayed "Draft", no Meta call); the second-seat admin grant was a named fixture seam; the cohorts (segments) card is a journey observation with no feature claim; and the seat chapter documents invite-and-revoke only — acceptance, deactivation, role changes and LAST_ADMIN stay pending. The same XLR-1 collision boundary applies to the owner journey's scheduled-to-sending leg. - The GUIDECOMPLETE carry (26 October 2026, lane
C:/CT-ZCODE-RESUME4172/lane-4172guidecomplete-ledger.json) brought the six remaining sibling chapters fromcodex/zcode-3456-guides(three of them byte-identical oncodex/zcode-3310-guides) into this tree, rewritten to this corpus's customer-instruction standard with every receipt, verbatim message and synthetic/fixture label preserved: the template studio (BATCH3310 studio/ wizard suite, fresh lane run plus the 8/8 prior D52 receipt), the campaign queue journey (lane-3280 first journey + committed spec 1/1 oncodex/zcode-3310-o14@192496b1d, including the ZC3244-D1 Queue-button history), the consent gate and the employee limited-role journey (both from the BATCH3456 journeys final run, 3 journeys in one chromium run exit 0, 2026-10-24T12:29Z,codex/zcode-3456-journeys@9d2136cb; the consent chapter carries its XLR-1 collision boundary verbatim), the public-site enquiry and partner intake (BATCH3310 lane journey + AGOS 81/81 cross-engine matrix + 9/9 real-PG endpoint runs, with the no-form shipping default stated), and the spend insight card (implementation-lane PG/HTTP receipts with red→green regression + fresh 9/9 UI run; the route is not yet mounted on Main and the card's 404-honesty is documented). All six are local candidate evidence — Chief acceptance and Main integration OPEN; the first-generation chapters still living only oncodex/zcode-3244-guidesremain superseded by this tree's rewritten chapters and are not carried. - Throughout, the three source standings stay distinct: local candidate (the tested checkouts above), Main source integration (Chief-reported PR #336 — not independently verified here), and live/Main-built runtime (not claimed anywhere in these guides).
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.