refer to one example call: https://dashboard.vapi.ai/calls/86ee6b09-a4d4-47e9-b0c1-00631300c85d The assistants keep just stopping to respond. This has been extremely embarrassing as I had just handed teh ai testing to my client, and it is not working. is VAPI broken?

Sorry to hear about the issue. As a first step, please double-check that your Assistant ID and Phone Number ID are correctly specified in your configuration—missing or incorrect values can cause the assistant to stop responding mid-call and end due to silence. Example checklist: - Ensure both IDs are set and match your intended assistant and phone number. - Verify your assistant has a valid Text-to-Speech provider and prompt configured. If the problem persists, check your call logs for any specific error codes or messages for further clues ([Vapi Support Bot guidance](https://discord.com/channels/1211482211119796234/1370485222214336564)). Source: - [Vapi Support Bot guidance](https://discord.com/channels/1211482211119796234/1370485222214336564)

I can handle this Mr Lucas accept request let talk about it

Hi Lucas van Staden, It seems like your assistant might be encountering a situation where it stops interacting during a call, leading to a silence timeout. This could happen due to a few potential reasons: 1. **Silence Timeout**: The call may automatically end if there's prolonged silence. You can check if the

silence-timed-out

reason is documented in the call logs. 2. **Assistant-Related Issues**: Common causes include the assistant recognizing a specific phrase that ends the call, or encountering an error such as

assistant-request-returned-no-assistant

or

assistant-said-end-call-phrase

. 3. **Call Duration**: If the call duration has reached the maximum limit, it might terminate as per the

exceeded-max-duration

reason. For a detailed list of call end reasons, you can refer to the [Call Ended Reasons documentation](https://docs.vapi.ai/calls/call-ended-reason). I recommend reviewing your call logs to identify the specific reason. Adjustments can be made based on that insight, such as modifying assistant prompts or settings.

The issue seems related to the 11labs transcriber service.

From the logs, the transcriber service failed to start in the beginning of the call. We recommend configuring some fallback transcribers in addition to replacing google gemini 2.0 flash with deepgram nova-2 or assemblyAI

how to configure fallback transcriber?

Thanks, I will setup backup transcribers 🙂 good opion to have.

cool, thanks!

Seems this is still a random issue. assistant setup with fallback.

"transcriber": {
        "model": "gpt-4o-transcribe",
        "language": "en",
        "provider": "openai",
        "fallbackPlan": {
            "transcribers": [
                {
                    "model": "scribe_v1",
                    "language": "en",
                    "provider": "11labs"
                }
            ]
        }
    },

test suite fail

The evaluation outcome cannot be determined because the call transcript is missing. Without the transcript, it's impossible to assess whether the AI successfully identified the patient by phone number and called them by their first name, created a minor account, made a new booking for the minor, and maintained polite and professional responses. Therefore, the test is marked as failed due to a lack of information.

all transcripts seem to be failing.

Glad you were able to get this resolved. If anything else comes up or you need further assistance, we’re here to help.