Control Room
Control Room

THE WORKBOOK

An AI bot incident runbook for inbox operators

A clear pause, triage and recovery record for a limited automation trial.

By Onlytool · Published 10 September 2026

These are illustrative planning scenarios, not reports of vendor tests or customer outcomes. Adapt the examples to an account you are authorised to operate. Use the field guide for the underlying method and the interactive tool for your own inputs.

Download the worksheet

THE SITUATION

A message contains an unsupported promise

An operator sees an output that exceeds the authorised account brief.

Work through it

Pause the affected workflow, preserve the relevant event reference and assign the correction to the account owner. Inspect whether similar actions remain queued.

What to check

Do not assume editing the brief changes messages already prepared or sent.

THE SITUATION

A duplicate send appears

The same intended action reaches the recipient more than once.

Work through it

Record event IDs, timestamps and the observed order. Check retries and duplicate handling through the provider’s supported controls.

What to check

Resume only after the relevant test demonstrates that the duplicate condition is handled.

THE SITUATION

The operator loses access

The person responsible for the trial cannot reach the normal dashboard.

Work through it

Use the documented secondary contact and access-revocation route. Transfer responsibility to the named backup owner.

What to check

A recovery plan that depends on the unavailable operator is incomplete.

YOUR WORKING DOCUMENT

Keep the decision
with the evidence.

Use the plain-text worksheet in your own approved system. It contains headings only, so you control which information is recorded and where it is stored. Nothing entered in a downloaded file is returned to this publication.

Save the blank worksheet ↓
INCIDENT RECORD
Time / time zone:
Account and workflow reference:
Reported by / incident owner:
Observed issue:
Scope currently known:
Pause action and confirmation:
Pending actions inspected:
Evidence references:
Human correction owner:
Cause / provider response:
Retest evidence:
Resume decision and reviewer:

Common mistakes to avoid

  1. Calling a completed checklist a compliance certificate.
  2. Starting without a backup owner for the stop procedure.
  3. Restarting after an incident because the dashboard looks normal without checking the cause.

Before implementing a workflow, confirm that it is supported by the chosen product and permitted under current platform rules. A planning example does not establish either. OnlyFans terms.

Check rollout readiness