### Answer Based on the available documentation, I don't have specific information about GoHighLevel (GHL) integration with Retell AI or how to share numbers between both platforms without Twilio as an intermediary. However, here are two general approaches Retell AI supports for custom telephony that might help: Option 1: Elastic SIP Trunking This is the recommended method if your telephony provider supports it. [(1) ]() You would set up a SIP trunk and configure your number to point to it, then import that number to Retell. Option 2: Dial to SIP URI If elastic SIP trunking isn't possible, you can dial calls to a specific SIP URI. Retell's SIP server URI is

sip:sip.retellai.com

. When using this method, Retell does not directly make or receive calls but relies on your system to dial the call to the respective SIP URI. Import Numbers to Retell You can import phone numbers from custom telephony using the Import Phone Number API, providing the termination URI for outbound calls. [(2) ]() For your specific GHL integration question, I'd recommend reaching out to support for guidance on whether GHL numbers can be configured to work with Retell via SIP trunking or if there's a specific integration path available. Check out these potentially useful sources: - [Custom Telephony Overview]() - [Import Phone Number]() - [Contact Sales]() Would you like me to provide a general answer about potential workarounds based on my knowledge?

​ To learn more, see the sources I considered: [[1] Custom Telephony Overview](https://docs.retellai.com/deploy/custom-telephony) [[2] Import Phone Number](https://docs.retellai.com/api-references/import-phone-number) ​

Feel free to tag @AI Evy with additional questions. I also appreciate feedback, it helps me improve.

@AI Evy why am i getting thi sresponse from the wbehook "Custom Webhook Action error: Custom Webhook Action error: {"error":"phone_required"}"

### Answer The error

{"error":"phone_required"}

indicates that your webhook endpoint is expecting a phone number parameter that isn't being provided in the request. I don't have specific documentation about this exact error message in the available sources. However, based on the webhook specifications, here are some things to check: For inbound webhooks, the payload includes

from_number

and

to_number

fields that are always present in the request. [(1) ]() For custom function webhooks, you need to ensure the parameters you're expecting are properly defined and passed. [(2) ]() Possible causes: 1. Your external webhook endpoint requires a

phone

or

phone_number

field that isn't being sent 2. The parameter name in your webhook configuration doesn't match what your endpoint expects 3. If using custom functions, the function parameters may not be correctly configured to pass the phone number To troubleshoot: - Check your webhook endpoint's expected request format - Verify the parameter names match between Retell's configuration and your endpoint - Review the Detail Logs in your Retell dashboard to see the exact payload being sent [(3) ]() If you're using a custom function webhook, make sure you've defined the phone parameter in your function configuration and that your prompt instructs the agent to pass it correctly. [(2) ]() Could you share more details about which type of webhook you're using (inbound webhook, custom function, or call event webhook) and what endpoint you're calling? That would help narrow down the issue.

​ To learn more, see the sources I considered: [[1] Inbound webhook](https://docs.retellai.com/features/inbound-call-webhook) [[2] Calling Webhooks In The Middle of A Call](https://discord.com/channels/1186424376300679209/1376986877927886979) [[3] Inbound webhook returns retell_llm_dynamic_variables but agent doesn't receive them](https://community.retellai.com/t/inbound-webhook-returns-retell-llm-dynamic-variables-but-agent-doesnt-receive-them/733) ​

Feel free to tag @AI Evy with additional questions. I also appreciate feedback, it helps me improve.

### Answer --- I don't have information about specific system updates around February 5th, 2026 in the available sources. However, there was a similar case where a user experienced webhook issues that turned out to be related to cached or incorrect webhook configuration rather than a system update. [(1) ]() In that case, the old webhook URL was still configured in the settings even though the user thought they had updated it. Troubleshooting steps: 1. Verify your webhook configuration - Check that your webhook URL is correctly saved in Settings → Webhooks 2. Check agent version - Ensure your phone number or agent is using the correct agent version that references the updated webhook URL 3. Review the Detail Logs in your Retell dashboard to see the exact payload being sent to your webhook 4. Verify request structure - For inbound webhooks, ensure your response follows the correct format with fields nested under `call_inbound`: [(2) ]()

json
{
  "call_inbound": {
    "dynamic_variables": {
      "first_name": "Pranam",
      "last_name": "Lipinski"
    }
  }
}

The

{"error":"phone_required"}

error is coming from your external endpoint (GHL) , not from Retell itself. This suggests your endpoint's expected parameters may have changed or the payload format it's receiving doesn't match what it expects. For direct assistance investigating your specific account and call logs, please reach out through: - [Contact Sales]() - [GitHub]()

​ To learn more, see the sources I considered: [[1] Global webhook sending incorrect Host header - 401 errors](https://community.retellai.com/t/global-webhook-sending-incorrect-host-header-401-errors/679) [[2] Inbound webhook returns retell_llm_dynamic_variables but agent doesn't receive them](https://community.retellai.com/t/inbound-webhook-returns-retell-llm-dynamic-variables-but-agent-doesnt-receive-them/733) ​

Feel free to tag @AI Evy with additional questions. I also appreciate feedback, it helps me improve.

@AI Evy Heres the weird part it was working perfectly until about 2 days ago

### Answer That's frustrating when something stops working unexpectedly. Based on similar cases in the community, here are a few things that could explain sudden webhook failures: Possible causes: 1. Webhook URL caching issue - There have been documented cases where webhook URLs appeared correctly saved in the dashboard but the system was still sending to an old URL. [(1) ]() [(2) ]() In one case, the support team confirmed "the old one is in the settings, not the new one." [(1) ]() 2. Agent version mismatch - If you recently published or updated your agent, ensure the phone number is bound to the correct agent version that has your webhook configuration. 3. Webhook not firing for specific agents - There was a case where one agent's webhook worked while another's didn't, despite identical configuration. Deleting and recreating the agent resolved it. [(3) ]() Recommended steps: 1. Double-check your agent's webhook URL is correctly saved and matches what you expect [(1) ]() 2. Verify your phone number is using the correct agent version 3. Check the Detail Logs in Retell to see the exact payload being sent 4. If the issue persists, try re-publishing your agent after confirming the webhook settings Since the

{\"error\":\"phone_required\"}

error is coming from your external endpoint (GHL) , not Retell, something may have changed on the GHL side or in how the payload is being formatted/sent. For direct investigation of your specific

account and call logs, please reach out through: - [Contact Sales]() - [GitHub]()

​ To learn more, see the sources I considered: [[1] Global webhook URL not being used - caching issue?](https://community.retellai.com/t/global-webhook-url-not-being-used-caching-issue/772) [[2] Global webhook sending incorrect Host header - 401 errors](https://community.retellai.com/t/global-webhook-sending-incorrect-host-header-401-errors/679) [[3] webhook](https://discord.com/channels/1186424376300679209/1453081094424498422) ​

Feel free to tag @AI Evy with additional questions. I also appreciate feedback, it helps me improve.