# Setting up webhooks to receive incoming calls, messages and status updates for calls (for Twilio users) > Learn how to configure Twilio webhooks for GHL Customer Care so inbound calls, SMS messages, and call status updates are sent to the correct GHL Customer Care endpoints. - Source: https://docs.ghlcustomercare.com/docs/phone-system/general/setting-up-webhooks-to-receive-incoming-calls-messages-and-status-updates-for-ca - Section: Phone System / General - Reading time: 8 min - Images: 8, each explained below - Modified on Fri, 4 Sep at 1:58 PM --- Twilio Webhook Configuration Setting Up Webhooks for Incoming Calls, Messages & Call Status Updates Configure Twilio to send inbound calls, incoming SMS/MMS messages, and call status updates to the correct GHL Customer Care endpoints. Overview Locations connected to their own Twilio account need the correct webhooks so Twilio can pass inbound calls, incoming messages, and call status updates to GHL Customer Care. Voice webhooks are configured on the individual Twilio phone number. Messaging can be configured directly on the number or through a linked Twilio Messaging Service, depending on the number's current configuration. This guide provides the exact webhook endpoints, explains which messaging path to use, and includes troubleshooting steps for calls, messages, or status updates that do not appear correctly in GHL Customer Care. Important These instructions apply to locations using **their own Twilio account**. They do not apply to phone numbers managed through GHL Customer Care's native LC Phone system. If another application intentionally controls the phone number's existing webhooks, replacing those values can change how inbound traffic is routed. Confirm that the number should route calls and messages into GHL Customer Care before replacing a custom webhook. Table of Contents [What is Twilio Webhook Configuration?](#what-is-webhook-config) [Key Benefits of Correct Webhook Configuration](#key-benefits) [Before You Begin](#before-you-begin) [Webhook Endpoints at a Glance](#webhook-endpoints) [Direct Number vs. Messaging Service](#messaging-paths) [How to Set Up Twilio Webhooks for GHL Customer Care](#setup) [Troubleshooting Twilio Webhooks](#troubleshooting) [Frequently Asked Questions](#faq) [Related Articles](#related) # **What is Twilio Webhook Configuration?** Twilio webhooks tell Twilio where to send events when someone calls or messages one of your Twilio phone numbers. Correct webhook configuration allows GHL Customer Care to receive those events and display or process them inside the connected sub-account. Voice configuration controls **incoming calls** and **call status updates**. Messaging configuration controls **incoming SMS/MMS messages**. These settings are especially important after connecting an existing Twilio account, moving a number, changing a Messaging Service, or troubleshooting calls or texts that no longer appear correctly in GHL Customer Care. ## **Key Benefits of Correct Webhook Configuration** Webhooks create the connection between Twilio and GHL Customer Care for inbound communication. Correct configuration helps prevent missing calls, missing messages, and incomplete call-status information. - **Inbound Call Routing:** Send incoming Twilio calls to GHL Customer Care's voice endpoint. - **Incoming Message Delivery:** Route inbound SMS/MMS activity into GHL Customer Care. - **Call Status Synchronization:** Send call-status events back to GHL Customer Care using the dedicated call-status webhook. - **Messaging Service Support:** Configure inbound messaging correctly when multiple numbers use a Twilio Messaging Service. - **Faster Troubleshooting:** Separate voice, direct-number messaging, and Messaging Service configuration so the correct failure point can be identified quickly. ## **Before You Begin** Confirming the correct Twilio account, phone number, and messaging path before editing webhooks prevents configuration changes from being applied to the wrong client or number. - Confirm the affected GHL Customer Care location uses a **connected Twilio account**, not LC Phone. - Log in to the Twilio account or subaccount that owns the phone number. - Identify the exact phone number experiencing the issue. - Confirm whether the phone number is attached to a **Messaging Service**. - Do not replace webhook values belonging to another intentional integration unless the number should now route into GHL Customer Care. **A2P 10DLC is separate from webhook configuration.** Twilio may display A2P registration notices on the same screens. Completing webhook setup does not replace applicable A2P registration requirements. ## **Webhook Endpoints at a Glance** Each event type must point to the appropriate GHL Customer Care endpoint. Copy these values exactly and use **HTTP POST** where specified. | Event | Twilio Field | GHL Customer Care Endpoint | Method | | --- | --- | --- | --- | | **Incoming Call** | A call comes in | `https://services.leadconnectorhq.com/phone-system/voice-call/inbound` | **HTTP POST** | | **Call Status Update** | Call status changes | `https://services.leadconnectorhq.com/appengine/twilio/incoming_call_status` | **HTTP POST** | | **Incoming SMS/MMS** | A message comes in / Messaging Service Request URL | `https://services.leadconnectorhq.com/appengine/twilio/incoming_message` | **HTTP POST** | | **Messaging Service Fallback** | Fallback URL | `https://services.leadconnectorhq.com/appengine/twilio/incoming_message` | **HTTP POST** | **Do not mix the endpoints.** The incoming-call URL, call-status URL, and incoming-message URL perform different functions. ## **Direct Number vs. Messaging Service** Incoming-message configuration depends on whether the Twilio number is using its own messaging webhook or belongs to a Messaging Service. Check the number's Active Configuration before changing messaging settings. | Configuration | Where to Configure Incoming Messages | | --- | --- | | **No Messaging Service linked** | Configure the phone number's Messaging section directly. | | **Messaging Service linked** | Open the linked Messaging Service and configure its Integration settings. | **Voice configuration is still managed on the individual phone number.** A linked Messaging Service changes the messaging setup path, not the Voice Configuration steps below. ## **How to Set Up Twilio Webhooks for GHL Customer Care** Configure voice first, then configure messaging using the path that applies to the phone number. Save each configuration before testing so Twilio uses the updated webhook values. ### **Step 1: Open the Twilio Phone Number** 1. Log in to the Twilio account or subaccount that owns the affected number. 2. Go to **Phone Numbers → Manage → Active Numbers**. 3. Select the phone number you want to configure. [Open Twilio Active Numbers →](https://console.twilio.com/us1/develop/phone-numbers/manage/incoming) ![Step 1: Open the Twilio Phone Number (image 1 of 8)](https://s3.amazonaws.com/cdn.freshdesk.com/data/helpdesk/attachments/production/155080149836/original/bQdShEuBKREN9VYnYFrWSTpj806csZkc0g.jpeg) **Step 1: Open the Twilio Phone Number (image 1 of 8)** This screenshot appears in the "Step 1: Open the Twilio Phone Number" section of "Setting up webhooks to receive incoming calls, messages and status updates for calls (for Twilio users)". For context, this section explains: Twilio Webhook Configuration Setting Up Webhooks for Incoming Calls, Messages & Call Status Updates Configure Twilio to send inbound calls, incoming SMS/MMS messages, and call status updates to the correct GHL Customer Care endpoints. Overview Locations connected to their own Twilio account need the…. - Controls: their own Twilio account, incoming calls, call status updates, incoming SMS/MMS messages, Before You Begin, connected Twilio account, Messaging Service, Webhook Endpoints at a Glance, HTTP POST, Incoming Call, Call Status Update, Incoming SMS/MMS Full procedure: 1. Inbound Call Routing: Send incoming Twilio calls to GHL Customer Care's voice endpoint. 2. Incoming Message Delivery: Route inbound SMS/MMS activity into GHL Customer Care. 3. Call Status Synchronization: Send call-status events back to GHL Customer Care using the dedicated call-status webhook. 4. Messaging Service Support: Configure inbound messaging correctly when multiple numbers use a Twilio Messaging Service. 5. Faster Troubleshooting: Separate voice, direct-number messaging, and Messaging Service configuration so the correct failure point can be identified quickly. ### **Step 2: Open the Number's Configure Tab** After selecting the phone number, open **Configure**. This page contains the routing, Voice Configuration, and Messaging configuration used for the number. ![Step 2: Open the Number's Configure Tab (image 2 of 8)](https://s3.amazonaws.com/cdn.freshdesk.com/data/helpdesk/attachments/production/155080149838/original/bP7eC5GCwGBE8YwcoKHoEfOIHZooJ-x3UQ.jpeg) **Step 2: Open the Number's Configure Tab (image 2 of 8)** This screenshot appears in the "Step 2: Open the Number's Configure Tab" section of "Setting up webhooks to receive incoming calls, messages and status updates for calls (for Twilio users)". For context, this section explains: Twilio Webhook Configuration Setting Up Webhooks for Incoming Calls, Messages & Call Status Updates Configure Twilio to send inbound calls, incoming SMS/MMS messages, and call status updates to the correct GHL Customer Care endpoints. Overview Locations connected to their own Twilio account need the…. - Controls: their own Twilio account, incoming calls, call status updates, incoming SMS/MMS messages, Before You Begin, connected Twilio account, Messaging Service, Webhook Endpoints at a Glance, HTTP POST, Incoming Call, Call Status Update, Incoming SMS/MMS Full procedure: 1. Inbound Call Routing: Send incoming Twilio calls to GHL Customer Care's voice endpoint. 2. Incoming Message Delivery: Route inbound SMS/MMS activity into GHL Customer Care. 3. Call Status Synchronization: Send call-status events back to GHL Customer Care using the dedicated call-status webhook. 4. Messaging Service Support: Configure inbound messaging correctly when multiple numbers use a Twilio Messaging Service. 5. Faster Troubleshooting: Separate voice, direct-number messaging, and Messaging Service configuration so the correct failure point can be identified quickly. ### **Step 3: Confirm US1 Voice Routing** Under **Voice Configuration**, confirm the Routing area shows **United States (US1) Region call routing is: Active**. If US1 is not active, use Twilio's routing controls to update the configuration before continuing. ![Step 3: Confirm US1 Voice Routing (image 3 of 8)](https://s3.amazonaws.com/cdn.freshdesk.com/data/helpdesk/attachments/production/155080149845/original/8Z-XLh_cbAv7x5v9uAmn4VZ-GCFy-Rr9Mg.jpeg) **Step 3: Confirm US1 Voice Routing (image 3 of 8)** This screenshot appears in the "Step 3: Confirm US1 Voice Routing" section of "Setting up webhooks to receive incoming calls, messages and status updates for calls (for Twilio users)". For context, this section explains: Twilio Webhook Configuration Setting Up Webhooks for Incoming Calls, Messages & Call Status Updates Configure Twilio to send inbound calls, incoming SMS/MMS messages, and call status updates to the correct GHL Customer Care endpoints. Overview Locations connected to their own Twilio account need the…. - Controls: their own Twilio account, incoming calls, call status updates, incoming SMS/MMS messages, Before You Begin, connected Twilio account, Messaging Service, Webhook Endpoints at a Glance, HTTP POST, Incoming Call, Call Status Update, Incoming SMS/MMS Full procedure: 1. Inbound Call Routing: Send incoming Twilio calls to GHL Customer Care's voice endpoint. 2. Incoming Message Delivery: Route inbound SMS/MMS activity into GHL Customer Care. 3. Call Status Synchronization: Send call-status events back to GHL Customer Care using the dedicated call-status webhook. 4. Messaging Service Support: Configure inbound messaging correctly when multiple numbers use a Twilio Messaging Service. 5. Faster Troubleshooting: Separate voice, direct-number messaging, and Messaging Service configuration so the correct failure point can be identified quickly. ### **Step 4: Configure Incoming Calls and Call Status Updates** Voice Configuration needs two GHL Customer Care endpoints: one for new inbound calls and one for subsequent call-status changes.
Configure withWebhook, TwiML Bin, Function, Studio Flow, Proxy Service
A call comes inWebhook
Incoming Call URLhttps://services.leadconnectorhq.com/phone-system/voice-call/inbound
HTTPHTTP POST
Primary handler failsNo change required for this setup.
Call status changes URLhttps://services.leadconnectorhq.com/appengine/twilio/incoming_call_status
Call Status HTTPHTTP POST
Caller Name LookupOptional. Leave at your preferred setting.
Save the phone-number configuration after entering the values. ![Step 4: Configure Incoming Calls and Call Status Updates (image 4 of 8)](https://s3.amazonaws.com/cdn.freshdesk.com/data/helpdesk/attachments/production/155080149853/original/IlcEg0CgJmsfxVU2KtAK92q_EzbK0G8aPw.jpeg) **Step 4: Configure Incoming Calls and Call Status Updates (image 4 of 8)** This screenshot appears in the "Step 4: Configure Incoming Calls and Call Status Updates" section of "Setting up webhooks to receive incoming calls, messages and status updates for calls (for Twilio users)". For context, this section explains: Twilio Webhook Configuration Setting Up Webhooks for Incoming Calls, Messages & Call Status Updates Configure Twilio to send inbound calls, incoming SMS/MMS messages, and call status updates to the correct GHL Customer Care endpoints. Overview Locations connected to their own Twilio account need the…. - Controls: their own Twilio account, incoming calls, call status updates, incoming SMS/MMS messages, Before You Begin, connected Twilio account, Messaging Service, Webhook Endpoints at a Glance, HTTP POST, Incoming Call, Call Status Update, Incoming SMS/MMS Full procedure: 1. Inbound Call Routing: Send incoming Twilio calls to GHL Customer Care's voice endpoint. 2. Incoming Message Delivery: Route inbound SMS/MMS activity into GHL Customer Care. 3. Call Status Synchronization: Send call-status events back to GHL Customer Care using the dedicated call-status webhook. 4. Messaging Service Support: Configure inbound messaging correctly when multiple numbers use a Twilio Messaging Service. 5. Faster Troubleshooting: Separate voice, direct-number messaging, and Messaging Service configuration so the correct failure point can be identified quickly. ### **Step 5: Confirm US1 Messaging Routing** In the phone number's Messaging configuration, confirm **United States (US1) Region message routing is: Active**. ![Step 5: Confirm US1 Messaging Routing (image 5 of 8)](https://s3.amazonaws.com/cdn.freshdesk.com/data/helpdesk/attachments/production/155080149860/original/8YeyN1X4W-58yewvde58E7oKhTaS6C2EQQ.jpeg) **Step 5: Confirm US1 Messaging Routing (image 5 of 8)** This screenshot appears in the "Step 5: Confirm US1 Messaging Routing" section of "Setting up webhooks to receive incoming calls, messages and status updates for calls (for Twilio users)". For context, this section explains: Twilio Webhook Configuration Setting Up Webhooks for Incoming Calls, Messages & Call Status Updates Configure Twilio to send inbound calls, incoming SMS/MMS messages, and call status updates to the correct GHL Customer Care endpoints. Overview Locations connected to their own Twilio account need the…. - Controls: their own Twilio account, incoming calls, call status updates, incoming SMS/MMS messages, Before You Begin, connected Twilio account, Messaging Service, Webhook Endpoints at a Glance, HTTP POST, Incoming Call, Call Status Update, Incoming SMS/MMS Full procedure: 1. Inbound Call Routing: Send incoming Twilio calls to GHL Customer Care's voice endpoint. 2. Incoming Message Delivery: Route inbound SMS/MMS activity into GHL Customer Care. 3. Call Status Synchronization: Send call-status events back to GHL Customer Care using the dedicated call-status webhook. 4. Messaging Service Support: Configure inbound messaging correctly when multiple numbers use a Twilio Messaging Service. 5. Faster Troubleshooting: Separate voice, direct-number messaging, and Messaging Service configuration so the correct failure point can be identified quickly. ### **Step 6: Configure Incoming Messages** Use the path that matches the phone number's current Twilio configuration. Path A — Number Is Not Connected to a Messaging Service 1. Remain on the individual phone number's **Configure** page. 2. Under Messaging, set **Configure with** to **Webhook, TwiML Bin, Function, Studio Flow, Proxy Service**. 3. Set **A message comes in** to **Webhook**. 4. Enter: `https://services.leadconnectorhq.com/appengine/twilio/incoming_message` 5. Set the method to **HTTP POST**. 6. Save the configuration. Path B — Number Is Connected to a Messaging Service If **Active Configuration** displays a linked Messaging Service, configure inbound messaging from that service instead of relying only on the number-level messaging field. ![Step 6: Configure Incoming Messages (image 6 of 8)](https://s3.amazonaws.com/cdn.freshdesk.com/data/helpdesk/attachments/production/155080149861/original/lCBD9SDZoHAkHMxhiniHtFMts3-l7JPeCA.png) **Step 6: Configure Incoming Messages (image 6 of 8)** This screenshot appears in the "Step 6: Configure Incoming Messages" section of "Setting up webhooks to receive incoming calls, messages and status updates for calls (for Twilio users)". For context, this section explains: Twilio Webhook Configuration Setting Up Webhooks for Incoming Calls, Messages & Call Status Updates Configure Twilio to send inbound calls, incoming SMS/MMS messages, and call status updates to the correct GHL Customer Care endpoints. Overview Locations connected to their own Twilio account need the…. - Controls: their own Twilio account, incoming calls, call status updates, incoming SMS/MMS messages, Before You Begin, connected Twilio account, Messaging Service, Webhook Endpoints at a Glance, HTTP POST, Incoming Call, Call Status Update, Incoming SMS/MMS Full procedure: 1. Inbound Call Routing: Send incoming Twilio calls to GHL Customer Care's voice endpoint. 2. Incoming Message Delivery: Route inbound SMS/MMS activity into GHL Customer Care. 3. Call Status Synchronization: Send call-status events back to GHL Customer Care using the dedicated call-status webhook. 4. Messaging Service Support: Configure inbound messaging correctly when multiple numbers use a Twilio Messaging Service. 5. Faster Troubleshooting: Separate voice, direct-number messaging, and Messaging Service configuration so the correct failure point can be identified quickly. 1. From **Active Numbers**, click the linked Messaging Service. 2. Open **Integration**. 3. Under **Incoming Messages**, select **Send a webhook**. 4. Enter the following **Request URL**: `https://services.leadconnectorhq.com/appengine/twilio/incoming_message` 5. Set the Request URL method to **HTTP POST**. 6. Enter the same URL as the **Fallback URL**: `https://services.leadconnectorhq.com/appengine/twilio/incoming_message` 7. Set the Fallback URL method to **HTTP POST**. 8. Click **Save**. ![Step 6: Configure Incoming Messages (image 7 of 8)](https://s3.amazonaws.com/cdn.freshdesk.com/data/helpdesk/attachments/production/155080149864/original/AkMZJ6tAZXJO-GjSEuA8nrmbdNSyaWPjpA.png) **Step 6: Configure Incoming Messages (image 7 of 8)** This screenshot appears in the "Step 6: Configure Incoming Messages" section of "Setting up webhooks to receive incoming calls, messages and status updates for calls (for Twilio users)". For context, this section explains: Twilio Webhook Configuration Setting Up Webhooks for Incoming Calls, Messages & Call Status Updates Configure Twilio to send inbound calls, incoming SMS/MMS messages, and call status updates to the correct GHL Customer Care endpoints. Overview Locations connected to their own Twilio account need the…. - Controls: their own Twilio account, incoming calls, call status updates, incoming SMS/MMS messages, Before You Begin, connected Twilio account, Messaging Service, Webhook Endpoints at a Glance, HTTP POST, Incoming Call, Call Status Update, Incoming SMS/MMS Full procedure: 1. Inbound Call Routing: Send incoming Twilio calls to GHL Customer Care's voice endpoint. 2. Incoming Message Delivery: Route inbound SMS/MMS activity into GHL Customer Care. 3. Call Status Synchronization: Send call-status events back to GHL Customer Care using the dedicated call-status webhook. 4. Messaging Service Support: Configure inbound messaging correctly when multiple numbers use a Twilio Messaging Service. 5. Faster Troubleshooting: Separate voice, direct-number messaging, and Messaging Service configuration so the correct failure point can be identified quickly. The call-status callback configured earlier belongs to the phone number's **Voice Configuration**. Do not copy the call-status URL into the Messaging Service's Delivery Status Callback field. ![Step 6: Configure Incoming Messages (image 8 of 8)](https://s3.amazonaws.com/cdn.freshdesk.com/data/helpdesk/attachments/production/155080149881/original/_BzNdLZvI5inEWeJVlZfa9apefXYYnKn7A.png) **Step 6: Configure Incoming Messages (image 8 of 8)** This screenshot appears in the "Step 6: Configure Incoming Messages" section of "Setting up webhooks to receive incoming calls, messages and status updates for calls (for Twilio users)". For context, this section explains: Twilio Webhook Configuration Setting Up Webhooks for Incoming Calls, Messages & Call Status Updates Configure Twilio to send inbound calls, incoming SMS/MMS messages, and call status updates to the correct GHL Customer Care endpoints. Overview Locations connected to their own Twilio account need the…. - Controls: their own Twilio account, incoming calls, call status updates, incoming SMS/MMS messages, Before You Begin, connected Twilio account, Messaging Service, Webhook Endpoints at a Glance, HTTP POST, Incoming Call, Call Status Update, Incoming SMS/MMS Full procedure: 1. Inbound Call Routing: Send incoming Twilio calls to GHL Customer Care's voice endpoint. 2. Incoming Message Delivery: Route inbound SMS/MMS activity into GHL Customer Care. 3. Call Status Synchronization: Send call-status events back to GHL Customer Care using the dedicated call-status webhook. 4. Messaging Service Support: Configure inbound messaging correctly when multiple numbers use a Twilio Messaging Service. 5. Faster Troubleshooting: Separate voice, direct-number messaging, and Messaging Service configuration so the correct failure point can be identified quickly. ### **Step 7: Test the Configuration** After saving the Twilio configuration, test each communication path separately so you can identify exactly which webhook is working or failing. 1. Call the Twilio number from an external phone and confirm the incoming call reaches GHL Customer Care. 2. Send an SMS to the Twilio number and confirm the message appears in **Conversations**. 3. Review the associated call activity in GHL Customer Care to confirm call-status information is updating. ## **Troubleshooting Twilio Webhooks** Troubleshoot the event that is failing instead of changing every webhook at once. Voice, call status, and messaging use separate configuration fields, so one can fail while the others continue working. Incoming Calls Do Not Reach GHL Customer Care Confirm the correct Twilio number is selected, US1 voice routing is active, **A call comes in** is set to Webhook, the incoming-call URL is exact, the method is HTTP POST, and the configuration has been saved. Calls Work but Call Status Does Not Update Correctly Re-check the **Call status changes** URL and confirm it uses **HTTP POST**. The call-status endpoint is different from the inbound-call endpoint. Incoming SMS Does Not Appear in Conversations First determine whether the number is attached to a Messaging Service. If it is, check the service's **Integration** settings. If it is not, check the number-level messaging webhook. Also confirm the number supports SMS. The Webhook Looks Correct but Messages Still Do Not Appear Review Twilio's Messaging Logs for the affected message. Confirm the message reached Twilio, note its status and Message SID, and use those details when escalating the issue. The Wrong Twilio Subaccount Was Configured If your Twilio account contains multiple subaccounts, confirm the affected phone number belongs to the same Twilio subaccount connected to the GHL Customer Care location before changing webhooks. Webhook Values Keep Changing Review whether another connected application or integration is managing the Twilio number. Repeatedly replacing webhooks without identifying the integration that owns them can cause routing conflicts. ## **Frequently Asked Questions** Q: Do I need to configure these webhooks if I use LC Phone? No. These steps are for locations connected to their own Twilio account. LC Phone webhook configuration is managed by the platform. Q: I have several Twilio subaccounts. How do I know which one to configure? Confirm the Twilio subaccount connected to the affected GHL Customer Care location and make sure that subaccount owns the phone number you are troubleshooting. Configuring the same phone number or webhook in another Twilio account will not correct the connected location. Q: Do I need to configure every Twilio phone number? Voice Configuration is stored on the individual Twilio phone number, so verify each affected number. Numbers that share a Messaging Service can use that service's shared inbound-message integration settings. Q: Why can calls work even when incoming SMS is missing? Voice and messaging use separate webhook settings. A correct Voice Configuration does not confirm that the number-level messaging webhook or linked Messaging Service is configured correctly. Q: Should the Messaging Service Request URL and Fallback URL be the same? Yes. For the GHL Customer Care Twilio setup documented here, both use `https://services.leadconnectorhq.com/appengine/twilio/incoming_message` with HTTP POST. Q: Does the call-status webhook belong in the Messaging Service Delivery Status Callback field? No. The `incoming_call_status` endpoint belongs in the phone number's Voice Configuration under **Call status changes**. It should not be reused as a Messaging Service delivery-status callback. Q: Does configuring these webhooks complete A2P 10DLC registration? No. Webhook configuration and A2P 10DLC registration are separate. A US local number used for application-to-person messaging may still require an approved A2P registration and proper Messaging Service association. Q: What should I collect before escalating a webhook issue? Collect the affected GHL Customer Care location, Twilio subaccount, phone number, exact timestamp of the failed event, screenshots of the current webhook configuration, and the relevant Twilio Call SID or Message SID when available. ### **Related Articles**  [Troubleshooting: Inbound SMS Showing as Calls or Not Appearing at All](https://docs.ghlcustomercare.com/docs/phone-system/messaging/troubleshooting-inbound-sms-showing-as-calls-or-not-appearing-at-all)   [How to Check Logs for a Specific Text Message in Twilio](https://docs.ghlcustomercare.com/docs/phone-system/messaging/how-to-use-twilio-messaging-logs-to-troubleshoot-sms-non-isv)   [US Phone Number Registrations — A2P 10DLC](https://docs.ghlcustomercare.com/docs/phone-system/a2p-registration/what-is-a2p-10-dlc-brand-and-campaign-registration)   [Overview of Phone Number Configuration Options](https://docs.ghlcustomercare.com/docs/phone-system/phone-numbers/overview-of-phone-number-configuration-options)   [What is the Native Phone System?](https://docs.ghlcustomercare.com/docs/phone-system/lc-phone-system/what-is-the-ghl-customer-care-s-native-phone-system-lc-phone)   [How Do I Migrate My Agency and Sub-Account Over to LC Phone?](https://docs.ghlcustomercare.com/docs/phone-system/lc-phone-system/how-do-i-migrate-my-agency-and-sub-account-over-to-lc-phone) --- Documentation for GHL Customer Care. Support: support@ghlcustomercare.com