The Feature That Serious Scheduling Apps Eventually Build
· 2 min read · By Joel Natkin
Open OpenTable, Calendly, or Mindbody and you’ll find the same small feature tucked in the settings: an automatic reminder that goes out before the appointment. None of them shipped it on day one. They added it later, after watching the same thing happen over and over — people book, people forget, and a forgotten booking is a slot unpaid for.
For a business that sells time, that empty slot is the whole problem. Depending on the industry, somewhere between 15% and 30% of booked appointments turn into no-shows, and each one is staff time, a held room, and a customer who’d have gladly taken the slot if they’d known it had opened up. A reminder is the cheapest thing that keeps it from happening.
But the content matters.
In controlled trials, carefully worded text reminders have cut no-show rates by 30% or more — while others barely move the number at all. Same channel, same timing, completely different result. The message has to do real work: the right tone, the right detail, an easy way to confirm or reschedule. The feature isn’t “send a text.” It’s “send the right text.”
But most apps never make it past that. The harder part by far is everything between your code and the customer’s phone — to send texts from an app at all, you have to register your business with the mobile networks, prove people consented, handle opt-outs, and wait out an opaque approval process that can run for weeks. Most developers start down that road, hit the paperwork, and quietly move the feature to “later.” It never ships.
Which is unfortunate, because the channel itself is remarkably effective when the message is worth reading.
A text lands on the lock screen, gets read in seconds to minutes, and doesn’t have to fight a spam folder or a promotions tab the way an emailed reminder does. For something time-sensitive — “your 2:00 is tomorrow, reply C to confirm” — there’s no better channel.
RelayKit gives you effective message workflows as a starting point, then handles the registration, consent, opt-out, and carrier-review process that often pushes the feature into the backlog.
If your app books time for anyone, this is a feature you’ll eventually want. Might as well be the version that ships.
— Joel