What is business texting? Definition, use cases and getting started

Your customers already read texts faster than email, and many of them already text you. They text the number on your truck, reply to your appointment confirmation, or send a photo of the leak under the sink. Most owners start by answering from their own phone. That works until it doesn't: a carrier filters your messages, an employee leaves with the customer thread on their phone, or someone texts STOP and you have no system that remembers.

Business texting is the version of this that is built for a company. You send from a business number, through a platform that carriers recognize, with opt-outs, consent and history handled in one place. This post covers what the term means, how it differs from personal texting, what registration involves and costs, and how to send your first text.

What business texting means

Business texting is a company sending and receiving SMS (and sometimes MMS, which carries pictures) with its customers from a business phone number, through software rather than a personal phone. The messages look like normal texts on the customer's side. The difference is everything behind them: who sends, how the carrier classifies the traffic, and what records exist.

Carriers call this kind of traffic A2P, short for application-to-person, as opposed to P2P (person-to-person) texting between friends. If you want the full distinction, our explainer on what A2P messaging is goes deeper. In practice, once software sends your texts, carriers treat them as A2P and apply A2P rules.

Business texting vs business messaging

You'll also see "business messaging." It's the wider term. Business texting usually means SMS and MMS. Business messaging includes those plus other channels: iMessage, RCS and chat apps.

One example on our side is the blue line, which sends texts as iMessage so they show up blue on iPhones with your business name and photo. It costs $99 a month per line plus 6 cents a segment. It needs no 10DLC registration. Each line can start up to 50 new conversations a day, with unlimited texting to people you already talk with. For most owners starting out, regular SMS is the right first step. The blue line is an add-on you consider later (docs: docs.tryready.com/guides/imessage).

How it differs from texting from your own phone

The middle row matters most. Carriers watch for business traffic coming from unregistered numbers, and they filter it. Your message says "sent," but the customer never sees it. Texting from your cell is fine for a single conversation. Once you send the same reminder to 80 people from an app, you're sending unregistered A2P traffic, and that's where texts start disappearing.

What businesses actually use it for

The most common uses, roughly in the order owners adopt them:

1. Appointment reminders and confirmations. "Reply C to confirm your 2 PM cleaning tomorrow." This is usually the first use and the one with the clearest payoff, because it cuts no-shows.
2. Order and job updates. Shipping notices, "your tech is 20 minutes out," "your car is ready." These are transactional texts the customer expects.
3. Two-way customer conversations. Questions, quotes and photos, handled from a shared inbox instead of someone's personal phone.
4. Review requests. One text after the job with a link.
5. Promotions to opted-in customers. Seasonal offers or a slow-week discount. These are marketing texts and need a different, stricter kind of consent.

The difference between items 1 to 4 and item 5 changes what you register and what consent you need. Transactional vs promotional SMS walks through where the line falls.

One thing business texting is not for: cold outreach. Contacting people who never gave you their number happens by phone and mail. Texts go to people who opted in or who texted you first.

The registration part: 10DLC in plain terms

If you text US customers from a regular 10-digit business number, the carriers expect you to register. The system is called A2P 10DLC. You register two things:

• Your brand. Your business identity: legal name, EIN, address and website.
• Your campaign. What you'll send and how people opt in, with sample messages.

It isn't a federal law. It's a carrier requirement, and carriers enforce it by filtering unregistered traffic. Our post on whether 10DLC is a law and who has to register covers the edge cases.

On Ready, registration happens in the app, with no setup fee. You pay $25 when you submit, which is your first month. After that, the monthly cost is $25/mo for registration and $2 per number. Most approvals take 2 to 7 days. You don't have to sit idle while you wait. An account can send up to 500 texts a month before it registers, and an account that bought its number first sends on our shared registration while its own is in review. Both send at the normal per-text rate.

What it costs: a worked example

Texts are billed per segment, not per message. A standard segment holds 160 characters. Longer texts split into 153-character segments. A single emoji switches the whole message to a different character set, and the limit drops to 70 characters per segment (67 when split).

Ready's Standard rate is $0.0075 per segment plus a $0.0045 carrier fee, $0.012 a segment all-in, and the same rate applies to replies you receive.

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.

Example assumptions: a 2,000-customer appointment reminder, about 140 characters, no emoji.

• 140 characters = 1 segment
• 2,000 × $0.0075 = $15, plus 2,000 × $0.0045 = $9 in carrier fees, $24 in all

Same reminder with one emoji added:

• 140 characters with an emoji = 3 segments (67 + 67 + 6)
• 6,000 segments × $0.0075 = $45, plus 6,000 × $0.0045 = $27 in carrier fees, $72 in all

One smiley face tripled the bill. Our app swaps curly quotes, long dashes and ellipses for plain ones before sending, so those won't change your count. Emoji will.

Price comparison, plainly: if you're a developer who only wants a raw API, Twilio lists about $0.0083 a segment, which is lower than our Standard rate. GoHighLevel's LeadConnector runs about $0.0128 all-in, also lower. What you get with Ready is in-app registration, the compliance controls below, a CRM, pipeline, automations and a unified inbox in one product. Full numbers are on our pricing section.

Consent, opt-outs and quiet hours

Compliance is ultimately the sender's responsibility. A platform can lower your risk but can't take it over. What we build in:

• STOP handling. When someone replies STOP or UNSUBSCRIBE, that number is blocked from every future campaign. Opted-out numbers are refused before sending and you aren't charged for them.
• Quiet hours. Texts are held outside permitted local hours based on the recipient's area, and they send later. You're charged only when they actually send. Campaigns, drip campaigns and automations wait up to 24 hours for the window; a one-to-one or API text is held only if the window opens within 6 hours, otherwise it is refused and must be resent; a one-to-one reply to someone who texted you in the last 24 hours goes out at any hour.
• Attestation records. Each bulk send and each API send that attests consent logs who sent it, to how many people, and when. This is not a per-contact consent record. Your signup form or store should keep each customer's opt-in time and wording. What opt-in means for texting covers what that record should hold.
• Optional scrubbing. TCPA-litigator and DNC screening, plus landline validation, each cost $0.003 extra per segment when switched on. Both are off by default. TCPA damages run roughly $500 to $1,500 per text, so the scrub is cheap insurance for larger lists. It reduces risk; it doesn't make you immune.

Getting started with Ready

Here's the order we'd follow as a new owner:

1. Create an account at /signup. To send, you add a card and get a number, which is $2 a month with the first month charged when you get it.
2. Get a number, local to your area if you can.
3. Use your 20 free texts first. They're for one-to-one sends (campaigns are paid from the first text), and they end once you pay for registration. Text yourself and a few willing customers, and check how messages look on their phones.
4. Register your brand and campaign in the app. Pick the use case that matches what you'll actually send.
5. Import only consented contacts, then save your reminder or update as a reusable template. Check its length before you add an emoji.
6. Send, and answer replies from the inbox.

If you run GoHighLevel, Ready installs natively and syncs messages two ways per sub-account. If you're building software, the API quickstart covers the API.

The short version

Business texting means texting customers from a business number through software, registered with the carriers, with opt-outs and records handled for you. Start with one transactional use, such as reminders or job updates. Register early, because most approvals take 2 to 7 days. Watch your segment count, because emoji multiply the bill. Text only people who asked to hear from you. If that sounds like what you need, use your first 20 texts to try it before you commit to anything bigger.