I've made some calls on local host yesterday succesfully. I just tried to make a single outbound call on prod for the first time and it got blocked and I got this fraud alet email. Call ID: d904da05-aaed-4cc3-8795-0170645c9e87 An error occurred in this call: call.start.error-fraud-check-failed https://cdn.discordapp.com/attachments/1420105261674401894/1420105262013878372/CleanShot_2025-09-23_at_13.49.042x.png?ex=68d42f96&is=68d2de16&hm=24f18e33c8a8b42c240b8246fb48a4ce8942791595b381669f784abf5b32d265&

Action Required: Please contact the Vapi support team at support@vapi.ai with your Call ID (

d904da05-aaed-4cc3-8795-0170645c9e87

) and a brief description of the fraud alert you received. This is the recommended way to trigger a manual review and restore your account access. Tip: Include any screenshots or error messages to help support resolve your issue faster. Source: - [Vapi Issue Reporting Guide](https://docs.vapi.ai/issue-reporting)

Hi Kai, Outbound calls require proper caller identification and trusted calling standards to prevent fraud and spam. Here's what you need to do: 1. Implement proper caller identification for your production environment: - Use E.164 format for phone numbers (+ - Avoid rapid successive calls from new accounts - Establish proper caller reputation 2. Follow Trusted Calling standards: - Register your business identity - Use verified phone numbers - Implement proper STIR/SHAKEN attestation through Twilio 3. Best Practices to Avoid Spam Flags: - Use consistent phone numbers - Build caller reputation gradually - Properly identify your business in caller ID[1](https://docs.vapi.ai/outbound-campaigns/overview#avoiding-spam) For your specific error

call.start.error-fraud-check-failed

, this indicates that the call was blocked by Vapi's fraud detection system. This is common when moving from testing to production, especially for new accounts making their first production calls. To resolve this, you should: 1. Ensure you're using properly registered phone numbers 2. Follow the trusted calling guidelines 3. Let us know if this persists