Twilio A2P Messaging Setup

Modified on Mon, May 22, 2023 at 12:22 PM

Twilio A2P Messaging Setup


Log into your Twilio account:  Main account


Explore Products



Select “Trust Hub” from the search bar



Select “A2P Messaging” from the sidebar



Select “Register for A2P” to begin setup



Create a Starter Customer Profile -> Continue (we don’t need the larger package)



Profile name: MM of XXX (Enter your office title)



Contact information (owner)


  • Phone number is the main office phone # (no dashes)
  • Save and continue
  • Business Address (MM of XXX)



Save and continue


  • Review your Starter
  • Check the “I declare that the information provided is accurate...” box
  • Submit for Review



Register for US A2P 10DLC screen > Select Continue



Register Campaign Use Cases: Check “Create a new Messaging Service” box and select Continue



Create Messaging Service and Messaging Service Friendly Name:


  • “Molly Communications” for example) then select “Notify my Users” in the dropdown then Save and Continue


Add Senders:


  • Check the main office # and agree to add the number.
  • Select “Add Phone Numbers to the Messaging Service”



Add Senders: If your main number is listed below hit “Continue”



Register Campaign Use Cases: Review your setup


Then Select “Register Campaign Use Case”



Confirm campaign Use Case Registration and Select “Confirm”



The final approval may take 24 hours. There may be a message in the top left saying “Registration has been submitted – please refresh this page for updated status.”



After a refresh, you can select “Use an existing Messaging Service”



You should see your Messaging Service Friendly Name (“Molly Communications” in this example) with a Status under US A2P 10DLS Status.


It will say complete when the review is completed.


 

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article