If your platform texts on behalf of customers, give each customer its own branded short domain, keep the redirect on infrastructure you control, and count clicks on your server rather than trusting a third-party shortener. Public shorteners share a reputation with every other sender on them, and carriers have been known to filter messages that carry those links. A short link you own is the safer default.
This post is a design guide for the team that has to build it. It's about the plumbing: domains, redirects, the data you store and the clicks you shouldn't believe. For the deliverability reasoning behind owning the domain, see why carriers filter public URL shorteners.
What Ready does and doesn't do here
Be clear about the boundary first. Ready sends the text you give it, and the request shapes in our API don't include link shortening or click reporting. If your product needs short links, you build the link service, or buy one, and put the finished short URL in the message body. Ready doesn't rewrite your links.
That's a fair split for a platform, because the link is part of your product. Your customers will want to see who clicked, and you'll want that data in your own database next to the contact. What Ready does handle is the sending side: sub-accounts for each customer, registration, the opt-out and compliance checks, and the per-segment billing that your link choices affect.
Why the link choice matters for cost and delivery
Two things happen when you add a URL to a text. The message gets longer, and the message gets looked at harder.
On length, a 23-character short link is cheap, but a long tracking URL with parameters can push a 150-character message past 160 and into a second segment. That doubles the cost of the send. If your body also holds an emoji or a curly quote, it's already UCS-2 with a 70-character limit, and a link makes that worse. We cover the arithmetic in SMS segment counter in code.
On scrutiny, carriers weigh links when they decide what to filter. A link on a shared public domain inherits the history of everyone else using it. A link on a domain tied to one customer's registered brand has only that customer's history. And a link in the very first message to a contact draws extra attention, which our post on the first-message link filter explains.
The architecture, in parts
A link service for a platform has five moving parts.
| Part | What it does | Design note |
|---|---|---|
| Domain per customer | Serves the short links for one sub-account | Use a subdomain of the customer's own site where they allow it |
| Link table | Stores code, destination, contact, message and customer | Scope every row by customer so tenants can't see each other's data |
| Redirect handler | Looks up the code and returns a redirect | Keep it fast and independent of your main app |
| Click log | Records each hit with time and user agent | Append only, written after the redirect is sent |
| Reporting | Rolls clicks up per message, campaign and contact | Filter likely bots before you show a number |
The domain row is the one people skip. If every tenant shares your one short domain, you've rebuilt the public-shortener problem inside your own product, and one customer's spam complaints land on all of them. Giving each sub-account its own domain isolates reputation the same way sub-accounts isolate registration.
Unique links per recipient or per message
You have two options for what a code identifies. A link per campaign tells you how many people clicked in total. A link per recipient tells you who clicked, which is what a CRM user wants on a contact timeline. Per-recipient links cost you a row per message, but that's cheap storage, and they also let you do things like stop a link from working after an opt-out.
Pick codes that can't be guessed. Sequential or short random codes let someone enumerate links and read other people's destinations. Use enough random characters that guessing is impractical, and don't encode the contact's phone number or name into the code.
Keep the destination simple. A redirect to a page on the customer's own site, with your tracking tied to the code rather than stuffed into the query string, keeps the message short and the landing page clean.
Expiry, errors and abuse
Decide up front what happens when a link is old, deleted or wrong. A text can be opened weeks after it was sent, so an expired code should land on a plain page that explains the situation, not a bare error. Serve every short link over HTTPS, and keep the destination on HTTPS too.
Abuse is the other half. If your customers can enter any destination, someone will point a short link at something harmful, and the damage reaches the domain's reputation. Check destinations against a block list, refuse redirects to other shorteners, and give yourself a switch to disable one customer's links without touching the rest. That's another reason for a domain per customer: you can pull one without breaking the others.
Clicks you shouldn't believe
A click count is only useful if it's roughly honest, and with SMS it often isn't. Link previews, security scanners and some phone software fetch a URL before a human taps it. If you log every request as a click, your numbers will be inflated and the first campaign report will look too good.
Some habits that help:
- Log the user agent and the request headers, then filter known preview and scanner patterns in reporting rather than at write time, so you can improve the filter later.
- Treat several hits within seconds of delivery as suspect, since people rarely tap that fast.
- Report unique clickers per message, not raw hits.
- Label the metric "estimated clicks" in the UI if you can't be sure.
Our post on link previews and carrier stripping goes into why preview fetches happen at all.
Privacy and compliance duties
A click log is personal data tied to a phone number. Decide what you keep and for how long, write it in your customers' terms, and give a customer a way to delete a contact's records. If a recipient opts out, your link service shouldn't keep generating personalized links for them.
The sending side has its own rules. Ready honors a STOP reply and blocks further texts to that number on the sub-account that received it, but that's about texts, not your click data. Compliance is ultimately the sender's responsibility, and the platform should make it easy for the customer to do the right thing, such as recording consent and disclosing the link's purpose. For the legal side of texting, our TCPA guide is the place to start.
Worked example: what a link does to the bill
Assume a customer sends a 140-character reminder to 8,000 contacts. A 23-character short link brings it to 163 characters, which is 2 segments in GSM-7. Trim the copy by 4 characters and it's 1 segment. At Ready's Standard rate of $0.0075 plus a $0.0045 carrier fee per segment, that's $0.012 per segment all-in, so the send is either 16,000 segments or 8,000 segments, billed at $0.012 each. Four characters of copy decide which. The all-in figure excludes screening, the per-segment charge for Scrub lists and Number validation when switched on.
Ready's all-in prices per segment include the carrier fee but not screening: Scrub lists and Number validation, the two switches in Settings under Compliance, each add $0.003 per segment when switched on, shown as screening on your bill, and both are off by default. Unless you turn the opt-out footer off, the first text to each contact, and one again from time to time, also gets "Reply STOP to opt out" and your business name if the message does not already have them, so a text close to the segment limit can bill one more segment.
The numbers are assumptions, but the lesson holds: budget the link's characters when you design the composer, and make the link length visible next to the segment count. Accounts opened before November 12, 2026 keep their signup prices, shown under Billing, and the pricing page has the current rates.
The practical takeaway
Own the domain, one per customer. Keep the redirect fast and separate, store clicks on your side, and treat the count as an estimate until you've filtered scanners and previews. Count the link's characters before you send. When the short URL is in the body, the send is the ordinary call described in the messages API reference, and you can try it from the API quickstart.