Skip to content

Bot governance

  1. Open Bots. The Published versions tab lists every published version with its company, bot, role, model, voice, honesty check result and deny-list matches. Use the filter All, Needs attention or Suspended; Load more pages on.
  2. Click a row to see the matched lines in a panel.
  3. Press Suspend this version, write a reason (at least 8 characters) and type SUSPEND. The box says the version stops taking calls for that company at once; calls already up continue. Allowed for platform_support and platform_owner.
  4. To undo it, press Unsuspend on the suspended version and confirm. It takes no reason.

Suspending twice keeps the first time and reason.

Behind the screen: GET /bots, POST /bots/versions/{version_id}/suspend, .../unsuspend.

Every published bot version is scanned on what the voice service would actually run: the instructions compiled with no call details. The scan reports:

  • Hard rules present. The product’s baked rules (no invented facts, no card or bank details, honouring a stop request, one question per turn) must appear in the text. Missing ones are listed by id. The rules a workspace can edit or remove per bot, such as the recording notice or the AI disclosure, are not part of this check. See honesty rules.
  • Deny-list matches. Each match shows the rule, its severity, the line number and the line itself (cut at 240 characters). At most 50 matches per version.

A version is flagged when a hard rule is missing or anything matched. The Needs attention filter shows the flagged ones.

A platform-wide list of phrases. The starting list covers claims to be human, guarantees and false government affiliation.

Field Meaning
label A short name
pattern The phrase, or a regular expression
is_regex Default false: the phrase matches anywhere, ignoring case
severity warn or block
enabled Default true

An empty pattern or a regular expression that does not compile is refused. Manage it on the Deny list tab of Bots: add, edit or delete a phrase (GET/POST /bots/denylist, PUT/DELETE /bots/denylist/{id}).

  • Core and the voice service refuse to start a conversation with that version. The message says bot version <id> is suspended by the platform: <reason>.
  • Checking a campaign reports a problem on every step that uses it.
  • Calls already up continue.
  • Publishing again or setting a version live does not lift a suspension. Only unsuspend does.

Core keeps no audit table of its own for this. The gateway writes the company’s visible audit line.