Wedding RSVP Text Service: How It Works and What It Costs (2026)

A wedding RSVP text service collects replies where guests already are. How text RSVPs work, per-event responses, reminders, and what the tools cost.

By Mia · 2026-07-20

A wedding RSVP text service is a narrower thing than a general wedding texting tool. The job is not just to broadcast announcements, it is to ask a question and record the answer against the right guest. You send the invitation by text, the guest replies or taps through, and the yes or no lands in your headcount without anyone opening an email or hunting for a reply card. This guide covers how text RSVPs work, why they tend to collect faster than a website RSVP alone, how per-event responses work for a multi-day wedding, and what the tools in this category charge. Pricing is from each company's public pages as of July 2026; check their sites for current numbers.

How an RSVP by text actually works

There are two shapes. The first is reply by keyword: the guest gets a text and answers in the thread, yes or no, or a number for the party size, and the service parses it into the list. Nothing to open, no page to load. The second is link based: the text carries a personalised link, the guest taps it, and a short browser page collects the response along with anything else you need.

Both avoid an app download for guests, which is the point. What makes either one work is that the link or the reply is tied to a specific guest record, so the response files itself. Nobody types their name, nobody guesses which household they belong to, and you are not reconciling a form export against your list afterwards.

Why a text collects RSVPs faster than a website alone

A wedding website RSVP page is a good thing to have, and most couples should still have one. The catch is that it requires the guest to go somewhere. They have to keep the URL, remember it exists, and pick a moment to sit down at it. Email adds another layer, since the invitation has to survive a promotions tab and a week of scrolling.

A text lands in the app the guest already checks, next to messages from their own family, and it can be answered in the ten seconds they are holding the phone anyway. The argument is mechanical rather than promotional: fewer steps between the ask and the answer means more answers. Relatives who will never open the wedding website will still read a text.

Per-event RSVPs for a multi-day wedding

One yes or no stops being useful the moment the wedding is more than a single event. A welcome dinner for out of town guests, a ceremony for everyone, a smaller brunch the next morning: each of those is its own headcount, and a guest coming to two of them is not simply attending.

A per-event RSVP asks the question once per function that guest is actually invited to, so the reply comes back as a set of answers rather than one. Catering numbers then read straight off it, per event, and they move as replies land. This applies to any multi-day wedding, and it is the norm for South Asian weddings where four or five functions across a week is ordinary. Not every text service does this; several collect one attendance answer for the whole wedding.

Reminders to non-responders only, and dietary capture

Collecting the first wave of replies is the easy half. The rest is following up, and this is where a tool that tracks RSVPs separates from one that only broadcasts. If the same system holds the list and the responses, a reminder can go to non-responders only, so the eighty people who already answered are not texted again about something they have done. Guests notice that, and it is the main reason a reminder reads as helpful rather than repetitive.

The same logic covers the fields that belong alongside the yes. Meal choice, dietary notes, plus ones and children, arrival day. Capturing those at the moment of the RSVP is much less work than a second round of messages later asking who eats what.

The tools in and around this category

A few tools sit squarely in this category.

• Replied is the most RSVP-first of the group. The whole product is guests replying by text: reminders to non-responders, meal choice up to three options, and household counting, so a party of five costs one RSVP. It lists $9.99 one-time per event with 25 text RSVPs included. That base pool is small for a wedding list and the expansion pricing is not published, so price yours first.
• WedTexts is worth naming mainly to rule out: it prices by guest count with unlimited messages and a real free tier up to 15 guests, but it is one-way broadcast by design and does not collect replies.
• Text My Wedding sells buckets of texts from $57 for 500, adding two-way replies and a guest photo stream at the $87 tier.
• txt.wedding charges a flat $1 per guest and is the only one of these four advertising WhatsApp, though that claim appears only in its homepage copy and not on its pricing or features pages.

Where Cordially Wed fits

Cordially Wed charges nothing for RSVP collection. The guest list with per-event tagging, the per-event RSVP responses, the wedding website, seating charts, and Apple and Google Wallet passes are all free, with no cap on guests or responses. The one paid piece is texting guests, and it is a one-time payment rather than a subscription: $59 for up to 100 unique guest phone numbers, $99 up to 200, $149 up to 400, with unlimited messages and replies included at every tier. Above 400 numbers, get in touch and we will price it.

SMS and WhatsApp send from the same screen, with regional numbers for US, UK and India lists, and replies land in an inbox in the app rather than on your personal phone. Guests need nothing installed; RSVP links open in a browser. Before paying anything you can send real messages to your own phone and see exactly what a guest receives. Start at cordiallywed.com/invite/.