Q: What should you do if you see this warning in your Twilio console?
A: To address this warning you must follow the four steps below:
Step 1: Verify your turboDial account is correctly configured
If your turboDial account operates in your primary Twilio console then no support from the turboDial team is needed. If, however, your turboDial account operates in a sub-account in Twilio for which you do not have access, then you will need to move your turboDial Account to operate in your Primary Twilio Account for which you have full access. You can do that in your turboDial Management Account so that you have the control needed to perform operations in your Twilio account.
Step 2: Register for A2P 10DLC
Follow Twilio’s instructions here to register for A2P 10DLC.
Step 3: Specify “Defer to Sender’s Webhook” in Twilio
Also, as part of your Messaging Service setup you must allow your phone numbers used with turboDial to have a different configuration for incoming messages while they are part of the same messaging service.
Refer to Twilio’s guidance (See Step 2) on how to accomplish that. The following image shows your Messaging Service should be configured for “Defer to sender’s webhook”, on the “Integration” page
Step 4: Install your Messaging Service SID in turboDial
Once you have created your Messaging Service in Twilio and have added the intended phone numbers to the Sender Pool for that Messaging Service, you last step is to login to your turboDial Management Account and install your Messaging Service SID into turboDial. That form is found here:
Install your Messaging Service SID in turboDial
(For searching: A2P 10DLC)