Text messaging, on the carrier you can actually register with.
SMS has complete send and receive support on two carriers, Telnyx and Twilio, and the choice is yours - because which one will register your business depends on where it is incorporated, not on anything we decide.
What works today
- Two carriers, both first class: Telnyx and Twilio. You connect one account under Integrations and the product leads with Telnyx, which is what it suggests when you have connected neither.
- Inbound SMS is received, resolved to a contact (by phone number), and can trigger an AI agent reply or wait for a teammate.
- Outbound SMS sends through the same conversation, with delivery status tracked back.
- STOP/START keyword handling: STOP opts a contact out immediately and blocks further sends; START reverses it.
- Signature verification on every inbound webhook, per carrier, so only real traffic from the carrier you connected is processed.
- A2P 10DLC registration is tracked whichever carrier you use: your brand and use cases, each number joined to one, and the carriers' answer recorded against it, so a number they would filter reads as unregistered rather than looking fine.
What it needs from you
An account with one of the two carriers, and the choice is yours because which one registers your business depends on where it is incorporated. Telnyx: a number in E.164 form and one API key. Twilio: the number, the Account SID, the auth token, and two webhook URLs Frontiva prints for you to paste into their console. Either way the account is yours, so carrier charges reach you at carrier rates rather than marked up through ours.
What it cannot do yet
We cannot provision a number for you, and we cannot file your A2P 10DLC registration on either carrier. Frontiva tracks that registration and records the carriers' answer against it, so you find out a number would be filtered before you find out by being filtered. Connecting both carriers at once is refused rather than used as a fallback, and the page says why.
What's next
Two things stay yours, and they are the same on either carrier. You register your own A2P 10DLC brand in your own carrier account: Frontiva records the outcome but does not submit it for you, and does not provision numbers. And you connect one carrier, not both: a second is refused rather than used as a fallback, because a 10DLC brand is registered per carrier, your customer would see a new sender number mid-thread, and a timeout is not proof that a message did not arrive.
Frequently asked questions
Which carrier should I choose?
Whichever will register your business, which depends on where it is incorporated rather than on anything about Frontiva. Both are equally supported here, and the product suggests Telnyx when you have connected neither. If one declines your brand, connect the other.
What do I need to connect a carrier?
A sending number in E.164 form and the carrier's credential. For Telnyx that is one API key, plus optionally the public key that verifies inbound webhooks and the messaging profile your registered campaign is attached to. For Twilio it is the Account SID and the auth token, and two webhook URLs that Frontiva prints for you to paste into their console.
Can I connect both carriers at once?
No, and the refusal is deliberate rather than a limitation. A 10DLC brand is registered per carrier so the unregistered one gets filtered anyway; a customer mid-conversation would see a different sender number and reply to the old one; and a send that times out is not proof of non-delivery, so trying the other carrier risks sending the same message twice.
Whose bill do the carrier charges land on?
Yours. The account is yours, so per-message and per-minute carrier rates and the 10DLC registration fees reach you at carrier rates rather than marked up through us. The number stays yours too, which also means you keep it if you leave.
Connect SMS (Telnyx or Twilio) when you're ready.
Start free - channel connections are configured per organization from Settings once you're signed up.