# Phone, outreach, dialer, and compliance > Set up phone outreach, complete A2P 10DLC messaging registration, attach SMS numbers, run campaigns, and monitor calls. Canonical: https://help.spacebrain.ai/chat-and-voice/phone-outreach-and-compliance/ ## What is A2P 10DLC? **A2P 10DLC** means application-to-person messaging over a US 10-digit long-code phone number. It is the carrier registration process a business completes before sending application-generated SMS from eligible local US numbers. In Spacebrain, this workflow is called **Messaging Compliance**. Spacebrain blocks SMS sending until the registration is approved and an eligible sending number is attached. The standing shown at the top of **Chat & Voice → Messaging Compliance** is the source of truth for whether the workspace can send SMS. ## Phone numbers Open **Chat & Voice → Phone Numbers** to review numbers available to the workspace. Acquisition, assignment, inbound routing, outbound identity, geographic capability, and supported messaging depend on provider, plan, country, and registration status. Before assigning a number, document its purpose, public identity, agent or destination, owner, business hours, fallback, recording behavior, and expected monthly usage. Test inbound and outbound behavior from an external device. ## How to complete A2P 10DLC registration Open **Chat & Voice → Messaging Compliance**, then complete the three numbered sections in order: 1. Under **Your business**, enter the business type, legal and customer-facing names, EIN or tax ID when required, live website, industry, contact details, and physical address. Select **Save & review**, fix every blocking finding, and then select **Register business**. The legal name and EIN should match the official record exactly, the website must be publicly reachable, and the address cannot be a PO Box. 2. Wait for the business status to become **Verified**. A registered business is locked in this screen; contact support if an amendment is required. 3. Under **What you send & consent**, choose the actual use case and opt-in method. Describe the campaign, provide two representative messages, explain how consent is collected, and supply the opt-in page, confirmation text, privacy policy, terms, HELP reply, and message flow requested by the form. Declare embedded links or age-gated content when applicable. 4. Select **Save & review** and resolve every blocking finding. Review the current carrier fees shown in the product before submitting. 5. After the business is verified, select **Submit for approval**. Submission is not approval; the campaign remains unable to send while it is in review. 6. When the campaign status is **Approved**, use **Numbers that may send** to attach each workspace phone number that will send SMS. Wait for the number to show **Registered** and for the standing to say **SMS sending is active** before testing. Maintain consistent business names, domains, privacy information, and messaging examples. Only send the approved use case and honor opt-outs across manual sends, campaigns, agents, and automations. ## A2P 10DLC FAQ ### Does submitting the registration mean it is approved? No. **In review** means the business or campaign is still being reviewed. The campaign must show **Approved**, the sending number must show **Registered**, and the page must say **SMS sending is active** before you treat setup as complete. ### Can I send SMS while A2P 10DLC is pending? No. Spacebrain reports **SMS sending is blocked** until the required business verification, campaign approval, and number attachment are complete. Read the reason in the current-standing alert rather than inferring readiness from an earlier step. ### What should I prepare before starting? Prepare the exact legal business identity, tax ID if required, a live website, physical address, a specific messaging use case, documented opt-in method and page, two realistic sample messages, opt-in confirmation language, privacy and terms URLs, and HELP and opt-out handling. The details must describe the messaging you will actually send. ### Does approval prove that every recipient consented? No. Registration establishes carrier approval for the declared program; it does not create recipient consent or guarantee delivery. Keep consent and suppression records, stay within the approved use case, and honor opt-outs everywhere a message can be sent. ## Outreach contacts and campaigns Use **Chat & Voice → Contacts** for the audience used by voice outreach and **Campaigns** for coordinated outbound activity. Before importing or selecting contacts: * Confirm source, consent, timezone, number validity, suppression, and owner. * Remove internal tests from production segments and production contacts from tests. * Define campaign purpose, schedule, caller identity, agent, retry policy, and stop conditions. * Keep audience size small for the first run. Monitor campaign status, call outcomes, usage, and complaints. Pause before editing a live campaign if the product does not explicitly state how in-progress work is handled. ## Power Dialer **Chat & Voice → Power Dialer** supports an operator working through an approved call list. Confirm list order, contact context, caller identity, notes, disposition behavior, and next-step ownership. Do not let speed override wrong-party checks, consent, or local calling rules. ## Calendar, SMS, and actions Calendar and SMS capabilities use connected actions. Verify the provider, availability window, timezone, required inputs, conflict handling, and confirmation behavior. An agent should not claim an appointment or message succeeded until the downstream result confirms it. ## Recordings and analytics Use **Recordings** for authorized quality review and **Analytics** for trends. Restrict downloads and sharing. Review a representative sample of successes, failures, escalations, opt-outs, and action attempts—not only high-scoring calls. Report date ranges and provider states can lag live activity. Number availability or a successful send does not establish legal permission. Confirm calling, recording, messaging, identity, consent, quiet-hour, and retention requirements for every region and use case. See [Chat & Voice agents](/chat-and-voice/agents), [Inbox channels](/inbox/channels), and [communications troubleshooting](/troubleshooting/communications-and-automations) for the systems that depend on a healthy phone and messaging setup.