Toll-Free Verification
Toll-free numbers (8xx area codes) go through a separate verification process from standard 10DLC local number registration. The two processes are independent — you can have both a local campaign (10DLC) and a verified toll-free number on the same account.
Surge can purchase numbers in 833, 844, 855, 866, 877, and 888 via API. The original 800 prefix is mostly exhausted — Surge can port in an existing 1-800 number on request, but new purchases use one of the other prefixes.
Toll-free vs 10DLC
| Toll-free verification | 10DLC (standard) | |
|---|---|---|
| Number type | Toll-free (8xx area codes) | Local 10-digit numbers |
| Registration | Per-number verification | Brand + campaign, then attach numbers |
| Use case | High-volume transactional, customer care | Any messaging use case |
| API support | Purchase via API; verification dashboard-only | Full API support |
| Review time | No published SLA | 24–48 hours typical |
How to verify a toll-free number
Purchase a toll-free number
POST /accounts/{account_id}/phone_numbers with type: "toll_free". This part has full API support.
Open the verification form in the dashboard
Navigate to Phone Numbers and find the number you just purchased.
Click Verify
Opens the toll-free verification form.
Complete the form
Provide your business information, opt-in description, and sample messages.
Submit and wait for carrier review
The number is marked as verified once the carrier approves. Until then, throughput is restricted.
Changes-needed on toll-free
If the carrier requests changes, Surge sends you a notification with details. Use the verification form in the dashboard to update and resubmit. The issues reviewers flag for toll-free are similar to 10DLC — opt-in flow clarity, business identity, and sample message quality. See Avoiding Rejection for the full breakdown.
API support
Today: purchasing toll-free numbers via API is supported. Coming: full toll-free verification via API. Until it ships, use the dashboard for the verification step.