SMS8

SMS glossary 31 messaging terms in plain words.

This SMS glossary explains the words you meet when you send business texts: A2P and P2P, 10DLC and The Campaign Registry, short codes and sender IDs, GSM-7 and segments, MMS, RCS and iMessage, webhooks, MCP and SMS gateways. Each term has a short definition and, where it matters, how SMS8 handles it when you send from your own phone and SIM.

Rules and registration terms

A2P (application-to-person)

A2P messaging is traffic sent by software to people: order updates, reminders, codes and marketing sent through an API or a platform. Carriers treat A2P traffic as business messaging and, in the United States, require it to run on registered routes such as 10DLC, toll-free or short codes. Unregistered A2P traffic on those routes is filtered or blocked.

With SMS8 your texts leave the SIM in your own Android phone, the same way a person sends them, so there is no A2P 10DLC brand or campaign to file. The background is in A2P 10DLC explained and how to avoid it.

P2P (person-to-person)

P2P messaging is a text sent from one phone to another, the way you text a friend or a customer from your own mobile. It uses a normal mobile number and the normal mobile network, and replies come straight back to that phone. Carriers expect P2P traffic to look like human conversation, so sending is paced rather than blasted.

SMS8 sends from your own phone and SIM, which is why customers see your real number and can reply to it. See the Android SMS gateway page for how it works.

10DLC (10-digit long code)

10DLC is the US system for sending A2P text messages from ordinary 10-digit phone numbers. Before a business can send on a 10DLC number through a cloud provider, it registers a brand and a campaign that describes the use case, and pays registration fees. Rejections and resubmissions can add weeks before the first message goes out.

SMS8 does not need 10DLC registration because messages go person-to-person from your SIM. See how to send bulk SMS from your own phone legally.

The Campaign Registry (TCR)

The Campaign Registry is the US industry hub where brands and 10DLC campaigns are registered and vetted. Messaging providers submit the business details and the use case to TCR, and carriers use the result to decide throughput and filtering. Each campaign describes what you send, sample messages and how people opt in.

Because SMS8 sends P2P from your own SIM, there is nothing to submit to TCR before you start.

Toll-free verification

Toll-free verification is the review a US or Canadian toll-free number (800, 888, 877 and similar) must pass before it can send business texts at volume. The provider submits the business, the use case and sample messages, and unverified numbers are restricted or blocked. It is a separate process from 10DLC.

SMS8 sends from the mobile number on your SIM, so no toll-free number or verification is involved.

Opt-out / STOP

An opt-out is a recipient telling you to stop texting them, usually by replying STOP. Respecting opt-outs is a legal and carrier requirement in many countries, and every marketing message should say how to opt out. Once someone opts out, you should not text them again unless they opt back in.

In SMS8, when a contact replies with the single word STOP, the number is added to your blacklist and pending or queued messages to it are canceled. Campaign basics are on the SMS marketing page.

Quiet hours

Quiet hours are the times of day when you should not send non-urgent texts, typically late evening and early morning in the recipient's time zone. Some countries and states set legal sending windows for marketing messages. Sending inside reasonable hours also gets more replies and fewer opt-outs.

SMS8 has a sleep time setting in your account: during that window, non-prioritized messages are held and are not sent.

Numbers and sender terms

Short code

A short code is a 5 or 6 digit number, such as those used for voting, alerts or promotions in the US. Short codes are leased, approved per program and built for high volume. They are one-way in practice for most people: customers cannot call them, and they cannot save them as a contact they recognise.

SMS8 sends from a full mobile number you own instead, so replies and calls come back to you.

Long code

A long code is a normal-length phone number, the same format as a personal mobile number. Long codes can send and receive texts and calls, which makes them good for two-way conversations. In the US, business long codes used through a cloud provider fall under 10DLC rules.

With SMS8 your long code is simply the number of the SIM in your phone. Pair a second phone or use a dual SIM to send from more than one.

Sender ID

The sender ID is what the recipient sees as the "from" of a text: a phone number, a short code or, in some countries, a name. Which sender IDs are allowed depends on the country and the carrier. A recognisable sender ID gets more opens and replies than an unknown number.

With SMS8 the sender ID is your own phone number, the one customers may already have saved, so they know who is texting.

Alphanumeric sender

