How to Report Issues Effectively
To help us assist you as quickly and accurately as possible, it’s essential to provide specific and actionable details when reporting issues. Vague messages like “X is not working” slow down the resolution process.
This guide will help you structure your reports to get the best support experience.
We handle three main categories of issues. Choose the appropriate category and follow the specific guidelines for faster resolution:
Unexpected assistant behavior, voice issues, transcription errors, or call failures.
Interface problems, configuration errors, or dashboard functionality issues.
Login problems, account upgrades, billing issues, or verification needs.
If you’re experiencing issues with assistant behavior, voice quality, transcription accuracy, or call connectivity, follow these guidelines:
When reporting assistant-related issues, always include:
- Call ID from the test call
- Timestamp where the issue occurred in the recording
- Detailed description of what happened
- Expected behavior vs. actual behavior
- Screen recording (for web-based calls showing the issue)
If the call never connected or failed completely, simply share the Call ID and we’ll investigate the connection logs.
Assistant issues often require multiple rounds of testing and refinement. After each change or suggestion from our team:
- Test the updated configuration
- Share the new Call ID
- Describe the results and any improvements
- Continue until the issue is resolved
This iterative feedback helps us identify and fix issues efficiently.
For problems with the Vapi dashboard interface, configuration screens, or any visual/functional issues in the web application:
- Screen recording or screenshots showing the issue
- Browser information (Chrome, Firefox, Safari + version)
- Operating system (Windows, macOS, Linux)
- Steps to reproduce the issue
- Console errors (if any - press F12 to open developer tools)
- URL where the issue occurs
For issues related to your account, billing, login, or organization settings, provide the following information:
- Email address used for your account login
- Organization ID (for organization-level inquiries)
- Detailed description of the issue
- Screenshots of error messages or unexpected behavior
Use this checklist to ensure you’re providing the right information for your issue type:
- Be specific: Instead of “it’s not working,” describe exactly what happened
- Include context: Mention what you were trying to accomplish
- Test consistently: Use the same configuration when reproducing issues
- Document changes: Keep track of what modifications you’ve made
- Record everything: Screen recordings are invaluable for UI and workflow issues
- Check console: Browser console errors provide crucial debugging information
Following these guidelines helps us resolve your issues faster and more accurately. Our support team can provide targeted assistance when we have the right information upfront.