Every reply is billed like a send: budgeting a 6-text booking inbox

Most texting budgets get built by counting what the business sends: one confirmation and one reminder per job. A salon, cleaner or plumber that books by text does not have a one-way list. It has a conversation. The customer asks, you offer times, they pick one, you confirm, they say thanks, and you remind them the day before. That is six texts, and on Ready, half of them are the customer's.

On Ready, a reply you receive is billed the same way as a text you send: $0.0075/segment plus the $0.0045 carrier fee, or $0.012 per segment in total. This post models what a two-way booking inbox costs per job and per month. It shows how a chatty customer or one emoji raises the segment count, and it compares the result with per-seat business texting tools. We make Ready, so we also point out where it is not the right fit.

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.

Why replies cost the same as sends

Carriers meter traffic in both directions. A text that arrives on your number travels the same network as one you send, and the carrier fee applies either way. Ready itemizes that fee separately, so the bill shows what the carrier charged and what we charged. Our post on the carrier fee line item explains how that fee works.

For a booking inbox, this means a budget that counts only outbound texts covers about half the real bill. A shop that books through conversations should plan on roughly as many inbound segments as outbound ones. Customers who write long messages can push the inbound share higher.

The 6-text booking, segment by segment

Here is a worked example. The booking is for a cut and color, the texts are typical for a salon, and the character counts are approximate.

That is 6 segments × $0.012 = $0.072 per booked job.

The emoji in text 5 does not change anything here. It switches that message to unicode, which lowers the single-segment limit to 70 characters, but "Perfect, thank you 😊" fits under 70. In the next section, an emoji in a longer message does change the count.

Where the segment count creeps up

The customer writes a paragraph

The segment rules are simple. A GSM-7 text fits 160 characters in one segment. Longer texts split into segments of 153 characters each. A single emoji or other non-GSM character switches the whole message to unicode, which fits 70 characters in one segment and 67 per segment once it splits.

Suppose text 1 instead reads: "Hi! My sister got her color done with you last month and loved it 😍 do you have anything Saturday? I'm thinking cut, color and maybe a gloss, how much would that run?" That is about 180 characters with an emoji, so it uses 3 unicode segments instead of 1.

Trades see the same pattern, often with larger numbers. A customer describing a leak ("water's coming from under the kitchen sink, looks like the pipe behind the disposal...") can easily write 300 characters:

• 300 characters, plain text: 2 segments (2 × 153 = 306 capacity)
• The same 300 characters with one 😬: 5 segments (300 ÷ 67 = 4.5, rounded up)

The emoji alone more than doubles the segment count on that message. You can't control what customers type, and you shouldn't try. Price for it instead.

Your own confirmation runs long

Text 4 sits close to the 160-character limit. If you add a parking note or a cancellation policy, it becomes 2 segments. On your outbound side, Ready replaces curly quotes, long dashes and ellipses with plain ones before sending, so a stray "smart" apostrophe won't push your confirmations into unicode. An emoji you type yourself still will.

The heavier, more realistic job

Combine the long first message (+2 segments) with a 2-segment confirmation (+1), and the booking costs 9 segments × $0.012 = $0.1080. The rest of this post budgets with both versions.

What it costs across a month of jobs

The rate is flat. It is $0.0075/segment on Standard at 300 segments or 5,400, so the column grows in a straight line.

Don't forget the threads that never book

Not every inquiry becomes a job. A customer asks a price, gets an answer and goes quiet. Suppose that for every 300 booked jobs, another 150 threads end after 3 segments. That adds 450 segments, or 450 × $0.012 = $5.40 a month. If you use missed-call text-back, some of those threads start with your auto-text. They still cost the same per segment.

The fixed costs on top of the messages

Registration

A steady booking inbox should run on a registered A2P 10DLC campaign, because carriers filter unregistered traffic. On Ready, registration has no setup fee. You pay $25 at submit, which is the first month. After that, the monthly cost is $25 for registration and $2 per number, so $27 a month with one number. Most approvals take 2 to 7 days. Our post on shared vs dedicated numbers explains why a shared number gets filtered.

• At 6 segments per job: 1,800 × $0.012 = $21.60 in messages, plus $27 in fixed fees
• At 9 segments per job: 2,700 × $0.012 = $32.40 in messages, plus the same $27

The compliance surcharge (off by default)

Scrubbing and landline validation each add $0.003 per segment when you switch them on for an account. Both are off by default. As a worst case, assume both are on and the surcharge applies to every segment in the model. The 9-segment, 300-job month then runs 2,700 × 2 × $0.003 = $16 more.

Whether you need either one depends on how you use the inbox. If customers text you first, the case for scrubbing is weaker than if you text a list you bought or imported. If you also send campaigns to older contacts, the case is stronger. Compliance is your call and your responsibility. These tools reduce risk; they don't make you immune to lawsuits.

Quiet hours

