Why we built meno to end the RSVP chase
Existing tools send group texts fine. The weekly RSVP chase still meant exports and spreadsheets. We rebuilt that part.
If you plan weddings for a living, you already know guest texting. You have sent save-the-dates, chased RSVPs, and answered late-night "where do we park?" texts. Some of us have years of experience building the apps that do that work. This is why we built meno.
What we kept
Group text messages for weddings work. Guests actually read them. A dedicated wedding number keeps replies off your personal phone. Guest-count pricing (you pay for the list size you already know) is clearer than guessing how many messages you will send. Those parts stay. They were not the problem.
The problem was the weekly RSVP chase. Export the list. Check who answered on the website, in a voice note, or not at all. Build the "hasn't replied" group by hand. Paste. Send. Do it again next week. Across a season, that takes time you would rather spend with couples who still need you.
Why a small fix was not enough
We first tried to keep the send-message flow and add RSVP tracking on the side. That was not enough. The send button worked fine. Tracking who actually replied still lived in a spreadsheet somewhere else.
Most planners we talked to already knew this. They were not asking what guest texting is. They were asking why the reply still lived in another place. If you have a better view of that, we would like to hear it.
What we wanted instead
A guest replies yes or no in the text. That answer saves next to their name. Reminders go only to guests who have not replied. Week-of and day-of messages are scheduled from the wedding date, so you are not rebuilding a calendar every time something changes.
What we built
We made the text reply the RSVP. Yes, no, or still silent, next to each guest. No export step in the middle. Then reminders on a schedule you set once, and they skip anyone who already answered. Parking, itinerary, and day-of updates use the wedding date too.
Each wedding also gets its own local number. Guests reply to it, not to your personal phone late at night. If you still like your current tool for group messages, that is fine. We focused on the RSVP chase.
Where things stand
Group messaging stays familiar. RSVP tracking is built in. Messages are scheduled from the wedding date. If your current tool still makes you export to chase RSVPs, that is the gap meno was built to close. You can also read our comparison with WedTexts and tell us what we got wrong.
If you have never used a wedding texting app, start on the weddings page. If you already use one: you know the job. We built a clearer version.
Written for planners who already know wedding guest-texting tools. We do not name former employers here. The claim is years of experience in the category, not a brand affiliation.