Vapi Support Bot Comments - VAPI

Vapi Support Bot

•Created by xenophobic-harlequin on 10/30/2025 in #support

hi wont accept payment for more credits. tried multiple credit cards, nothing is blocked by bank

Thanks for sharing the details. To help pinpoint the issue, could you confirm if you see your credit card listed as an active payment method on the Vapi billing page, or does it prompt you to re-enter your card details each time you try to purchase credits? Sources: - Vapi Changelog October 30, 2024 - Vapi Changelog November 30, 2024

5 replies

•Created by like-gold on 10/30/2025 in #support

Couldn't verify payment method

Thank you for sharing the details. To help us investigate further, could you please let us know the exact error message shown in the popup when your payment method cannot be verified? Source: - How to Report Issues Effectively

3 replies

•Created by genetic-orange on 10/30/2025 in #support

Voice Model Mismatch Between API Call and Logged Voice Provider

This behavior is likely due to Vapi's Voice Fallback Plan, which automatically switches to a backup provider (like ElevenLabs) if the primary voice (e.g., "Paige") is unavailable. To check or modify your fallback configuration, review your assistant setup for a section like this:

"voice": {
  "provider": "vapi",
  "voiceId": "Paige",
  "fallbackPlan": {
    "voices": [
      { "provider": "elevenlabs", "voiceId": "dOPyu4KyOAHZJaFmb3" }
    ]
  }
}

"voice": {
  "provider": "vapi",
  "voiceId": "Paige",
  "fallbackPlan": {
    "voices": [
      { "provider": "elevenlabs", "voiceId": "dOPyu4KyOAHZJaFmb3" }
    ]
  }
}

Action: Review your assistant's fallback plan to confirm if this is expected, and adjust as needed.
For more details, see the Voice Fallback Plan documentation. Source: - Voice Fallback Plan documentation

4 replies

•Created by absent-sapphire on 10/30/2025 in #support

How can I get the call ID injected into an apiRequest type tool call?

The most reliable way to get the call ID in your apiRequest tool is to extract it from the request payload sent by Vapi, rather than relying on header interpolation. In your server code, you can access it like this:

// Example: Express.js handler
app.post('/your-tool-endpoint', (req, res) => {
  const callId = req.body.message?.call?.id;
  // Use callId as needed
});

// Example: Express.js handler
app.post('/your-tool-endpoint', (req, res) => {
  const callId = req.body.message?.call?.id;
  // Use callId as needed
});

This ensures you always have the correct call ID, as documented in the Vapi Custom Tools guide.
Note: Header variable interpolation for {{call.id}} is not currently supported for apiRequest tools, so extracting from the payload is the recommended approach. Source: - Custom Tools Documentation

3 replies

•Created by graceful-blue on 10/30/2025 in #support

Urgent: transferCall and handoff Tools Failing to Locate Destination Assistant

To resolve the "assistantDestination 'Not Found'" error with the transferCall tool, ensure your tool's parameters include the required destination property with the correct assistant ID or phone number. Here's a sample configuration for your tool's parameters section:

"parameters": {
  "type": "object",
  "properties": {
    "destination": {
      "type": "string",
      "enum": ["YUB_English"], // Use the exact assistant ID or phone number
      "description": "The destination assistant ID or number to transfer the call to."
    }
  },
  "required": ["destination"]
}

"parameters": {
  "type": "object",
  "properties": {
    "destination": {
      "type": "string",
      "enum": ["YUB_English"], // Use the exact assistant ID or phone number
      "description": "The destination assistant ID or number to transfer the call to."
    }
  },
  "required": ["destination"]
}

Update your tool configuration with this snippet, replacing "YUB_English" with the correct assistant ID if needed. This should resolve the destination not found error and allow call transfers to your language-based assistants. Sources: - Vapi documentation: call forwarding - Vapi Discord Support Example

2 replies

•Created by xenial-black on 10/28/2025 in #support

Critical: Struggling with a transferCall error

You should add "serverMessages" and "phoneCallProviderBypassEnabled" as top-level fields inside your assistant's main JSON object. For example:

{
  "name": "Your Assistant Name",
  "serverMessages": ["phone-call-control"],
  "phoneCallProviderBypassEnabled": false,
  // ...other assistant properties...
}

{
  "name": "Your Assistant Name",
  "serverMessages": ["phone-call-control"],
  "phoneCallProviderBypassEnabled": false,
  // ...other assistant properties...
}

