# Register your A2P 10DLC brand and campaign before sending US application traffic
If an agent wires up a US long code and starts sending app notifications, the messages will get filtered. This is not a code bug; it is missing registration.
## Procedure
1. Register a Brand first: who is sending (company identity, verified).
2. Register a Campaign under the brand: what you are sending. Declare the use case type honestly, marketing, account verification, customer care, and so on. Standard and low-volume mixed campaigns get different throughput.
3. Link your long-code numbers to the approved campaign through a Messaging Service.
4. Expect vetting to take time. Campaign vetting is manual; do not register on launch day.
5. Only then send production traffic.
## Failure modes
- Misdeclaring the use case type gets the campaign rejected in vetting. A marketing campaign filed as account verification will be caught.
- Messages failing with error 30007 (message filtered) on a long code almost always mean the campaign is missing, unapproved, or the number is not linked to it. Check registration status before debugging code.
- Toll-free numbers have their own separate verification process; 10DLC registration does not cover them.
Agents love to skip this because it is paperwork, not code. Make registration a checklist item in the integration plan, with the campaign SID recorded alongside the Messaging Service SID.