A customer may text at 10:40 PM asking about tomorrow. Because they texted you in the last 24 hours, your reply from the inbox can go out right away. A text you start yourself during their quiet hours is held only if their window opens within 6 hours; otherwise it is refused and not charged, and you send it again once the window opens. Tell customers in your confirmation template when to expect a reply.

Getting started

The first 20 texts are free one-to-one sends, which covers testing a booking thread. Use them before you register, because they end as soon as you pay for registration. To send, you add a card and get a number, which is $2 a month with the first month charged when you get it. An account can send up to 500 texts a month before it registers, at its normal per-text rate. After that, it has to register.

Comparing it with per-seat business texting tools

Tools like Salesmsg, Skipio and OpenPhone charge per seat. You pay a monthly fee for each person who uses the inbox, so the bill grows with headcount. Usage-based pricing grows with the number of conversations instead. To compare the two, look at your own invoice rather than our estimate:

1. Find your current monthly texting bill, including seats and any overage.
2. Count your booked jobs last month and estimate segments per job (6 if customers are brief, 9 or more if they write paragraphs).
3. Multiply segments by $0.012 and add $27 for registration and one number. Exclude the compliance surcharge unless you plan to switch it on.

Here is how that usually plays out. A three-chair salon with three people answering texts pays three seat fees under per-seat pricing. On Ready, the same 300-job month costs its message spend plus $27 in fixed fees, and the inbox, CRM, pipeline and automations come with it instead of being priced per user.

Per-seat pricing can be the better deal in some cases. A solo operator booking 40 jobs a month, already comfortable with a per-seat app and its allowance, may gain little from switching. The decision isn't worth a migration over a few dollars.

Raw APIs and GoHighLevel also charge less per message. Twilio is about $0.0083/segment before you build an inbox, and GoHighLevel's LC Phone is about $0.0083 a message, or about $0.0128 all-in. If you're already set up on LC Phone and happy with it, the per-message math favors staying. The reasons to switch to Ready are self-serve registration, the compliance stack and the included platform, not a lower per-text price.

Keeping a booking inbox lean without sounding curt

• Keep confirmations under 160 characters. Put the deposit link and policy in the confirmation and move extra details to a link. The AI message writer and spam-filter check can help you shorten a template.
• Leave emoji out of your own templates. One emoji in a 150-character confirmation turns 1 segment into 3.
• Offer two specific times, not "when works for you?" An open question often adds a round of back-and-forth.
• Combine the reminder and prep instructions into one text instead of sending them separately. Our appointment reminder templates are written to fit in one segment.
• Don't ask customers to keep replies short. A detailed leak description helps you quote the job, and two extra segments cost less than five cents.

The practical takeaway

Budget a two-way booking inbox by segments in both directions, not by texts you send. Use 6 segments per job as the floor and 9 as a realistic planning number. At $0.012 per segment, excluding the compliance surcharge, that comes to roughly 6 × $0.012 = $0.07 to 9 × $0.012 = $0.11 per booked job in message costs, plus $27 a month for registration and one number. Add a few dollars for inquiries that don't book. If you switch on scrubbing or landline validation, add up to $0.003 per segment for each.

Then compare that total with what one job is worth to you. The messaging cost is small relative to the job, but it's still worth knowing exactly what it is. To run the numbers on your own inbox, the per-segment card is on our pricing page, and you can set up an account and test a booking thread with your first 20 free texts before you register.

Frequently asked questions

Do incoming text replies cost money on Ready?

Yes. On Ready, a reply you receive is billed the same way as a text you send: $0.0075 per segment plus the $0.0045 carrier fee, or $0.012 per segment in total. Carriers meter traffic in both directions, so the carrier fee applies either way. For a booking inbox, plan on roughly as many inbound segments as outbound ones, and more if customers write long messages.

How much does it cost to book an appointment by text?

In the post's worked example, a 6-text salon booking uses 6 segments, which comes to 6 × $0.012 = $0.072 per booked job. A heavier, more realistic job with a long first message and a 2-segment confirmation uses 9 segments, or 9 × $0.012 = $0.1080. Registration adds $27 a month with one number on top of the message cost.

Does an emoji make a text message cost more?

Often, yes, because one emoji switches the whole message to unicode. A unicode text fits 70 characters in one segment and 67 per segment once it splits, versus 160 and 153 for plain GSM-7 text. A 300-character message is 2 segments in plain text but 5 with one emoji. Short replies like "Perfect, thank you 😊" still fit in one segment. On outbound texts, Ready swaps curly quotes, long dashes and ellipses for plain ones before sending.

Is per-seat business texting a better deal for a small shop?

It depends on your headcount and volume. Per-seat tools like Salesmsg, Skipio and OpenPhone charge a monthly fee for each person using the inbox, so the bill grows with staff. Usage-based pricing grows with conversations instead. A solo operator booking 40 jobs a month who's happy with a per-seat app may gain little from switching. A three-chair salon with three people answering texts pays three seat fees, so it's worth comparing against your own invoice.