I’m currently testing my outbound campaign in GHL, and it’s showing “outbound calling limit reached – import number from Twilio.” The number I’m using is already from Twilio. Could you please assist urgently? @Vapi @Vapi Support Bot https://cdn.discordapp.com/attachments/1476715263356436710/1476715263863820388/image.png?ex=69a221c2&is=69a0d042&hm=a242d17eb1daa53ef53f8d3ad01a4799e0b2ae4f9ed57cb1db858e7149039f2e&

To resolve the "outbound calling limit reached" error, ensure your Twilio number is properly imported into Vapi: 1. Go to the Phone Numbers section in your Vapi dashboard and click Import. 2. Enter your Twilio phone number, Account SID, and Auth Token, then click Import from Twilio. This step is required even if your number is from Twilio—numbers must be imported via the Vapi dashboard to be eligible for outbound campaigns. For more details, see the [Vapi Outbound Campaigns Quickstart](https://docs.vapi.ai/outbound-campaigns/quickstart). Source: - [Outbound campaigns quickstart](https://docs.vapi.ai/outbound-campaigns/quickstart)

Hey Alee! I've fixed this exact error for 2 clients recently, it's a Twilio-to-GHL linking issue, not an actual limit. Quick fix. Are you on agency or sub account level? DM me 🚀 @Alee Hadeed

We’re a GHL agency and currently facing two issues: @KENNY When triggering outbound calls via API from GHL workflows, we’re receiving a “limit reached” error. Could you please clarify which limit is being hit (API, calling, rate limit, etc.) and how we can resolve or increase it? We’re also having trouble connecting GHL with Vapi for calendar syncing. The calendars are not syncing properly in Vapi. Could you please guide us on the correct setup or check if there’s any issue from your end?

Hey please share call id/org id so we can investigate more