I am trying to launch a campaign since yesterday but even if I set it as Start now, it just gets everything scheduled with an unknown start date. I (AFAIK) dont have any KYC issues, and dont have anything else running everything is either completed or canceled. I really need to use this. I even purchased more credits hoping that would solve it but still no. Email support also hasn't helped. Campaign ID: b21f6980-2db1-421e-9653-0f8050588976 https://cdn.discordapp.com/attachments/1420831531387064350/1420831532301684797/image.png?ex=68d6d3fb&is=68d5827b&hm=52e9975e84c73de85d7d9c605ab3cd8f9fa103e333835bf2f34bfe3addeaa86c&

Thank you for sharing the details. To help diagnose why your outbound campaign is stuck with an unknown start date, could you confirm if you are using an imported phone number from a provider like Twilio, Vonage, or Telnyx (not a Vapi free number) for this campaign? This is a common requirement for outbound campaigns to start properly. Source: - [Outbound campaigns quickstart](https://docs.vapi.ai/outbound-campaigns/quickstart)

yes, I am using a number I bought from Twilio

Suggestion: Please double-check your SIP trunk and webhook configurations in both Twilio and Vapi, as recent changes or misconfigurations are a common cause for campaigns getting stuck in a scheduled state with no start date. Even if you haven't changed anything recently, try re-saving your webhook/SIP settings and then relaunch the campaign. If the issue persists, consider sharing any recent changes or screenshots of your SIP/webhook setup with support for deeper investigation. This step is based on known issues where outbound campaigns remain queued due to SIP or webhook misconfigurations ([source](https://discord.com/channels/1211482211119796234/1372358449761091584)). Source: - [Vapi outbound call not triggering (Discord)](https://discord.com/channels/1211482211119796234/1372358449761091584)

What do I have to check?

Check your Twilio phone number's webhook configuration: Go to your Twilio Console → Phone Numbers → select your campaign number → set the "A call comes in" webhook to your server's

/incoming

endpoint, for example:

https://your-server.com/incoming

Make sure the HTTP method is set to

POST

and save the changes. This ensures Twilio can properly route calls to your campaign and is a common fix for campaigns stuck in a scheduled state ([documentation](https://docs.vapi.ai/calls/call-queue-management#configure-phone-number-webhook)). Source: - [Call queue management with Twilio](https://docs.vapi.ai/calls/call-queue-management#configure-phone-number-webhook)

@Vapi Support Bot This is what I have https://cdn.discordapp.com/attachments/1420831531387064350/1420853427814010910/image.png?ex=68d6e85f&is=68d596df&hm=9e4c9f686833ff08543d734306dfa8d512f3eba6fe70061d4b205c11e6d06057&

Thank you for sharing your Twilio configuration details. Based on the documentation, outbound campaigns typically require the "A call comes in" webhook to point to your own server's

/incoming

endpoint (e.g.,

https://your-server.com/incoming

), not directly to a Vapi endpoint like

https://api.vapi.ai/twilio/inbound_call

([see docs](https://docs.vapi.ai/calls/call-queue-management#configure-phone-number-webhook)). Can you confirm if you have a custom server set up to handle incoming webhooks from Twilio, or are you relying solely on Vapi's endpoints? Source: - [Call queue management with Twilio](https://docs.vapi.ai/calls/call-queue-management#configure-phone-number-webhook)

I don't have a server endpoint. Just Vapi one. Always has been like that.

Action Required: To resolve your outbound campaign issue, update your Twilio number's "A call comes in" webhook to point to your own server's

/incoming

endpoint (not the Vapi endpoint). For example:

https://your-server.com/incoming

This change is necessary for outbound campaigns to start properly ([see documentation](https://docs.vapi.ai/calls/call-queue-management#configure-phone-number-webhook)). If you don't have a server, you'll need to set one up to handle these webhooks. Source: - [Call queue management with Twilio](https://docs.vapi.ai/calls/call-queue-management#configure-phone-number-webhook)

@Vapi Support Bot But why was it working before and suddenly it stopped working? Not having a server was never an issue...

I understand the confusion. Current Vapi documentation requires your Twilio number's "A call comes in" webhook to point to your own server's

/incoming

endpoint for outbound campaigns to work:

plaintext
https://your-server.com/incoming

If it worked previously without a server, this is no longer supported—**setting up your own server endpoint is now required** for campaigns to start ([see documentation](https://docs.vapi.ai/calls/call-queue-management#configure-phone-number-webhook)). Unfortunately, the documentation does not explain why this changed. Source: - [Call queue management with Twilio](https://docs.vapi.ai/calls/call-queue-management#configure-phone-number-webhook)

... I dont think this is correct. Can I talk to a human?

Hey! To help track down this issue, could you share: \- The call ID \- When exactly this happened (the timestamp) \- What response you expected to get \- What response you actually got instead This would really help us figure out what went wrong!