To resell SMS, you meter every segment per customer, add your own margin on top of your provider's cost, show carrier fees as a separate line, and keep compliance clearly assigned. The texting itself is the easy part. The billing and the responsibility are where resellers get hurt.

This guide walks through those four decisions in order. We make Ready, so we'll use its model for examples, and we'll flag where the same advice applies to any provider.

Decide what you're actually selling

You can sell texting as a line item, bundle it into a plan, or hide it inside a feature such as appointment reminders. Pick before you price, because it changes how you meter.

A line item is the most honest. Customers see segments used and what each cost. A bundle is simpler to sell, but you carry the risk when a customer sends far more than you assumed. Both work, and a bundle needs usage caps you can enforce.

Whichever you pick, write down what happens at the edges. What does a customer pay when a text fails? Does a reply count against a bundle? Settle these before launch, because a billing rule you invent during a dispute rarely survives it.

Meter in segments, per customer

Bill on segments, not messages. A single SMS segment is 160 GSM-7 characters, longer texts split into 153-character segments, and an emoji drops the limit to 70. A 140-character text with one emoji is 3 segments, not 1.

Ready gives each customer a sub-account, so usage is already separated by tenant. Replies are billed like sent texts, so your meter has to count inbound segments too. A customer who gets 600 replies has used 600 more segments, even if they sent nothing.

Show the customer a preview of segment count while they write a message. It cuts support tickets, since people stop being surprised that a long text with an emoji costs more.

Set your markup

Your margin sits between what Ready charges you and what you charge the customer. Ready's rate is $0.0075 a segment plus a $0.0045 carrier fee, which we pass through at cost. Accounts opened before November 12, 2026 keep their signup prices, shown under Billing.

Ready lets you set a per-customer price, so one customer can pay more than another. Our white label SMS API guide explains the partner fee rules, including that raising an existing customer's price needs their consent. Plan a notice period before any increase.

Two pricing mistakes show up often:

  • One flat markup for everyone. A self-serve customer and a hand-held one don't cost you the same to support.
  • Forgetting the fixed costs. Registration and numbers are monthly charges, not per-text ones.

Itemize the fees

Show each customer separate lines for texts, the carrier fee, numbers and registration. Itemizing is easier to defend when a customer disputes a bill, and it keeps your margin from looking like a surprise.

Bill lineWhat it coversReady's cost to you
Text segmentsSent and received$0.0075 a segment
Carrier feePass-through at cost$0.0045 a segment
RegistrationBrand and first campaign$25 a month
Phone numberEach number$2 a month
ScreeningOptional Scrub lists and Number validationPer segment, only when switched on

Add a markup on whichever lines you choose, and leave the carrier fee visible. See the pricing page for every price, and 10DLC costs for SaaS platforms for the fixed-cost math.

Assign compliance responsibility in writing

Compliance is the sender's responsibility, and when you resell, your customer is the sender while you're the platform. Say so in your terms. Ready gives you tools that reduce risk: STOP handling, quiet hours, an optional TCPA and DNC scrub and a sender attestation. None of that makes anyone immune to a lawsuit.

Spell out who owns what:

  1. Your customer owns their consent records and their message content.
  2. You own the product, the sub-account setup and the support path.
  3. Ready stores a sender attestation per bulk or API send. It doesn't keep a per-contact opt-in record, so your forms or CRM should.

Also set content rules. Texting people who never agreed is a problem on any platform, and a scrub doesn't fix it. Ready isn't HIPAA compliant and doesn't sign BAAs, so tell customers to keep health details out of texts.

Handle registration for every customer

Each reselling customer needs their own carrier registration under their own legal business, with an EIN. Most approvals take 2 to 7 days, and a rejected campaign needs a clear message back to the customer. Build that into onboarding. Our 10DLC registration API guide shows how to drive it from your product.

Support is part of the product you're reselling. When a text gets filtered, the customer calls you, not us. Decide who answers, how fast, and what you can see in the account. Budget time for it, because it's the cost most resellers underestimate.

A launch checklist

Before you sell the first text:

  1. Write the pricing page and the bill lines.
  2. Decide the markup per customer type.
  3. Build the usage meter and test it with an emoji text.
  4. Draft the compliance terms so each party's duties are written down before a dispute.
  5. Run registration end to end with one friendly customer first, and fix what confuses them.

When that's done, sign up and send a first text. Sending needs a card and a number on the account, and every text is charged at the normal rate. Read the API quickstart for the request shape.