Why We Built WedLoop on SMS (and Why More Apps Should Follow)

This past year I've been to a lot of weddings — some as a guest, some in the wedding party. And every single time, the weeks leading up to the event felt the same: I had no idea what I was supposed to be doing. The save-the-date had arrived eight months earlier and was long gone. The wedding website URL? Also gone. So I did what everyone does — I texted the bride or groom. Sometimes weeks out, sometimes the morning of. And I'd later learn I was one of many guests doing the exact same thing.

Then I got married. I was determined not to let it happen to my guests. I put every detail on the wedding website, set up a custom domain that was easy to remember, wedding.slapelis.com, printed a QR code on the save-the-date — everything I could think of to make the information impossible to lose. My guests still did exactly what I had done at every other wedding. They texted us.

That pattern stuck with me. When people actually need an answer about an event — the kind of answer they need now, not eventually — they don't open an app. They don't search their physical mail. They don't dig through their inbox. They text someone.

When we started building WedLoop, we took that seriously.

The easy path we didn't take

The default move would have been to build another app. Or a guest-facing web portal with accounts, passwords, and a dashboard full of wedding details. We could have made it beautiful. That's kind of our thing.

But smartphones have been around for almost two decades now. Everyone's home screen is already full. Nowadays, everyone has too many logins, too many notifications, too many apps they opened once and never again. Asking someone to create an account to attend your cousin's wedding is asking them to care about your software more than they care about the event itself. They don't, and they shouldn't.

So we asked a different question: where do people already want to communicate about things that matter to them?

The channel signals the message

Here's something I've come to believe: the channel you communicate on signals how much you respect someone's attention.

Email has become the equivalent of physical mail — mostly promotions, mostly ignored, mostly skimmed in bulk. When a brand emails you, the implicit message is "we'd like something from you, when you get around to it." That's fine for newsletters. It's a terrible fit for "the shuttle leaves in 20 minutes."

SMS is different. SMS is where your mom texts you, where your group chat plans dinner, where your partner sends the grocery list. It's the channel reserved for people and information that actually matter. When your phone buzzes with a text, you look.

Most companies that do use SMS have squandered this. They blast promotional codes and shipping updates and "WE MISS YOU" (the feeling isn't mutual) messages until users reflexively tune them out. But that's a choice, not a property of the medium. SMS done well isn't marketing — it's utility.

The obvious objections

You can't just start sending SMS programmatically in the U.S. There are laws and regulations around it — which, in my opinion, haven't kept up with how the world actually works. Before you can text anyone, you need documented consent. With a provider like Twilio, you submit your opt-in flow for carrier review, iterate until it's approved, and even then the whole process feels more bureaucratic than it should. It's genuinely harder than spinning up a web app or an email list. But that friction on the sender side is exactly what keeps the channel valuable on the receiver side. If SMS were as cheap and frictionless as email, it would look like email — and your inbox already tells you how that ends.

"Why not WhatsApp or iMessage for Business?" WhatsApp is great for some markets — we're adding international support now — but in the U.S. the common denominator is still SMS. Every phone has it. No app to install, no platform to opt into. Universality wins for event communication, where your guest list spans generations and tech comfort levels. iMessage for Business has a different problem: it only lets the user initiate contact with the business. That's a dealbreaker for us. Half of what WedLoop does is outbound — the initial invitation, date reminders, the occasional blast a wedding planner needs to send. A channel where we can't text first isn't a channel we can build on.

"Isn't rich formatting a dealbreaker?" Sometimes. But events aren't Notion docs. "Ceremony at 4, black tie, shuttles at 3:15" doesn't need formatting. And when something richer is needed, a link in a text works fine.

What this means beyond weddings

Weddings made the case obvious to us because they're emotional, time-sensitive, and involve people who may or may not know each other well but need to coordinate. But the same properties show up in plenty of other places. A small clinic reminding a patient about tomorrow's appointment is time-sensitive and personal. A local school letting parents know practice is cancelled can't afford to land in a promotions tab. A community organization rallying volunteers for Saturday morning needs to reach people who care but aren't checking an app. Anywhere a relationship matters more than a funnel, SMS earns its place.

The lesson isn't that every app should use SMS. It's that you shouldn't assume your users want another app, another login, another dashboard, or another notification stream at all. Figure out where your users already are — where they already want to communicate — and meet them there. For WedLoop and our guests, that's SMS. For your product, it might be something else entirely. But it probably isn't wherever is most convenient for you to build.

For us, that meant SMS. I suspect we won't be the last.