Every few months someone asks us, gently, why we still invest engineering time in SMS. It's not the interesting channel. Voice has the latency numbers. The web widget has the design work. SMS is text messages — a technology old enough that most of our engineers were in school when it was already ubiquitous. The honest answer is that SMS reaches people the other two channels structurally cannot, and that gap doesn't close no matter how good the widget gets.
What a chat widget actually requires
A web widget is a great channel — for a customer who is, right now, on your website, holding a device with a modern browser and a working data connection, willing to stay on that page long enough to type. That's a real customer. It's also a narrower slice of your actual customer base than it feels like from inside a product team that spends all day looking at widget conversations.
It excludes the customer who found you through a friend's phone number, not your website. The customer whose data plan runs out before the end of the month. The customer on a basic phone, not a smartphone, who represents a real and current share of the population in the markets we serve. The customer who has your number saved from a previous visit and would rather text than navigate back to a site and wait for a widget to load. None of these people are edge cases. They're a normal customer, just not one who happens to be looking at a browser tab right now.
What SMS doesn't need to work
It's worth listing what SMS doesn't require, because the list is short and that's the entire point. No app to download. No account to create. No browser, no JavaScript, no CSS rendering correctly on whatever device someone happens to be holding. No data connection at all, in the strict sense — SMS rides on the same basic signaling channel as a phone call, which is why it still gets through in situations where a data-dependent widget wouldn't even finish loading. A customer needs exactly one thing to reach a business over SMS: a phone number that can send and receive text messages, which describes essentially every mobile phone in use, new or decades old.
That's a meaningfully lower bar than "modern smartphone with a working data plan and a browser that renders correctly," and the gap between those two bars is where a real, non-trivial share of customers live — particularly outside the biggest cities, where feature phones and patchy data are still an everyday reality rather than an exception, a pattern TRAI's own subscriber data has tracked for years.
Async isn't a downgrade
There's a related assumption worth pushing back on: that SMS is the fallback channel, the one you use when the "real" channels aren't available. We don't think that's right either.
A customer mid-shift at work, or mid-errand, or just not in a position to sit and type back and forth in real time, isn't poorly served by SMS — they're well served by it. They can read a text between meetings and reply an hour later without losing anything, because the conversation is still exactly where they left it when they come back. A live chat widget open in a background tab doesn't offer that; if they close the tab, the context is gone, or at best buried in an email transcript nobody rereads. SMS is asynchronous by nature, and for a lot of real customer situations, asynchronous is simply the correct shape for the conversation, not a compromise. AIVA's SMS engine is built specifically to pick a thread back up correctly no matter how long the gap between messages runs — the async nature only pays off if the system on the other end actually remembers.
The customer who isn't on your website right now isn't a lost customer. They're a customer on a different channel, and SMS is often the only one that reaches them.
What SMS honestly gives up
None of this is a case for SMS over everything else, and it's worth being direct about what it costs. A text thread can't show a live calendar the way a widget can — a customer choosing between three appointment slots is working from words, not a visual grid, which is a real disadvantage for anything genuinely spatial or visual, like browsing photos of a salon's work or comparing product images. There's no button to tap, no rich card to glance at — every interaction has to resolve into something that reads clearly as text. And a long, detailed policy explanation that a widget can format with line breaks and headings turns into a wall of text on SMS that most customers won't read closely.
That's why SMS isn't positioned as a replacement for the widget or for voice — it's a third channel with its own shape, good at some things and genuinely worse at others. A business relying on SMS alone would lose the customers who want to browse visually before they ask a question. A business relying on the widget alone loses everyone SMS reaches instead. The reason AIVA runs all three isn't redundancy; it's that no single channel covers the actual range of how customers prefer to get in touch. Where SMS is unambiguously better is anything time-bound and low-effort to act on — a booking confirmation or an appointment reminder a customer can reply to in five words from wherever they are, which is a big part of why reminders sent by text hold up better than a reminder phone call that has to be answered live or gets lost to voicemail.
The reach argument, plainly
We keep coming back to a simple test: does this channel work for a customer holding any phone, on any network, at any moment, without asking them to be somewhere specific first? Voice comes close — it needs a working call, nothing else. SMS matches it — no app, no browser, no data connection required, just a text. A web widget, by definition, needs the customer to already be exactly where the business wants them, doing exactly what the business wants them to do.
That's not an argument against the widget. It's excellent at what it's built for — a visitor with intent, already on the page, one question away from converting, and AIVA's web widget is built to earn that moment well. It's an argument against treating SMS as a secondary channel because it's the oldest one. The reason it's still here, on every phone, unchanged for two decades, is that it never depended on any of the things that make the newer channels fragile. That's not nostalgia. That's reach nothing else has matched yet.
Why we built it this way from the start
This is also why SMS was never designed as a bolt-on notification system sitting apart from "the real product." It runs on the same conversation engine as voice and the web widget, understands plain language and a handful of shorthand commands like STATUS and RESCHEDULE, and carries the same context whether a booking started on a call, on the website, or in the text thread itself. We've written about why we built voice first, SMS second, and the widget third — SMS earned its place in that order specifically because of the reach argument above, not because it was the easiest thing left to build.
The businesses that get the most value from AIVA aren't choosing one channel and ignoring the rest. They're letting customers show up wherever they already are — a call, a text, or a widget — and trusting that whichever one a customer picks, the conversation on the other end is exactly as capable.