Verified numbers, steady delivery.
Verify toll-free numbers for business texting, once per enterprise, so the messages sent from them are trusted and keep arriving.
Known to carriers, not guessed at.
No business on file behind the number, so networks have less reason to trust what it sends.
The business, use case and opt-in are on file, which supports steady text delivery.
Illustrative messages
One request, four parts.
Collect everything a verification needs in a single flow, for each enterprise, instead of chasing it across emails and spreadsheets.
Acme Retail Ltd
The enterprise, under its own name, so the number is tied to a real business.
- Part
- Business
- Collected
- ✓ In one flow
- Note
- Reused for every number
Illustrative
Every business, its own number.
Each enterprise texts from a toll-free number registered in its own name, under your brand. You see every number and where it stands.
- Start a request when an enterprise signs up
- Follow every number to Verified
- Offer verification as a chargeable service
Illustrative businesses and numbers
From request to first text.
- 01Submit
Add the business, use case, samples and opt-in in one request.
- 02Review
The request is reviewed, and you follow its status in the portal.
- 03Verified
The number is registered for business texting.
- 04Send
Text from it with the same API as every other message.
One number, fully on file.
Everything behind a verified number sits in one record: the business, the use case, the samples and the proof of opt-in.
↺Reused ·✎Entered ·✓Automatic
- Business
- Acme Retail Ltd ↺ Reused from the enterprise
- Use case
- Order and delivery updates ✎ Declared in the request
- Sample message
- Your order #4821 has shipped. Reply STOP to opt out. ✎ Shown as customers see it
- Opt-in proof
- Checkout, step 3: “Text me order updates” ✓ Stored with the request
- Number
- +1 833 555 0142 ✓ Linked on approval
- Status
- ✓ Verified ✓ Tracked in the portal
Send from it like any number.
Once a number is verified, send with the same POST /v1/messages call and pick it as the sender. No separate endpoint for toll-free.
- Switch number per message or campaign
- Receipts and replies on the same webhooks
{
"to": "+1 415 555 0100",
"from": "+1 833 555 0142",
"text": "Your order has shipped"
}Illustrative request
Verification that pays for itself.
Sell registration and branded calling as paid services, and cut spoofing complaints.
Higher delivery and answer rates, and no more brand spoofing.
Questions, answered.
It is how a toll-free number is registered for business texting, so the messages sent from it are trusted and delivered steadily.
A verified number is known to carriers, which supports steady text delivery. An unverified number gives networks less reason to trust the traffic.
The business, the use case, sample messages and how customers opt in. Acepeak collects these in one flow for each enterprise.
Yes. Verification is handled per enterprise, so each business texts from a toll-free number registered in its own name.
They sit together under DLT & Caller ID. 10DLC covers local numbers, and toll-free verification covers toll-free numbers, so one team runs both.
No. Once a number is verified you send from it with the same POST /v1/messages request as any other message.
Get delivered. Stay trusted.
Talk to partnerships about verifying toll-free numbers for your enterprise customers.