opr8r
Live
Talk to us

§ 00 · Compliant A2P texting · infrastructure, not an app

Compliant texting for your product. In days, not a quarter.

Opr8r is the compliance operator between your software and the carrier network. Scroll to send a message down through it.

Talk to us See how it works

01 · Every send is checked

Your product sends. Opr8r checks it on the way down.

One API call. Before anything reaches the carrier, three rules run in order, and they run again at transmit.

  1. 01ConsentOpt-in on record for this number
  2. 02CapUnder the per-recipient limit this week
  3. 03Quiet hoursInside the recipient's local window
  4. 202DeliveredSent from your Telnyx account, every check logged

02 · STOP always wins

A revoked consent bounces the send, even mid-queue.

Opr8r refuses the send no matter what your code asked for. You get a structured reason back, never a silent failure.

  1. 409consent_opted_outCap and quiet hours are never evaluated
  2. →LedgerRefusal written with its source: stop_keyword
  3. →Webhookconsent.revoked, signed, sent to you

03 · You own it

Three layers. Two of them are yours.

Your product and your Telnyx account, with your numbers, brand and data, stay where they are. Opr8r is the layer in the middle. To fire us, slide it out by rotating one key.

  • Your numbers
  • Your brand
  • Your data
  • No export ticket
Talk to us See pricing
100%
of sends consent-checked at transmit
< 1s
STOP-to-block, platform-side
0
silent failures — every refusal is a structured, logged reason
§ 01
THE PROBLEM

10DLC is a maze. TCPA is a liability. STOP is a legal obligation. None of it is your product.

You built the app. Then the carrier ecosystem asked you to become a compliance team: brand and campaign registration, opt-in evidence, opt-out handling, quiet-hour rules that vary by timezone, per-recipient caps — and rejections that cite error codes no one documents.

REJECTION LOG
●MNO_REJECTEDcampaign
●TELNYX_FAILEDsend
●campaign rejected: 803registry
●campaign rejected: 806registry
●resubmit — reason not documented
§ 02
THE SOLUTION

Governed send, not raw send.

Opr8r sits between your product and the carrier and enforces compliance on every message — regardless of what your code asks for. That's the point.

01 · ENFORCEMENT

Every send checked

consent → cap → quiet hours, re-checked at transmit. A STOP that lands mid-queue wins. Refusals come back as structured 409s, never silent.

02 · REGISTRATION

10DLC, done for you

We've been through the review rounds and know the undocumented rules. Approved or refunded.

03 · EVIDENCE

The consent ledger

One legal-grade system of record for opt-in and STOP, global across every message class. This is the evidence you'll want if you're ever asked.

04 · OWNERSHIP

You own everything

It runs in your Telnyx account. Your numbers, your brand, your data. Fire us by rotating one key.

§ 03
HOW IT WORKS

Three moving parts.

You own two of them.

STEP 01 · YOURS

You bring the product

Your app, your content, your customers, your Telnyx account.

STEP 02 · OPR8R

Opr8r registers and governs

10DLC campaigns registered in your account; every send gated; STOP, consent and quiet hours enforced; every event logged.

STEP 03 · YOURS

You integrate in an afternoon

Call one API, subscribe to signed webhooks, drop in the opt-in widget.

Read the full flow →
§ 04
DEVELOPERS

Refusals are never silent.

One endpoint to send. A structured answer every time — queued, held, or blocked with a reason your code can act on.

POST /v1/send

{
  "to": "+15125550142",
  "body": "Thanks for visiting — mind leaving a quick review?",
  "message_class": "review_request",
  "idempotency_key": "rv_9f2c…"
}
202 queued
409 Conflict

{
  "code": "consent_opted_out",
  "send_id": "snd_01J8Z…",
  "opted_out_at": "2026-07-14T18:22:07Z",
  "source": "stop_keyword"
}
code — machine-actionable reason
opted_out_at — the ledger timestamp
source — how consent was revoked
X-Switchboard-Signature: t=1786…,v1=8b3f…