An alphanumeric sender ID shows a brand name, such as "MYSHOP", instead of a number. It is allowed in many countries, often after registration, and not allowed in others such as the US. Recipients cannot reply to an alphanumeric sender, so it only suits one-way messages.

SMS8 sends from a real number rather than a name, so every message can get a reply into your team SMS inbox.

E.164

E.164 is the international format for phone numbers: a plus sign, the country code and the national number with no spaces or leading zero, up to 15 digits in total. For example, a US number is written +14155550100. Using E.164 everywhere avoids failed sends caused by missing country codes.

The SMS8 API accepts numbers in the number field, and writing them in E.164 is the safest choice. See the SMS8 API documentation.

Message format terms

GSM-7

GSM-7 is the default character set for SMS. It covers basic Latin letters, digits and common punctuation, and fits 160 characters in a single message. A few characters, such as the euro sign, square brackets and the tilde, take two character slots.

Paste a draft into the free SMS character counter to see which encoding it uses.

UCS-2 (Unicode)

UCS-2 is the encoding used when a text contains a character outside GSM-7, such as an emoji, Arabic, Chinese or many accented letters. A single UCS-2 message holds 70 characters instead of 160. One emoji in a long message can switch the whole text to UCS-2 and multiply the number of segments.

SMS8 has no per-message fee, so a Unicode text does not cost more on your plan.

SMS segment

A segment is one SMS unit on the network: up to 160 GSM-7 characters or 70 UCS-2 characters. Longer texts are split into several segments, and most cloud providers bill each segment as a separate message. Knowing the segment count is how you predict cost on per-message pricing.

SMS8 plans include unlimited SMS and MMS, so segments do not change your bill. Compare costs with the SMS cost calculator.

Concatenated SMS

A concatenated SMS is a long message sent as several segments that the receiving phone joins back into one text. Each segment carries a small header, which is why a multi-part GSM-7 message holds 153 characters per segment and a multi-part UCS-2 message holds 67. The reader sees one message.

Long texts sent through SMS8 leave your phone as normal long messages, with no extra fee per part.

MMS (multimedia messaging)

MMS is the format for texts that carry pictures, GIFs, audio or video, or a longer body with a subject. It travels over the carrier's data path and shows inline in the recipient's messages app. Size limits depend on the carrier.

SMS8 sends MMS from your Android phone: in the API set type=mms and pass public image links in attachments. The details are in how to send MMS with an API.

RCS (Rich Communication Services)

RCS is the successor to SMS on Android, with typing indicators, read receipts, high-quality media and longer messages over data. It works when both phones and carriers support it, and falls back to SMS when they do not. Business RCS through cloud providers usually needs a verified sender program.

SMS8 sends SMS, MMS and RCS from the customer's own Android phone and SIM. See the Android SMS gateway.

iMessage

iMessage is Apple's messaging service between Apple devices, sent over the internet rather than the SMS network. It supports long messages, media, reactions and read receipts, and is tied to an Apple ID. Messages to non-Apple phones fall back to SMS.

SMS8 sends iMessage from a Mac you own with the SMS8 Gateway app, with SMS fallback. The recommended pace is 50 new contacts a day per Mac. Read more on the iMessage API page.

Blue bubble

"Blue bubble" is the everyday name for an iMessage, because iPhones show iMessages in blue and SMS in green. Many iPhone users read a blue bubble as a message from a real person they know. That is why businesses want to reach iPhone customers by iMessage.

With SMS8, iMessages leave your own Mac and Apple ID, so they appear as blue bubbles from you. See iMessage marketing and the blue bubble.

Verification terms

OTP (one-time password)

An OTP is a short code, usually 4 to 8 digits, sent to a phone to prove the person controls it. It is valid once and for a short time. OTPs are used for sign-up, login, password reset and payment confirmation.

SMS8 sends OTP codes from your own number, with no per-message fee, and its MCP server includes tools to send and verify codes. See the SMS OTP verification API.

2FA (two-factor authentication)

2FA is a login that asks for two different proofs: something you know, such as a password, and something you have, such as a phone that receives a code. SMS codes are one of the most common second factors because every phone can receive them. Good practice includes short expiry times and limits on attempts.

You can deliver 2FA codes through the SMS8 API or the OTP tools. Best practices are in phone number verification best practices.

