{"type":"video","version":"1.0","html":"<iframe src=\"https://www.loom.com/embed/2b796f0707be492ba951f33263fd3297\" frameborder=\"0\" width=\"1920\" height=\"1440\" webkitallowfullscreen mozallowfullscreen allowfullscreen></iframe>","height":1440,"width":1920,"provider_name":"Loom","provider_url":"https://www.loom.com","thumbnail_height":1440,"thumbnail_width":1920,"thumbnail_url":"https://cdn.loom.com/sessions/thumbnails/2b796f0707be492ba951f33263fd3297-00001.gif","duration":389.733333333334,"title":"Solution: Resolving 30034 errors when you thought you were registered for US A2P 10DLC","description":"In this video, we will explore the relationship between Messaging Service and your A2P 10DLC Campaign.\n\nWe have seen some of our builders struggle with their messages being blocked even after they have a verified campaign. The problem here is that the number might not be in the Sender Pool.\n\nAdditionally we have seen that incoming messages might stop working after being added to Messaging Service. That's because the Messaging Service has an integration control that overrides the number's configuration.\n\nA2P 10DLC Overview: https://twil.io/understanding-a2p-10dlc\n\nAddtionial Messaging Service Docs: https://www.twilio.com/docs/messaging/services"}