Bot guides — building, publishing and copying bots

Who these guides are for: customer ADMINISTRATORS — every bots journey needs a seat with bot-management permission.

Plan prerequisite for every bot guide: these journeys need a plan that includes bots. The Basic plan is messaging-only — it excludes bots and AI entirely, and changing a seat's role cannot unlock them there. See the Basic plan refusal.

The five guides, each written only from real, qualified evidence of the actual app:

  1. Building a bot flow and the no-match fallback — the block types you can use, the rules that keep a flow valid, and what happens when a customer writes something no block matches. (Evidence FULL3747-O14EV S2, Chief acceptance open)
  2. Bot capacity, saved versions and rollback — your plan's active-bot limit, the read-only saved version history every publish creates, and two-step rollback. (Evidence CT-BOT3021, Chief-accepted)
  3. Publishing a bot, testing in the simulator, and rolling back — the draft/published lifecycle as one journey, the publish guard, why the first publish is version 2, and the nothing-is-sent dry-run simulator. (Evidence ZC3132 BOT-CONT runs publish-run2 + browser-run4; since accepted as a bounded local candidate by review 3144 — full snapshot/rollback content fidelity remains open)
  4. Copying a bot — duplicate a bot as a new draft in one click, on desktop and phone, with the member-seat refusal and the administrator recovery. (Evidence ZC3132 BOT-CONT runs browser-run4 + api-pg-run1; since accepted as a bounded local candidate by review 3144 — fixture-contract scope, not arbitrary-graph fidelity)
  5. Moving a bot flow between bots — export and import — download a bot's flow as a portable file and bring it back as a brand-new draft bot, with every refusal message explained. (Evidence CT-FLOW3002, Chief-accepted)

Selected screenshots live in the assets/ folder (assets/flow/ and assets/capacity/ for the Chief-accepted guides, assets/publish/ and assets/copy/ for the ZC3132 guides). Per-image provenance and SHA256 checksums are in assets/ASSETS-MANIFEST.json (flow/capacity) and assets/publish-copy-ASSETS-MANIFEST.json (publish/copy).

All guides use screenshots from isolated synthetic test businesses; the examples are simulated test data, not live customer traffic. Areas without qualified evidence are intentionally absent, not forgotten.


Evidence standing (kept for honesty). Current standing of the ZC3132 guides: at authoring time Chief acceptance of the bot lane was open (historical status, preserved). Independent review CT-BOT-REVIEW3144 has since accepted the bot local candidate at HEAD 23aecb51afdac01e67ae25d5e07f76c432ed8d07 for 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.