Go-live checklist
What Taliiq checks before a test call or deploy, how to fix each item, and what FAILED means in Observe.
Go-live checklist
When the go-live checklist feature is enabled for your organization, the dashboard tells you what is missing before you test or deploy an agent. You can fix most items with one click.
Checklist steps
The agent page shows four steps:
- Create agent — you already have an agent.
- Test passed — a console test finished successfully with at least one user turn and one agent reply.
- Channel connected — a web widget, inbound SIP endpoint, or inbound phone number points at this agent.
- Go live — the agent is published and running.
Readiness checks
Before a console test or deploy, Taliiq runs these checks:
| Check | Meaning | Typical fix |
|---|---|---|
| Voice selected | A voice-capable agent needs a voice (or a realtime voice setting). | Pick a voice for me, or choose one in Setup. |
| Providers connected | Speech recognition, brain model, or voice speech has no usable credential. | Open Integrations and connect the named provider. |
| Brain connection valid | A custom brain connection is invalid or disabled. | Re-select the connection in Setup. |
| Balance OK | Wallet is empty (blocking) or low (warning). | Add credit in Billing. |
| Channel connected | Info for tests; required before deploy for voice or chat agents. | Add a web widget (or link a phone / SIP channel). |
| Test passed | Warning on deploy only: no successful console test yet. | Open the console and run a short test. |
Deploy is blocked when any blocking check fails. You can still deploy when only warnings remain (or use Deploy anyway for non-blocking cases). Console Connect anyway is hidden while a blocking check fails.
What FAILED means in Observe
Console and chat sessions can end as FAILED with a plain reason:
| Reason code | What you see |
|---|---|
pipeline_error | The agent could not start its voice or speech. Check the voice and provider settings. |
no_agent_reply | You spoke but the agent did not answer. Check the model and voice connection. |
no_conversation | The call ended before anyone spoke. |
billing_blocked | Your balance is too low to place calls. |
Real inbound phone calls where the caller never spoke stay successful; only dashboard console tests treat a silent session as failed.
Feature flag
This surface is gated by ff_dashboard_go_live_checklist (rollout, off by default). With the flag off, the checklist UI and deploy/console guards stay hidden. Honest FAILED status from the agent runtime still applies.