If your config is nested or managed differently, could you share a snippet of your assistant JSON structure? That will help me give you the exact placement. Source: - Debug call forwarding drops

16 replies

•Created by fair-rose on 10/28/2025 in #support

Critical: Struggling with a transferCall error

To resolve the call.in-progress.error-transfer-failed issue, explicitly set these fields in your assistant's JSON config:

"serverMessages": ["phone-call-control"],
"phoneCallProviderBypassEnabled": false

"serverMessages": ["phone-call-control"],
"phoneCallProviderBypassEnabled": false

Add or update these properties, then test your transfer again. This is the most common fix for your error according to the Vapi troubleshooting guide. Source: - Debug call forwarding drops

16 replies

•Created by robust-apricot on 10/30/2025 in #support

Error When Creating SIP Trunk Number

Thanks for sharing your configuration details. To help troubleshoot, could you confirm if your SIP provider requires a specific authentication method (such as SIP registration or IP-based authentication), or if they provided any additional error details or logs when the credential creation failed? Source: - SIP Trunking Documentation

9 replies

•Created by extended-salmon on 10/30/2025 in #support

DPA GDPR documents

For GDPR compliance documents and the DPA:
Vapi provides a Data Processing Agreement (DPA) at no charge, but it is only available to enterprise customers. To access GDPR documentation or request the DPA, please visit security.vapi.ai. If you require the DPA and are not yet on an enterprise plan, you will need to upgrade; for urgent issues, use the contact options on the security portal to reach their Data Protection Officer or support team for further assistance. Sources: - GDPR Compliance - Vapi Documentation (internal DPA/GDPR process)

2 replies

•Created by probable-pink on 10/30/2025 in #support

Long response times from nowhere?

Thank you for sharing the test IDs and setup details. To help narrow down the cause of the choppy audio and long response times, could you please check if there were any errors or warnings in the Vapi dashboard's Call Logs or API Logs for the "bad" test (ID: 019a3481-e927-7fff-b9e4-2a93174b7840)? If so, what did you find? Source: - Debugging voice agents

2 replies

•Created by quickest-silver on 10/30/2025 in #support

chat widget

To send structured chat data from the Vapi chat widget to your Make.com webhook, add a JavaScript event listener for the widget's message event and forward the data using fetch. Here’s a concrete example:

document.addEventListener('DOMContentLoaded', function() {
  const widget = document.querySelector('vapi-widget');
  widget.addEventListener('message', function(event) {
    fetch('https://your-make-webhook-url.com', {
      method: 'POST',
      headers: { 'Content-Type': 'application/json' },
      body: JSON.stringify(event.detail) // event.detail contains the chat message
    });
  });
});

document.addEventListener('DOMContentLoaded', function() {
  const widget = document.querySelector('vapi-widget');
  widget.addEventListener('message', function(event) {
    fetch('https://your-make-webhook-url.com', {
      method: 'POST',
      headers: { 'Content-Type': 'application/json' },
      body: JSON.stringify(event.detail) // event.detail contains the chat message
    });
  });
});

Replace https://your-make-webhook-url.com with your actual Make.com webhook URL. This will forward each chat message as structured JSON to your webhook for further processing. Source: - Vapi Web Widget Documentation

4 replies

•Created by provincial-silver on 10/30/2025 in #support

Additional credits are not getting updated

For urgent credit update issues, join the Vapi Discord community and post your situation in the #support channel with your organization ID and payment details. This channel is monitored for real-time assistance and may help escalate your case faster than email alone.
Tip: Clearly state "urgent billing/credit issue" in your message for priority attention.
More details: Vapi Support Options Source: - Vapi Support

7 replies

•Created by national-gold on 10/30/2025 in #support

Additional credits are not getting updated

Thank you for your patience. Since your credits are still pending and no confirmation email was received, please report this issue directly to Vapi support with your organization ID, payment details, and screenshots for urgent review.
You can do this by emailing support or using the issue reporting guidelines to ensure all necessary information is included.
This will help the team investigate and resolve your credit update as quickly as possible. Sources: - How to Report Issues Effectively - Discord conversation about Vapi free plan upgrade issues

7 replies

•Created by ratty-blush on 10/30/2025 in #support

Additional credits are not getting updated

Thank you for sharing the details and screenshots. To help us investigate further, could you please confirm if you received any email confirmation or error message regarding your $40.00 credit purchase on Oct 30th, 2025?

7 replies

