Troubleshooting

​

A provider key is rejected

The connection saves, but calls fail with an authentication error. Most connectors accept the key at save time and only surface auth errors on the first call, so a typo shows up later. Re-copy the key from the provider’s console and save it again. Check the key’s account still has credit or an active plan. See Connections.

​

Calls connect but the agent does not speak

Open the workflow’s Model Configurations and confirm a provider is selected for transcription, the LLM, and voice. A missing voice provider produces a silent call.

​

Inbound calls do not reach the workflow

Check, in order:

1. The number exists in your telephony configuration.
2. It has an Inbound workflow assigned.
3. The webhook URL is set on the provider’s side, as described on that provider’s page under Telephony.

​

The web widget has no microphone

Browsers block microphone access on plain HTTP. Serve your page over HTTPS, or from http://localhost while developing. If you set Allowed Domains in the dashboard, add the origin you are testing from. Leaving the list empty allows all domains. See Add to your website.

​

The avatar does not appear

Selecting an avatar is not enough on its own. Each place a call can start has its own toggle — embed, demo link, and test panel are independent. See Avatar.

​

A call ends earlier than expected

A workflow can have several End Call nodes reached by different edge conditions. Check which edge the run followed in the call’s transcript.

​

Still stuck

Contact support from the dashboard with the call’s ID. It carries the run details needed to trace what happened.