Every few months someone asks us, gently, why we still put engineering time into SMS. It's not the exciting channel. Voice has the hard real-time problems. The web widget has the design work. Texting is a technology that was everywhere decades ago.
The honest answer is that SMS reaches people the other two channels structurally can't, and that gap doesn't close no matter how good a chat widget gets. A widget only works for someone who is on your website right now, with a capable device and a working connection, willing to stay on the page long enough to type.
That's a real customer, and an important one. It's also a narrower slice of your customer base than it feels like from inside a product team that spends its days looking at widget conversations. Plenty of customers find you through a saved number, a friend's recommendation, or a printed card, and never open your site at all.
If you're deciding whether texting deserves a place next to your widget, the comparison table further down is the quickest route; it's also where we're most candid about what SMS does badly.
What is business SMS, and how does it differ from a chat widget?
Business SMS means two-way text messaging between your business number and customers' phones. A customer texts the number they already have saved, and your business replies. No app, account, or browser is involved on the customer's side.
A chat widget is a conversation window on your website. It answers visitors in real time, in text or voice, and Aiva Chat's web widget can book appointments and answer questions from your business information instantly.
In Aiva Chat, the two work differently by design:
- The widget is automated. The AI answers visitors directly and can book into your calendar.
- SMS automation is opt-in. With Booking by text turned on, the AI replies to appointment texts on its own: it books, moves, and cancels. Other texts wait for a team member, who can click for an AI-drafted reply, edit it, and send it.
- SMS can't look things up. By text, the AI can't run live lookups or custom actions, such as checking an order's status.
- Both share one inbox. Texts, chats, and calls sit together, so your team sees the full history.
Texting suits businesses whose customers already text them: clinics, salons, home services, tutors, and local shops. It's especially valuable where customers include people on basic phones, limited data plans, or busy schedules.
How business texting works in Aiva Chat
Step 1: The customer texts your number
They use the number they already know, often saved from an earlier visit or call. No website visit is needed.
Step 2: The thread lands in your inbox
The message appears in Aiva Chat's Conversations inbox next to calls and chats. If the customer sends a photo or voice note, Aiva Chat reads the image or transcribes the audio so your reply can respond to what was actually sent.
Step 3: The AI or a person replies
If Booking by text is on and the text is about an appointment, the AI replies on its own, and its texts are marked "Sent by AI" in the inbox. For anything else, click "Suggest a reply" and Aiva Chat writes a draft in the customer's language using your business information. Edit it as needed and send. A reply from your team pauses the AI on that conversation, so you can take over any thread.
Step 4: Opt-outs are handled automatically
If a customer texts STOP, Aiva Chat confirms once and adds the number to your do-not-contact list. START opts them back in, as carriers require. A few other texts can go out without a person pressing send: a booking confirmation after a call or chat booking, and, if you switch on the built-in "Missed call text-back" rule on the Webhooks page's Workflow Rules tab, a text to anyone whose call you missed. Beyond those, replies to customers' texts go out automatically only when Booking by text is on.
Step 5: Bookings move to the right channel
If a texting customer wants to book and Booking by text is on, the AI offers open times and books in the thread. If it's off, your team can call them back or point them to your website chat. After a booking, a text confirmation can go out.
Why SMS reaches customers a chat widget can't
It needs almost nothing from the customer
No app to download, no account, no browser, and no page to load. A customer needs one thing: a phone that can send texts. That describes nearly every mobile phone in use, new or old. A widget needs a capable device, a connection, and a website visit.
Not everyone has a smartphone
Pew Research Center found in 2025 that 98% of U.S. adults own a cellphone of some kind, while 91% own a smartphone. The gap is small in percentage terms but represents millions of people, and it's wider in many markets outside the U.S. Those customers can text you. They can't use your widget.
It meets customers who never visit your site
Someone who got your number from a neighbor, a flyer, or a past appointment has no reason to open your website. They'll text or call. A widget, by definition, only reaches people already where the business wants them.
Async suits busy customers
A customer mid-shift or mid-errand can read a text between tasks and reply an hour later without losing anything. A live chat in a background tab doesn't offer that. For plenty of conversations, a slow back-and-forth is simply the better fit. Our post on Aiva Chat's SMS engine covers how threads stay coherent across long gaps.
It's good for low-effort follow-ups
A booking confirmation or a quick follow-up that a customer can answer in five words from wherever they are suits texting well. So does a missed call: Aiva Chat's missed-call text-back rule texts the caller from your own number (only between 8 AM and 9 PM, and never to numbers on your do-not-contact list) and adds a call-back task for your team. Keep those messages short enough to read at a glance.
The customer who isn't on your website right now is still your customer, just on a different channel, and SMS is often the only one that reaches them.
SMS use cases that a widget can't cover
These scenarios are illustrative.
The customer with a saved number
Problem: A regular salon customer wants to know if Saturday is busy. She has the number saved and no interest in visiting the website. How Aiva Chat handles it: With Booking by text on, Aiva Chat replies with Saturday's open times and can book her in. Otherwise her text lands in the inbox; staff click for a suggested reply, check it, and send it between clients. Outcome: She gets an answer in her preferred channel, and staff spend seconds at most rather than a phone call.
The customer at work
Problem: A clinic patient can't take calls during a shift but wants to ask about test results timing. How Aiva Chat handles it: The text thread holds the question; staff reply with a drafted answer when free, and the patient reads it on a break. Outcome: No phone tag, and the conversation is still there an hour later.
The photo of the problem
Problem: A homeowner texts a photo of a leaking pipe asking whether it's urgent. How Aiva Chat handles it: When staff click Suggest a reply, Aiva Chat reads the image and drafts a response suggesting a call for an emergency booking; staff send it and the customer calls. Outcome: The text starts the conversation, and booking happens on a call where it belongs.
The customer on a basic phone
Problem: An older customer uses a feature phone and never browses the web. How Aiva Chat handles it: Texting works exactly as it would on a smartphone. Outcome: A customer the widget could never reach stays in touch.
SMS vs. chat widget: honest comparison
| Business SMS (Aiva Chat) | Website chat widget (Aiva Chat) | |
|---|---|---|
| Customer needs | Any phone that can text | Website visit, capable device, connection |
| Who replies | The AI for appointment texts when Booking by text is on; otherwise a person, using AI-drafted suggestions | The AI, automatically |
| Books appointments | Yes, once Booking by text is turned on | Yes |
| Conversation pace | Asynchronous, over hours | Real time, in one sitting |
| Rich formatting and long answers | Poor, plain text only | Good |
| Reaches customers who never visit your site | Yes | No |
| Setup requirement | Texting-capable number; A2P 10DLC for US numbers | One script tag on your site |
The widget is better at a lot. It answers instantly without staff involvement, books appointments directly, and handles longer or more detailed answers well. For a visitor with intent, already on your pricing page, it's the right tool, and texting can't match it.
SMS gives up formatting and some automation. A long policy explanation becomes a wall of text, booking by text stays off until you turn it on, and texts the AI can't handle still need someone on your team to reply. Those are real costs.
What SMS keeps is reach. It works for customers who aren't on your site, aren't on a smartphone, or aren't free to chat in real time. That's why we treat it as its own channel, not a fallback. Our post on why voice comes first, SMS second, and the widget third explains how the three fit together.
How to set up business texting in Aiva Chat
Step 1: Confirm your number can text
Use a Twilio number with SMS capability. Your existing voice number may already support it.
Step 2: Register for A2P 10DLC if you're in the US
US carriers require business senders on standard numbers to register. Twilio's A2P 10DLC guide explains the standard; Aiva Chat's registration walkthrough covers the steps in the dashboard. Start early, because approval takes time.
Step 3: Make sure your business information is complete
AI-drafted replies use the same knowledge as calls and chat, so accurate hours, prices, and policies produce better drafts.
Step 4: Decide who watches the inbox
Even with Booking by text on, texts the AI can't handle and customers who ask for a person wait for your team, so assign someone to check texts at set times. Use the Unread filter to see what's waiting.
Step 5: Publish your number for texting
Tell customers they can text you, on your website, receipts, and signage.
Step 6: Decide how texts get booked
Turn on Booking by text in Booking setup if you want the AI to book, move, and cancel appointments by text. If you leave it off, prepare a short reply that invites texting customers to call or use website chat when they want to book.
Common mistakes with business texting
Expecting texting to run itself
In Aiva Chat, the AI only replies to texts once you turn on Booking by text, and even then it hands some texts to your team. Businesses that enable texting and never check the inbox leave those customers waiting longer than voicemail would. Assign ownership before you advertise the number.
Settling times by hand over text
With Booking by text off, texting can't book or reschedule, and long back-and-forth threads trying to settle a time frustrate everyone. Turn Booking by text on, or move booking to a call or website chat quickly.
Sending walls of text
Detailed policies don't read well on a phone screen. Keep replies short and link to a page or offer a call for anything long.
Skipping registration
Unregistered US business texting can be filtered or blocked by carriers. Complete A2P 10DLC registration before relying on texting.
Treating SMS as a replacement for the widget
Each channel reaches different customers. Dropping the widget for texting loses visitors who want instant answers and online booking.
Best practices for business SMS
- Check the inbox on a schedule. Several fixed times a day beats "whenever."
- Use suggested replies, then edit. Drafts save time; your edit keeps them accurate.
- Keep messages short. One question, one answer.
- Let the AI book by text, or move booking to calls or chat. Don't negotiate times by hand over text.
- Respect opt-outs. Aiva Chat handles STOP automatically; don't work around it.
- Advertise that you text. Customers won't text a number they think is voice-only.
Conclusion
Our judgement is that texting earns its place for one reason: it reaches people a widget can't, including customers on basic phones, those who never visit your site, and those who can't chat in real time. No improvement to the widget closes that gap.
The decision point is staffing. In Aiva Chat the AI can handle appointment texts once you turn on Booking by text, but other texts and hand-offs still need a person, so texting only helps if someone owns the inbox at set times. Advertise your number for texting without that, and you've built a slower voicemail.
As a next step, ask your front desk how many customers already text your number, and who's answering them today.
Ready to reach customers on every channel?
Start with the texts you already get. Connect your Twilio number during the 14-day trial (no card needed), let a week of customer texts land in the shared inbox, and try Suggest a reply on each one before sending. If you're in the US, begin your A2P 10DLC registration on day one, since approval takes time.
Every plan includes texting, voice, and chat; Starter is $49 a month, with Twilio and OpenAI billing your own accounts. Call +1 (970) 972-0974 to hear the voice side.
Start your free trial, or book a demo to plan who watches the inbox and when.
Posts from the people building Aiva Chat in Rajkot — how the product works, what we have learned building it, and guides for getting the most out of an AI receptionist.