txt.wedding

    Wedding website vs. group text vs. mass SMS: which do guests actually see?

    Last updated

    Mass SMS wins for anything time-sensitive. Wedding websites are great reference material but guests rarely return to them after RSVPing. Email gets opened by roughly 20% of recipients. Group texts reach everyone in the thread but cap out around 20 to 32 people, expose every phone number, and generate reply-all noise. Use a website for standing details, and individual text messages for anything that changes.

    Use all three, deliberately

    • Website: the permanent reference. Schedule, dress code, hotel blocks, FAQ. Free with txt.wedding.
    • Email: the long version, sent early, when detail matters more than speed.
    • Text: anything guests need to act on within 48 hours.

    Channel comparison

    ChannelReachBest forFails at
    Mass SMS (individual)Very highDay-of changes, reminders, logisticsLong-form detail
    Wedding websiteLow after RSVPSchedule, travel, registry, FAQAnything urgent
    EmailAbout 20% openedSave-the-dates, long updatesWedding-day reach
    Group textHigh but cappedThe wedding partyLists over ~30, privacy, reply-all
    Social postUnpredictablePhotos afterwardsGuests who aren't on it

    Common questions

    Do I still need a wedding website?

    Yes, for standing information. txt.wedding includes one free at txt.wedding/w/your-names with a guest sign-up form built in.

    Why do so few guests revisit a wedding website?

    Most guests visit once to RSVP or check the date and never return. Anything that changes after that visit needs to be pushed to them, not posted.

    Reach every guest, in minutes

    Free to set up. Free wedding page and guest gallery. $1 per guest to text your list.