Hello Vapi Support Team, I'm writing regarding two persistent issues with my Vapi.ai account that are preventing me from making outbound calls: 1. CSV Upload Validation Errors: I'm attempting to upload a CSV file for bulk outbound calling, but consistently receive validation errors stating "Phone number is required" for rows 2, 3, and 4 (as shown in the attached screenshot). I've verified that my CSV file contains: - A properly named "phone" column - Phone numbers in E.164 format - No empty rows or missing values 2. Single Outbound Call Activation Issue: When trying the "Call One Number" option with my assigned number (+1 224 307 1984), I receive the error: "Outbound Call Failed. 'phoneNumber' is activating. Contact support@vapi.ai if not active within 5 minutes." This issue has persisted for several hours. I've already tried: - Reformatting my CSV file multiple times with various tools - Creating a simple test CSV with only 2-3 properly formatted entries - Waiting for the phone number to activate (over 5 minutes as suggested) - Checking my account settings and ensuring I have sufficient credits I've attached screenshots showing both error messages. As I'm building an important workflow that integrates with Make.com, resolving these issues is time-sensitive for me. Could you please: 1. Provide specific guidance on the exact CSV format requirements 2. Check the status of my outbound phone number activation 3. Advise if there are any account verification steps I need to complete Thank you for your prompt assistance with this matter. https://cdn.discordapp.com/attachments/1360456330690953266/1360456330875375678/cebf79d0-02d8-48cd-822a-7d45ab6dda3e.jpg?ex=67fb2f31&is=67f9ddb1&hm=be7de840e002e34dd0e35749af7fdcb306ebce5f6000fde5f9dc404a9d13cb3f& https://cdn.discordapp.com/attachments/1360456330690953266/1360456331131093012/0618080b-cb6b-4f54-9530-beb80fec6662.jpg?ex=67fb2f31&is=67f9ddb1&hm=fc5a564c7f99d23e18346b1d281f9577f8a990389c992152aa1e2fa831943317&

Hi there! 👋 I understand you're facing some urgent issues with CSV uploads and outbound calling in Vapi. Let me help you troubleshoot these problems. I'm unable to check the specific status of your outbound phone number activation or advise on account-specific verification steps as I don't have access to your account details. However, I can definitely help with the CSV format requirements and provide some general troubleshooting steps for both issues. ## CSV Format Requirements Based on the information I found, here are the specific CSV format requirements for bulk outbound calling: 1. **Required Columns**: Your CSV file must have a "number" column (not "phone") for the phone numbers to call, and there's an optional "name" column. This might be why you're getting the validation errors - the column name should be "number" rather than "phone" [according to the CSV upload requirements](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1334251359519641692). 2. **Phone Number Format**: The numbers should be in E.164 format (e.g., +15558675309) [as mentioned in the documentation](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1333444985353404558). 3. **File Size Limit**: The maximum file size is 5MB [as shown in your screenshot and confirmed in the documentation](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1334251359519641692). ## Troubleshooting CSV Upload Validation Errors Try these steps to resolve your CSV validation issues: 1. **Rename Your Column**: Change your column name from "phone" to "number" in your CSV file. 2. **Check for Hidden Characters**: Sometimes CSV files can contain hidden characters or formatting issues. Try creating a new CSV file from scratch with just the "number" column and a few test entries. 3. **Verify Format**: Ensure there are no spaces, extra characters, or formatting issues in your phone numbers.

Message marked as helpful by @ideallionaire! 🎉

Hey Ideallionaire, could you share your Org ID here and your CSV file in DM with me? I could take a look at what might've gone wrong for you.