•Created by fair-rose on 10/30/2025 in #support

DTMF tool executing but not navigating

To improve DTMF navigation, try adding pauses between digits in your DTMF sequence using the w character (for a 0.5s pause) as recommended in the IVR Navigation guide. For example, instead of sending 1234#, use:

1w2w3w4#

1w2w3w4#

Update your DTMF tool configuration in the Vapi dashboard to include these pauses—this often resolves IVR recognition issues.
For more details, see the IVR Navigation documentation. Source: - IVR Navigation

4 replies

•Created by fair-rose on 10/28/2025 in #support

Custom LLM Inquiry

You must configure Azure OpenAI credentials in the Vapi dashboard's "Model Providers" section—passing them directly in the API request is not supported and will cause the "Couldn't Find Credential for Model Provider" error. To resolve this, add your Azure OpenAI credentials in the dashboard, then reference the model in your assistant config like this:

{
  "model": {
    "provider": "azure-openai",
    "model": "gpt-4.1-mini-2025-04-14"
  }
}

{
  "model": {
    "provider": "azure-openai",
    "model": "gpt-4.1-mini-2025-04-14"
  }
}

No further API-side credential configuration is needed—just use the dashboard integration.
See the Azure OpenAI Integration Guide for details. Source: - Azure OpenAI Integration Guide

10 replies

•Created by ambitious-aqua on 10/28/2025 in #support

Critical: Struggling with a transferCall error

To help resolve your transferCall error:
Can you confirm if your assistant's JSON config currently has "serverMessages": ["phone-call-control"] and "phoneCallProviderBypassEnabled": false?
This is the most common cause for the call.in-progress.error-transfer-failed issue (see troubleshooting guide). Source: - Debug call forwarding drops

16 replies

•Created by rare-sapphire on 10/29/2025 in #support

VAPI Voice randomly sounds robotic or distorted during some calls

To start troubleshooting the robotic or distorted voice issue, check the call logs for your provided Call ID and timestamp in the Vapi Dashboard: 1. Go to Observe > Call Logs in your Vapi Dashboard. 2. Locate call ID 019a2bb6-a9eb-744a-96df-13fc7a6e0acb and review the logs around timestamp 00:20 for any errors or warnings. This will help you identify if there are any TTS errors, latency spikes, or audio format issues at the moment the distortion occurs. Source: - Debugging voice agents

4 replies

•Created by wise-white on 10/29/2025 in #support

variable in api tool

Try this:
Make sure your API tool defines the variable in the body schema, even for GET requests. For example:

{
  "type": "apiRequest",
  "name": "getHistory",
  "url": "https://rnogrvgymqipnmwgxjmp.supabase.co/rest/v1/n8n_chat_histories_maverick?select=*&ten_digit=eq.{{ten_digit}}&limit=20",
  "method": "GET",
  "body": {
    "type": "object",
    "properties": {
      "ten_digit": {
        "description": "The ten digit phone number",
        "type": "string"
      }
    },
    "required": ["ten_digit"]
  }
}

{
  "type": "apiRequest",
  "name": "getHistory",
  "url": "https://rnogrvgymqipnmwgxjmp.supabase.co/rest/v1/n8n_chat_histories_maverick?select=*&ten_digit=eq.{{ten_digit}}&limit=20",
  "method": "GET",
  "body": {
    "type": "object",
    "properties": {
      "ten_digit": {
        "description": "The ten digit phone number",
        "type": "string"
      }
    },
    "required": ["ten_digit"]
  }
}

This ensures {{ten_digit}} is recognized and replaced in your URL.
Check your tool config and redeploy if needed.
(Source: information found in the Default Tools documentation)

5 replies

•Created by complex-teal on 10/29/2025 in #support

google_calendar_check_availability_tool ignores timeZone and treats local timestamps as UTC (America

Yes, your approach is correct!
When the caller provides a time in America/Toronto, convert it to an ISO 8601 string with the explicit offset, like:

{
  "startDateTime": "2025-10-30T09:30:00-04:00",
  "endDateTime":   "2025-10-30T10:30:00-04:00",
  "timeZone": "America/Toronto"
}

{
  "startDateTime": "2025-10-30T09:30:00-04:00",
  "endDateTime":   "2025-10-30T10:30:00-04:00",
  "timeZone": "America/Toronto"
}

This matches the best practice in the documentation and should resolve the timezone issue you experienced. Source: - Google Calendar tool documentation

6 replies