A good client SMS report answers five questions: did the texts arrive, did people reply, did anyone opt out, what did it cost, and is the client's registration healthy. Everything else is decoration. If you can pull those five numbers per client every month, you can explain texting results without hand-waving.
This guide is for agencies and for the developers who build reporting for them. We'll cover what to include, where each number comes from in Ready, how to keep clients' data separate, and how to explain the numbers when they look bad. We aren't quoting industry benchmarks, because rates vary by list, offer and timing, and a made-up average does more harm than a blank cell.
The five numbers that belong in every report
The direct answer: report delivered, replies, opt-outs, cost and registration status, in that order, per client.
| Metric | What it tells the client | Where it comes from |
|---|---|---|
| Texts sent and delivered | Whether messages reached phones | The message list for that sub-account |
| Replies received | Whether people engaged | Inbound messages on the same list |
| Opt-outs | Whether the list is healthy | The opt-outs list for that sub-account |
| Cost per segment and total spend | What texting costs | Your invoice and the rate card |
| Registration status | Whether sending is approved | The registration status for that client |
Put these at the top as a small table, then add a short paragraph of plain language. A client who owns a clinic or a roofing company doesn't need a dashboard tour. They need one paragraph that says what happened and what you'll do next.
Where the numbers come from
The direct answer: each client is a sub-account in Ready, so you can read their messages, opt-outs, numbers and registration separately instead of untangling one shared pool.
Each customer gets a sub-account with its own numbers and carrier registration. The endpoints you need are:
GET /v1/sub-accountsto list the clients you manage (see the sub-accounts docs).GET /v1/messagesto page through a client's messages withbefore_id. Count by direction and status for sends, deliveries and replies. See the messages docs.GET /v1/opt-outsfor the account's opted-out contacts, andGET /v1/opt-outs/:phonefor one number. The plain list covers opted-out contacts on that account only, so it won't include a STOP from a deleted contact or one held on another account in the family. Use?scope=allfor the full Ban list, and see the opt-outs docs.GET /v1/numbersfor the numbers each client has.GET /v1/registrationfor the registration status (more in the registration docs).
Run these on a monthly job, store the results as snapshots, and compute the month from your own copy. That way a report you sent in March still matches in June, even if a contact has since been deleted.
Delivered is not the same as read, and reply rate needs a denominator
The direct answer: define each metric in one sentence in the report footer, so nobody argues about it later.
- Delivered means the network accepted the message for the phone, not that a person read it. Failed and filtered messages are the gap between sent and delivered.
- Reply rate is replies divided by delivered texts, over the same period. State whether you count one reply per contact or every reply.
- Opt-out rate is opt-outs divided by delivered texts to unique contacts.
A worked example, with assumptions: a client sent 1,200 texts in a month, 1,164 were delivered, 96 contacts replied, and 9 opted out.
- Delivery: 1,164 out of 1,200 is 97 percent.
- Reply rate: 96 out of 1,164 is about 8 percent.
- Opt-out rate: 9 out of 1,164 is under 1 percent.
These numbers are invented for illustration. Don't compare your client's figures to them. Compare each client to their own previous month, and write what changed. If you're tracking delivery failures, our guide to text message analytics and delivery reporting goes deeper on how to read them.
Cost per segment, explained once
The direct answer: bill and report in segments, since segments are what get charged, and show the rate beside the total.
Ready's rate is $0.0075 per segment plus a $0.0045 carrier fee, passed through at cost and shown separately on the bill. Replies you receive are billed like texts you send. Accounts opened before November 12, 2026 keep the prices they signed up with, shown under Billing.
A single segment is 160 characters in GSM-7. Longer texts split into 153-character segments, and an emoji drops the limit to 70 characters (67 when split). So a 175-character promo with an emoji is 3 segments, and that's why a client's spend can climb while the message count stays flat. Put one sentence in the report if the average segments per message changed.
If you add a markup or a flat monthly fee for the client, show it as its own line so the pass-through part stays honest. Our post on per-message versus flat rebilling for agencies compares the models, and ties are easier when your report counts segments the way the bill does.
Registration status is a report line, not a footnote
The direct answer: tell the client whether their registration is approved, pending or needs attention, because unregistered traffic gets carrier-filtered.
Registration is a Ready line item per customer, with the brand and its first campaign billed monthly and extra campaigns billed separately. Most approvals take 2 to 7 days. Ready registers businesses with an EIN only, so a client without one has to get an EIN first.
Report it as one of three states:
- Approved. Sending is on, and you list the numbers attached.
- In review. Say when it was submitted and what you're waiting on.
- Needs action. Say exactly what the client has to provide.
For agencies that put the registration under their own brand, our guide to A2P 10DLC for agencies explains who files what.
Keeping the report honest
The direct answer: separate what Ready measures from what your CRM measures.
Texts, replies and opt-outs come from the messaging side. Booked calls, closed deals and revenue come from the client's CRM, and you shouldn't credit texting for them unless you've matched the contacts. When you do match them, say how: by phone number, within what window, and what you did with contacts who were also reached by email or a call.
Don't report a number you can't source. If you didn't track something, write "not tracked this month" and fix the gap.
Compliance deserves a line too. Opt-outs are honored automatically, and quiet hours are enforced based on the recipient's area, which reduces risk. It doesn't remove the client's own responsibility to hold consent for the people they text, and your contract should say who keeps those records.
Frequently asked questions
What should an SMS report for a client include?
Include sends and deliveries, replies, opt-outs, cost per segment with total spend, and registration status. Add one plain-language paragraph on what changed since last month and what you'll do next.
Where do I get per-client numbers in Ready?
Each client is a sub-account, and you can read its messages, opt-outs, numbers and registration separately through the API. Page GET /v1/messages with before_id and count by direction and status.
Should I include industry benchmarks?
Only if you can cite a source and a matching list type. Otherwise compare each client to their own earlier months, which is more useful and can't be wrong.
Next step
Pick one client, pull last month's messages and opt-outs, and fill in the five-row table by hand. Once that reads well, automate the pull for every sub-account. If you want to try the sub-account setup, sign up and read the 10DLC explainer so registration status means something to your clients.