They text you. They leave with a booking.

They text a normal phone number

Your business gets a dedicated phone number and customers text it the way they text anyone. There is no app to install, no link to tap, no portal to log into, and no account to create. They open their messages, type, and send.

It is a real number of your own, not a shared shortcode that a customer has to be told is special and that arrives on their phone looking like a marketing blast from a company they have never heard of. The thread sits in their message list with your name on it, and it is still there in three months when they need you again.

• A dedicated business phone number, not a shared shortcode
• No app, no link to tap, and no account to create
• The thread stays in their message list and is easy to find again
• Answered in seconds, day and night, including the hours you are closed

The booking finishes in the thread

The usual answer to a text enquiry is a link. Here is our booking page, go and pick a time. A good share of customers never open it, and a share of the ones who do abandon it on a phone with two bars of signal.

Here the booking completes in the message thread. Availability is checked against your live calendar as the conversation happens, the open times come back, and the appointment is written directly to the calendar once the customer picks one. No page to load, no callback promised, no second system to check afterwards.

It is the same machinery described on the booking and no-show prevention page, delivered over text: real availability, then risk scoring on the booking that comes out of it.

• Real availability checked live, then written to your calendar
• No booking link to send and no page for the customer to open
• Google Calendar and Calendly both supported
• Every booking scored for no-show risk, with reminders timed to match

So does the order

Ordering over text is treated as a first-class path rather than an afterthought. The order is built turn by turn in the thread, with modifiers and variants captured as structured data rather than as a paragraph somebody has to read out at the pass.

Money is handled in integer cents throughout, so the total the customer sees and the total they pay are the same number. You get a receipt on your phone the moment an order confirms, and the pickup time is resolved rather than left as a vague soon. See how ordering works across every channel.

• Orders completed over text, with modifiers and variants
• Structured data, not free text somebody has to decode
• Money handled in integer cents, so totals are exact
• An owner receipt on your phone the second an order confirms

Reminders arrive in the same thread, and replies are acted on

Confirmations and reminders go back into the conversation the customer already had with you, not out from an unfamiliar number that reads like spam. One thread, one continuous record of their relationship with your business.

And the replies are read. When somebody answers a reminder with yes, or asks to move it to Friday, or says they need to cancel, that reply is classified and acted on: confirmed, rescheduled, cancelled, automatically, without you touching anything. The booking status moves on its own as a result.

Quiet hours and timezone handling sit underneath all of it, so nothing sends in the middle of the night, wherever the customer is. That is the part customers notice and the part that decides whether your messages get read or muted.

• Confirmations and reminders in the same thread as the conversation
• Replies classified and acted on: confirmed, rescheduled, or cancelled
• Booking status updates automatically, without the owner in the loop
• Quiet hours and timezone handling, so nothing sends overnight

The compliance part, said out loud

Plenty of owners have been burned by a texting vendor once, and the damage is not a bad month. It is a customer who asked to stop hearing from you and got another message six weeks later.

Opt-out is enforced in code rather than requested in a prompt or left as a checkbox somebody has to remember. An opted-out customer is excluded from every segment from that point on, permanently. Every campaign message carries the required footer, applied automatically.

One honest limit worth stating: campaign messaging is subject to carrier registration and consent. This is not an unlimited or unrestricted texting firehose, and anyone selling you one is selling you a problem. Conversational replies to a customer who messaged you first and campaign sends to a consented list are different things, and the platform treats them differently.

• Opt-out enforced in code, not in a prompt or a checkbox
• The required footer applied automatically to campaign messages
• Campaign messaging is subject to carrier registration and consent
• Opted-out customers excluded from every segment, permanently

Questions owners ask