{
  "type": "consent.revoked",
  "occurred_at": "2026-07-14T18:22:07Z",
  "data": {
    "number": "+15125550100",
    "recipient": "+15125550142",
    "keyword": "STOP"
  }
}
Verify the signature before trusting the payload.
<script
  src="https://cdn.opr8r.ai/optin.js"
  data-key="pk_live_…"
  data-origin="https://app.yourproduct.com">
</script>

<div data-opr8r-optin="review_request"></div>
Opt-in evidence is written to the ledger at submit.
§ 05
THE RAILS

The rules are load-bearing. Your code can't bypass them.

Enforcement lives in the platform, not in your integration — so a bug in your code can't send to someone who opted out.

STOP / HELP / START

Handled at the platform per CTIA, ledger updated, event fired to you. Keyword messages never leak into your inbound stream.

QUIET HOURS

Default 21:00–08:00 in the number's local timezone; held sends auto-release when the window opens.

CAPS & THROTTLE

Per-recipient cap and per-number rate limit, enforced before a single message leaves.

CONSENT IS GLOBAL

One STOP silences text-backs, reviews, and reminders alike. Per (number, recipient).

CONTENT STAYS YOURS

Bodies are stored, never logged. PHI-minimal is your policy; the platform never weakens for anyone.

The platform refuses non-compliant sends regardless of what the caller asks. That refusal is the product.

§ 06
WHO IT'S FOR

Built for the companies that text on behalf of others.

Engagement & review platforms

Missed-call text-back, review requests, reputation sends — on behalf of hundreds of local businesses, each with its own brand.

Vertical SaaS

Reminders, ETAs, confirmations inside your app — texting as a feature, not a product you have to staff.

Agencies with their own tool

Many client brands, one compliant pipe. Transactional only — we don't do cold blasting.

If you're a single business looking for a texting app with an inbox, Opr8r isn't it — and we'll tell you that on the call.

OUTBOUND · SAMPLE
Thanks for visiting — mind leaving a quick review? Your appointment is tomorrow at 2:00 PM. Your technician is 10 minutes away.
consent ✓cap ✓quiet hours ✓
● delivered
§ 07
ALTERNATIVES

You could build this. Here's what it costs you.

BUILD IT YOURSELF
RAW TWILIO / TELNYX
TWILIO ISV
OPR8R
10DLC approval expertise
you learn it the hard way
you learn it the hard way
APIs, no judgment
done for you, approved-or-refunded
Consent ledger / evidence
you build & maintain
you build & maintain
you assemble primitives
built-in, legal-grade
STOP / quiet hours / caps
your code (and your bugs)
your code
your code
platform-enforced, un-bypassable
Ownership / lock-in
n/a
you own the account
you own the account
you own the account — fire us with one key
Time to first compliant send
a quarter+
weeks
weeks
an afternoon

You own the account. You own the numbers. You own the brand.

Everything is registered in your name, in your Telnyx account. Leaving is rotating one key. No export tickets, no hostage data, no migration project.

Most vendors make lock-in the moat. We made not locking you in the pitch.

$ opr8r keys rotate
● new key issued
● opr8r access revoked
account, numbers, brand — unchanged
§ 08
PRICING

Priced like infrastructure. Not per your customers' texts.

A one-time registration fee per campaign (approved or refunded) and a flat monthly platform fee — a base that includes your first active campaign, plus a fee per additional one. Carrier costs are billed by Telnyx to your account; we never rebill them.

REGISTRATION
one-time

Per 10DLC campaign. Approved or refunded.

PLATFORM
$400/mo

Includes your first active campaign. +$150/mo per additional one.

WORKED EXAMPLE
≈ $3,250/mo

A platform with 20 client campaigns ($400 + 19 × $150) — about 15% of one compliance hire.

See full pricing →

Add compliant texting to your product.

Tell us what you're building and who you send to. If we're a fit, you'll know on the first call — and if we're not, we'll say so.

Talk to us Read the docs
● delivered