VerifyRelay

Login codes that actually arrive.

One API for OTP, 2FA, and transactional SMS — with automatic cross-carrier failover, real delivery analytics, done-for-you 10DLC filing, and SMS → voice → WhatsApp escalation.

See pricingRead the docs
TCPA violations run $500–$1,500 per message — and 10DLC registration is mandatory for US application-to-person SMS. We handle both.
VerifyRelay product illustration
VRVerifyRelay — OTP delivery console
Sample data
Verification sends · Sample

Every login code, watched until it lands.

Each send is attempted in live route-score order. When a route degrades, the next provider takes over automatically — and the delivery receipt proves it arrived.

RecipientRoute takenDelivered inStatus
+1 ••• ••• 0142Twilio — primary route1.8sDelivered
+1 ••• ••• 7831Vonage degraded → Telnyx failover4.6sFailover
+44 ••• ••• 2210Sinch — primary route2.3sDelivered
+1 ••• ••• 5520SMS routes failed → voice call38sVoice escalation
4providers routed — Twilio, Vonage, Telnyx, Sinch
3escalation steps — SMS → voice → WhatsApp
1API call per send — failover included
Delivery SLA rail
SLA target — Scale
Measured from provider webhooks
99.5%
Automatic failover
Re-routing when a route degrades
Auto
Route scoring
Live receipts re-score every route
Live
10DLC filing
Brand + campaign filed for you
Included
Sample console. Sends, routes and timings are illustrative. Recipient numbers are masked — no real customer data is shown.
Sample — an illustrative OTP delivery consoleLogin codes that actually arrive.

Every SMS API gives you one route and calls delivery “best effort”

When a login code doesn't arrive, you lose a signup, a sale, or a customer. The incumbents don't solve this:

  • Orchestration layers (Knock, Courier, Novu): you bring your own provider — they explicitly disclaim responsibility for delivery.
  • Twilio Verify rides only Twilio's network. By definition it cannot fail over to a different provider.
  • AWS End User Messaging validated auto-failover — but only inside AWS.
  • 10DLC paperwork drowns small teams: brand and campaign registration is mandatory and fiddly.

A smart router above the carriers

VerifyRelay sits above Twilio, Vonage, Telnyx, and Sinch, watches real delivery receipts per route, and automatically re-routes each message across providers when a route degrades. Honest infrastructure statement: we are intelligent routing, analytics, and compliance tooling built on top of established SMS providers. We do not own carrier infrastructure and hold no carrier contracts.

Failover

Automatic cross-carrier failover

Every send is attempted in score order across providers. A send error or hard failure immediately re-routes — no code changes on your side.

Scoring

Real delivery analytics

Per-route delivery rates with Bayesian smoothing, fed by live Twilio/Vonage delivery webhooks. Your dashboard shows what actually arrived.

Escalation

SMS → voice → WhatsApp ladder

When SMS fails across all routes, we escalate: voice call with the code, then WhatsApp. A critical OTP gets through even when SMS is down.

Compliance

Done-for-you 10DLC

We file and maintain your US 10DLC brand and campaign registration. Delivery receipts are kept as audit evidence.

Security

Verified webhooks, validated input

Twilio callbacks are signature-verified; phone numbers are E.164-validated; API keys are compared in constant time.

Honesty

A router, not a network

We say “we route over Twilio and Vonage” the way others say “powered by AWS.” Never carrier ownership, never invented delivery percentages.

How it works

  1. Send one request

    POST /v1/verify/send with to, code, and your API key. E.164 validation happens before anything is billed.

  2. We pick the best route

    The router orders providers by live delivery score for the destination and sends over the winner.

  3. Failover happens automatically

    Errors and hard failures re-route to the next provider instantly; every attempt is returned in the response.

  4. Receipts feed the scores

    Twilio/Vonage status callbacks update per-route rates continuously, so tomorrow's sends use today's data.

Stop losing signups to silent SMS failures.

One API. Every carrier route that matters. A delivery SLA on Scale.

See pricing
Activation status (honest, October 2026): VerifyRelay’s routing, failover, metering and self-serve provisioning software is built and tested, and checkout provisions an API key via the claim page. Live SMS delivery is not available yet: it starts only after a messaging provider account (Twilio or Vonage) is configured on the deployment and US 10DLC registration is complete. Until then the API answers sends with an explicit provider_not_configured response — no message is sent and no delivery is claimed.