Get your texting numbers approved
U.S. carriers require every business that sends automated texts to register first. This is a one-time setup per business. Follow the steps below — the platform tracks your progress and files most of it for you through Twilio.
1 · Toll-free vs. local 10DLC — which do you need?
Both are legitimate. For a local trades shop we recommend running both, in parallel: toll-free gets you sending within days while the local numbers finish registering.
Toll-free (1-8xx)
- You already own +1 844 524 6373.
- One verification form — no EIN strictly required.
- Approves in ~1–3 weeks; high throughput.
- Trade-off: 1-844 feels less "local neighbor."
Local 10DLC (301 / 240)
- A local area-code number per client shop.
- Requires Brand + Campaign registration (TCR).
- Feels like a real neighbor texting back.
- Best long-term for missed-call recovery.
2 · What you'll need (gather once)
Have these ready for the business you're registering. For your own account that's Ravric Solutions; later, each client shop supplies its own.
| Item | Example / note |
|---|---|
| Legal business name | Exactly as on tax records — "Ravric Solutions LLC" |
| Business type + EIN | LLC/Corp → EIN required (Standard brand). No EIN → Sole Proprietor path (lower volume). |
| Business address | Physical registered address |
| Website URL | Live site describing the service; ideally links a privacy policy |
| Contact person | Name, email, mobile — must be reachable for the verification code |
| Sample messages | The exact texts customers will get (2–3 examples — provided below) |
| Opt-in description | How customers consent (for missed-call text-back: "customer called the business") |
3 · Toll-free verification do this first
4 · A2P 10DLC — register your Brand
The Brand is who is sending. One brand per business. Two paths:
Needs an EIN. Higher throughput, all use cases, better deliverability. Recommended if Ravric (or the client) is a registered LLC/Corp.
No EIN needed. Lower daily caps (~1 msg/sec, limited recipients/day), some carriers restrict it. Fine to start a solo shop, upgrade later.
5 · A2P 10DLC — register your Campaign
The Campaign is what you send. For missed-call recovery use the Customer Care / Conversational use case.
6 · Consent language & sample messages most important
Carriers reject vague opt-in. For missed-call text-back the consent basis is: the customer initiated contact by calling the business. Copy these into your registration.
Opt-in description (paste into Brand/Campaign forms)
Consumers initiate contact by calling the business's published phone number. When a call is missed, the business replies by SMS to the number the consumer called from, to help schedule service or answer their question. Consumers can reply STOP at any time to opt out. No numbers are purchased, rented, or shared; messages are only sent to people who first contacted the business.
Sample messages (attach 2–3)
1) Hi, this is {Business Name} — sorry we missed your call! Were you looking to book a service visit or ask a question? Reply here and we'll help. Reply STOP to opt out.
2) Thanks! We have openings Thu 8-10am or Fri 1-3pm. Which works? Reply with a time and we'll lock it in.
3) You're booked for Thu 8-10am. We'll text a reminder the day before. Reply HELP for help, STOP to opt out.
Costs & timelines (set by Twilio/carriers — approximate)
| Item | Cost | Time |
|---|---|---|
| Toll-free verification | Free to file | ~1–3 weeks |
| A2P Brand vetting | ~$4 one-time | Minutes–1 day |
| Campaign registration | ~$15 one-time + ~$1.50–$10/mo | Hours–few days |
| Local number | ~$1.15/mo each | Instant |
| Per message | ~$0.008 + carrier fee | — |
These are the only real out-of-pocket costs to get compliant. The platform pre-fills and submits the paperwork through Twilio so you don't touch the console.