Hi {GuestFirstName}! we here - we're getting married on the big day in town. Save the date; your invitation will follow soon.
Most couples land on five to seven texts across the whole engagement - a first announcement around eight months out, a details drop, a reply nudge, the wedding-week logistics, and a photo share after. Enter your date and the planner turns that consensus into a dated send plan, every message token-ready with a live segment count.
Hi {GuestFirstName}! we here - we're getting married on the big day in town. Save the date; your invitation will follow soon.
Hi {GuestFirstName} - our wedding website is up! Schedule, hotel block, and everything for the big day lives here: {Link:wedding-website}
Hi {GuestFirstName} - we're finalizing numbers for the big day and would love to know if {PartyMembers} can make it. RSVP here: {{rsvpLink}}
Hi {GuestFirstName} - one week to go! Parking, timing and the forecast for the big day are all here: {Link:week-of-details}
Hi {GuestFirstName} - tomorrow's the day! Ceremony at the venue: doors from 3:30pm, and we begin at 4pm sharp. Sleep well!
It's today, {GuestFirstName}! One last note: the venue, doors 3:30pm. Directions and parking: {Link:directions}. See you soon!
Hi {GuestFirstName} - thank you for celebrating with us! The first photos are up, and we'd love yours too: {Link:photo-album}
Private by design: this planner runs entirely on this page — nothing you enter leaves your browser. Your names, date and venue only fill in the preview above, and they're gone when you close the tab.
Nobody needs another list of 27 templates. You need to know which texts to send, on which dates, to which guests — so that's what the planner computes.
Wedding date, single day or whole weekend, and the tone you'd actually text in. That's everything the plan needs.
Seven or eight sends anchored to your date — from the first text about eight months out to the photo share the week after — each with its audience and a live segment count.
Copy any message, or the whole plan in one click. When you're ready, Text My Wedding schedules every send and resolves the tokens per guest.
The question every couple asks before the first send, answered by the plan itself: it's almost never the count that annoys guests - it's the calendar and the scoping. Five habits keep your wedding guest message plan welcome in every thread.
Across planners, vendors and couples, the settled range is five to seven texts over the whole engagement - roughly one per moment in the library below. The planner defaults to that range: seven sends for a single-day wedding, eight for a full weekend.
Months apart early, then closer together as the day approaches: one text around eight months out, one around four, then everything else packed into the final six weeks. Guests read cadence as care when it tracks what they need to do next.
Week-of logistics, the day-before reminder and the morning-of note all land inside seven days. That's not too many - it's the one stretch of the wedding week message schedule where guests want more texts, not fewer.
The blast that gets you muted is the one that clearly wasn't for the person reading it. Scope each send - hotel-block guests, weekend guests, the not-yet-replied - and even eight texts read as exactly enough.
Keep every send between 9am and 9pm in the guest's own time zone. A scheduled send exists precisely so you can write the text at midnight and have it arrive at ten.
If you've been searching for the best wedding text message planner — or a custom or personalized one — here is the honest version: deterministic scheduling plus real merge tokens, so what you copy still works when it actually sends.
A custom plan starts from your date, your venue and your event shape — not a generic checklist. Switch the tone and all seven or eight messages re-word themselves, still anchored to your calendar.
Every message carries real merge tokens —{GuestFirstName}, {PartyMembers} — that resolve differently for every household, so 140 guests each get their own text, not a blast. See how in our guide to personalizing wedding guest texts.
The planner runs entirely on this page: nothing you enter leaves your browser. Your names, date and venue fill in the preview above and disappear when you close the tab.
The first thing most guests hear from you by text: the date exists, the city is chosen, clear the calendar. One fact, warmly delivered - the paper and the website come later.
Hi {GuestFirstName}! It's Nadia & Cole - we're getting married! June 12 next year, in Asheville. Hold the date for us; everything else will follow soon.
{GuestFirstName} - news from June & Wes: we're getting married October 9 in Sedona. Clear the date. More soon.
Dear {GuestFirstName}, Carmen & Leo are delighted to share that they will be married on the fourth of September in Savannah. A formal invitation will follow.
🎉 {GuestFirstName}! Tess & Omar are getting MARRIED. May 22, Lake Tahoe. Clear the whole weekend - details to come!
One more thing from Nadia & Cole, {GuestFirstName} - we're making a whole weekend of it, Friday welcome drinks through Sunday brunch, and {PartyMembers} are invited to all of it. Details soon!
Enter your wedding date in the planner above and this library becomes a dated schedule - seven or eight sends, each one token-ready and segment-counted before it goes anywhere.
Where the plan earns its keep: the website goes live, the room block opens, and the reply window opens and closes. One decision per text, link at the end.
Hi {GuestFirstName} - everything for October 9 now lives in one place: schedule, hotels, dress code and the good parking. {Link:wedding-website}
Heads up from Carmen & Leo - our room block at the Grove Inn releases July 1. Book yours: {Link:room-block}
Dear {GuestFirstName}, for guests travelling to Savannah: flight guidance, the shuttle schedule and accommodations are now available here: {Link:travel}
Hi {GuestFirstName} - invitations are officially in the mail! When yours arrives, you can reply in about a minute right from your phone: {{rsvpLink}}
{GuestFirstName}! Six weeks out and the seating chart waits for no one 👀 Can {PartyMembers} make it? {{rsvpLink}}
Half the plan lands in this one week, and that's how guests want it: logistics while there's still time to act, a day-before reminder, and a morning-of note that fits one screen.
Hi {GuestFirstName} - it's wedding week! The short version: Saturday at Hazel Hall, doors 4pm Shuttles leave the Grove Inn at 3:15 Warm evening, ceremony on the lawn The long version: {Link:week-of}
Saturday: self-park on Mill St or ride the 3:15 shuttle from the inn. Doors 4pm. Map: {Link:map}
Quick note from Tess & Omar - Saturday's ceremony is on grass and the evening cools off fast, so flat shoes and a layer are a good idea. Everything else: {Link:week-of}
Dear {GuestFirstName}, we look forward to seeing you tomorrow. Guests are seated from half past three, and the ceremony begins promptly at four. Warmly, Carmen & Leo.
IT'S TODAY, {GuestFirstName}! 🥂 Hazel Hall, doors 4pm, vows 4:30. Map: {Link:map}. Bring the dance moves.
The plan's last anchor sits about a week after the day: photos gathered, thank-yous on their way, and one good sign-off before the thread goes quiet.
Hi {GuestFirstName} - we're married! Thank you for being part of it. The first photos are up, and there's a spot in the album for yours too: {Link:album}
Photo drop: the gallery from Saturday is live, and it has room for yours. {Link:album}
Dear {GuestFirstName}, thank you for celebrating with us. Having {PartyMembers} there meant more than we can say - written notes are on their way to you.
Breaking news from Tess & Omar: there is leftover cake and we are not sharing. Thank you for the best day of our lives - more soon!
One last one from Nadia & Cole - safe travels home, {GuestFirstName}. Thank you for making the weekend what it was. Photos and proper thank-yous to follow!
The planner computes the schedule; these guides resolve the judgment calls — what's rude, what splits into three segments, and what to say when the venue changes with guests already in the car.
Five to seven across the whole engagement is the cross-source consensus, and it's what this planner defaults to: seven dated sends for a single-day wedding, eight for a weekend. And when couples worry about sending too many, the real culprit is almost never the total - it's an unscoped blast that clearly wasn't meant for the guest reading it. Scope each send to the guests it applies to and the count takes care of itself.
Anchor everything to the wedding date: the first text around eight months out, the details drop around four months, a reply nudge six weeks out, then week-of logistics, a day-before reminder, a morning-of note, and a photo share about a week after. Enter your date in the planner and those anchors become real calendar dates you can schedule.
No - and that's deliberate. The planner is deterministic: the same inputs always produce the same plan, computed entirely in your browser. The {GuestFirstName}-style merge tokens are a closed vocabulary, and a language model will happily invent {GuestName} or [Name] variants that never resolve - silently breaking the one thing that makes these messages sendable. If you want AI phrasing, rewrite a planner message in your own tools, but keep the tokens exactly as they are.
Completely free, with no sign-up and no limit on rebuilding the plan. We built it to introduce you to Text My Wedding, the app that can schedule and send the plan for you - but copying every message out by hand costs nothing and always will.
No. The planner runs entirely on this page - nothing you enter leaves your browser. Your names, wedding date, venue and city exist only to fill in the preview, and they're gone the moment you close the tab.
They're merge tokens - placeholders that resolve to each guest's own details when the message sends through a tool that supports them. The planner uses exactly six: {GuestFirstName}, {GuestLastName}, {HouseholdName}, {PartyMembers}, {{rsvpLink}} and {Link:...} short links. If you're texting by hand, swap in the real names before you hit send.
It places them on the calendar - the opening text sits about eight months out and the reply nudge six weeks out - but each of those four moments has its own dedicated guide on this site, with wording written for its specific rules. Use the planner for the schedule and the in-between texts, and the dedicated guides when you're writing those four.
The planner plans; sending is what the Text My Wedding app does. Create a free account, add your guests, and the same seven or eight messages become scheduled sends - each one personalized per guest, delivered on its date between reasonable hours, with the replies collected for you.
Writing one of the four texts this planner only schedules? Each has its own guide: sending wedding invitations by text, save-the-date text messages, RSVP reminder texts and thank-you note wording. And when you'd rather we do the sending, see everything you can send with Text My Wedding.
Planning the rest of the wedding too? Build the day's schedule with the free wedding timeline generator, write your promises with the wedding vow generator, and thank everyone afterwards with the wedding thank-you note generator — all free, and all running the same private, in-your-browser way as this planner. And when it's time to word the invitation itself, the wedding invitation wording generator handles hosting lines, formality and the details card.
Text My Wedding schedules every send on its date, resolves the merge tokens per guest, and collects the replies — so seven or eight dated texts never have to leave your notes app by hand.