Developer terms

Delivery report

A delivery report (DLR) is the status the network sends back after a text: delivered, failed or still pending. It tells you whether the recipient's carrier accepted the message. Delivery reports are the basis of reliable retries and accurate campaign stats.

SMS8 posts delivered and failed events to your webhook, and the status of each message is visible in the dashboard and the API.

Webhook

A webhook is a URL on your server that a service calls when something happens, such as an incoming text. Instead of asking for new data on a timer, your code receives each event as an HTTP POST the moment it occurs. Webhooks should be verified with a signature and should return a 2xx status quickly.

SMS8 webhooks carry an X-Signature HMAC-SHA256 header and are retried at increasing intervals for up to 30 days. Setup is on forward SMS to a webhook.

API key

An API key is a secret string that identifies your account when your code calls a service. It goes in a request header and must be kept out of public code and browsers. If a key leaks, you replace it.

The SMS8 API reads your key from the X-Api-Key header on POST https://app.sms8.io/api/v1/messages. See the SMS API page for examples in five languages.

MCP (Model Context Protocol)

MCP is an open protocol that lets AI assistants such as Claude, Cursor and other tools call outside services through a standard set of tools. An MCP server describes what it can do, and the AI decides when to use it. It turns "text this customer" into a real action.

The SMS8 MCP server is at https://mcp.sms8.io; in Claude Code run claude mcp add --transport http sms8 https://mcp.sms8.io. See the MCP SMS server.

Gateway and hardware terms

SMS gateway

An SMS gateway is the service that turns a request from software, such as an API call or an email, into a text message on the mobile network, and passes replies back. Cloud gateways connect to carriers through their own routes and charge per message. Phone-based gateways use a real SIM to send.

SMS8 is a hosted SMS gateway that sends through your own phone and SIM on a flat monthly plan. Read the cloud SMS vs phone gateway comparison.

Android SMS gateway

An Android SMS gateway is an app on an Android phone that receives send jobs from a server and sends them from the phone's SIM, then reports status and incoming texts back. It gives software the phone's real number. It needs the phone to stay powered, online and allowed to run in the background.

SMS8 works with Android 7 or newer: install the app, scan the pairing code and send. See the Android SMS gateway page and the complete guide.

Dual SIM

A dual SIM phone holds two active SIMs, each with its own number. Both numbers can send and receive texts from the same device. It is a simple way to separate two lines or double what one phone can send.

SMS8 lists both SIMs under the device, and the API lets you pick one per message or rotate across every SIM. See dual SIM and eSIM SMS gateway.

eSIM

An eSIM is a SIM built into the phone and activated by downloading a carrier profile, with no plastic card. A phone can store several profiles and usually keeps one or two active. A data-only eSIM cannot send texts.

To SMS8, an active eSIM with a mobile line is a SIM like any other and sends the same way as a physical card.

Throughput / pacing

Throughput is how many messages a route can send per second or minute; pacing is spreading messages out so they look like normal traffic and are not filtered. Cloud routes set throughput by registration tier. A phone and SIM have a natural pace set by the carrier.

For bulk sends, SMS8 paces one message every 10 to 30 seconds per SIM, and you add phones to send more. For iMessage the recommended pace is 50 new contacts a day per Mac. See unlimited bulk SMS from your own number.

Common questions

Still unsure? We answer fast.

A2P texts are sent by software to people, such as alerts and campaigns through a cloud API, and in the US they must use registered routes like 10DLC. P2P texts are sent from one phone to another. SMS8 sends from your own phone and SIM, so there is no 10DLC filing.

160 characters with the GSM-7 character set, or 70 when the text contains an emoji or other Unicode characters. Longer texts are split into segments of 153 or 67 characters and joined again on the phone.

The gateway is the system that sends the text on the mobile network; the API is how your code talks to it. SMS8 is both: a REST API at app.sms8.io that hands each message to your paired Android phone, which sends it from its SIM.

Not with SMS8. You send from the mobile number of the SIM in your own phone, which customers can save, call back and reply to.

When a contact replies with the single word STOP, SMS8 adds the number to your blacklist and cancels any pending or queued messages to it.

Send from your own number today

Pair a phone or a Mac and send your first message in minutes. 3-day trial with 30 messages, no card needed.