#1211486158232617032 Hello, Can you please help us to make the outbound calls? How to use the create call function to make the outbound calls? I have tried from the vapi api manual but in the place of the customer it is only supporting a 3 digit number. But the number should be 11 digit. Please check the screenshot attached. https://cdn.discordapp.com/attachments/1308876293617745990/1308876293944905850/image.png?ex=673f898a&is=673e380a&hm=fc0a0fd0a4abb0f10585d06df8c3455f75ec01ed3e8fb1efb38262b1e850cb66&

@Maruf WellnessExpress Hello! I'd be happy to assist you with making outbound calls using the VAPI. It seems there might be a misunderstanding or a misconfiguration if it's only accepting a 3-digit number for the customer. The customer number should indeed be in a full international format, typically including the country code, which would make it longer than 3 digits. To use the create call function, you need to ensure that you're passing the customer's phone number in the correct format. Here's a general outline of how you might use the function: 1. Ensure you have the correct authorization token and phone number ID. 2. Format the customer's phone number in international format (e.g., +14151231234). 3. Set up the headers with your authorization token. 4. Use the API endpoint for creating calls, typically a POST request. 5. Pass the necessary parameters, including the phone number ID and the correctly formatted customer number. If you're still encountering issues, could you please provide me with the exact error message or describe the issue in more detail? If there's a specific function you're referring to in the VAPI API manual, please let me know the name of the function, and I'll guide you through the process. Regarding the screenshot, I'm unable to view attachments, but if you describe the error or the part of the manual you're referring to, I can certainly help you resolve the issue. If the problem persists, you may need to contact support for more detailed assistance.

@Maruf WellnessExpress this will be fixed by end of this week, sorry for the inconvenience.