<?xml version="1.0" encoding="UTF-8"?><oembed><type>video</type><version>1.0</version><html>&lt;iframe src=&quot;https://www.loom.com/embed/27930efa8c5f43ca86337ca84478fa18&quot; frameborder=&quot;0&quot; width=&quot;1920&quot; height=&quot;1440&quot; webkitallowfullscreen mozallowfullscreen allowfullscreen&gt;&lt;/iframe&gt;</html><height>1440</height><width>1920</width><provider_name>Loom</provider_name><provider_url>https://www.loom.com</provider_url><thumbnail_height>1440</thumbnail_height><thumbnail_width>1920</thumbnail_width><thumbnail_url>https://cdn.loom.com/sessions/thumbnails/27930efa8c5f43ca86337ca84478fa18-00001.gif</thumbnail_url><duration>268.099114481</duration><title>Quick Tip: Resolve A2P 10DLC Messaging Service Issues</title><description>In this Quick Tip, we will explore the relationship between Messaging Service and your A2P 10DLC Campaign.

We 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.

Additionally we have seen that incoming messages might stop working after being added to Messaging Service. That&apos;s because the Messaging Service has an integration control that overrides the number&apos;s configuration.

A2P 10DLC Overview: https://twil.io/understanding-a2p-10dlc

Additional Messaging Service Docs: https://www.twilio.com/docs/messaging/services</description></oembed>