Description
Motivation
With the emergence of 10DLC carrier requirements, Twilio has implemented a new workflow for registering messaging services with a 10DLC campaign use-case. More info about that here.
This configuration can be done in the Twilio interface, which is fine for folks who are only using one or a few static messaging services, but for folks using the per-campaign messaging services with decentralized campaign creators, this isn't a viable solution.
Detailed Design
Essentially, this A2P campaign use case registration form in the Twilio console needs to be re-created both in the Organization Admin Settings, linked to the default messaging service, and also in the Campaign Admin in the Service Management section. I suspect it makes sense to populate the organization setting as the default for campaigns to make this easier for folks creating campaigns.
When the campaign is started and the messaging service is created on the server, the new Twilio API endpoints will need to be used to register the use case with the messaging service.
Project Plan Information
Sponsor Organization (will test alphas/betas)
WFP
(possibly?) AFL-CIO
Developer allocated
Planned timeline
ASAP – as mentioned, carriers may already be penalizing unregistered messaging services.
Files/File-sections touched
Organization Admin, Campaign Admin interfaces + org and campaign backend
Schema changes and migrations
We probably want to add a new JSON column with the configuration details in either the campaign or campaign_admin table. Perhaps there's a way we can figure out how to avoid making a db migration though.