Production checklist

Use this checklist for a new assistant or a material release. Record the published version and the channel you actually tested.

Configuration and evidence

• The selected organisation and provider accounts are correct, with fresh successful connection tests.
• The assistant's prompt, first message, language and timezone match the business task.
• Required documents are processed, selected and approved for public disclosure.
• Validated-answer sources are reviewed and unexpired; unsupported questions produce the intended fallback.
• Required intake fields, refusal and exit paths pass their flow tests.
• Published tools have the intended inputs, destinations and permissions.

Customer channel

• The intended assistant version is published and assigned to the channel.
• A widget's exact origin is allowed and its own configuration is published.
• A phone number is owned and real inbound/outbound routing has been tested where offered.
• A WhatsApp channel is verified, callbacks are configured and the required formats work.
• A new session on the actual channel shows the intended version in Logs.

Actions and privacy

• A real test action succeeds with approval and is blocked when declined.
• Unknown or interrupted action results do not cause duplicate submissions.
• Transfer and handoff paths have been tested where offered.
• Recording, analysis and memory consent choices are clear and independent.
• Retention and deletion settings match the information you intend to keep.

Usage and operation

• Available AI credits and, for paid voice, runtime USD cover the expected traffic.
• Maximum call duration, monthly wallet cap and concurrent-call allowance are appropriate.
• Someone is responsible for reviewing call failures, outcomes and webhook delivery.
• Your evaluation suite passes and you know how to restore a draft and publish a correction.

Begin with a controlled pilot. Review call logs and usage, then increase traffic when actual results support it.