Hi {GuestFirstName}! Wedding update from Rosa & Ben - our website is live with the schedule, hotel block and everything else you'll need: {Link:wedding-website}
Almost every couple ends up sending the same four texts - a details drop months out, week-of logistics, day-before and day-of notes, and the post-wedding photo share - so start with those moments: every template below covers one of them, with a live segment count so you know exactly how it lands.
The first working text most guests get, and the easiest place to start: the website, the hotel block, and how to plan travel - one decision per message, link at the end.
Hi {GuestFirstName}! Wedding update from Rosa & Ben - our website is live with the schedule, hotel block and everything else you'll need: {Link:wedding-website}
Quick one from Maya & Sam - our hotel block at the Fairview releases March 1. Book here: {Link:hotel-block}
Dear {GuestFirstName}, travel details for Amara & Theo's wedding are now available, including flights, shuttles and accommodations: {Link:travel-details}
{GuestFirstName}! Fair warning: we're stealing you for a whole weekend 🎉 Rooms, rides and the full plan: {Link:wedding-website}
Hi {GuestFirstName} - a note while you plan: the dress code for our June wedding is garden formal. Outfit ideas and the full schedule are here: {Link:wedding-website}
The free planner takes your wedding date and turns these into a dated send schedule - every text token-ready and segment-counted before it goes anywhere.
Timing, parking and weather - the questions every guest texts you at 11pm on Thursday, answered before they ask.
Hi {GuestFirstName} - it's wedding week! Three quick things: 1. Ceremony doors open 3:30pm Saturday 2. Free parking in the north lot 3. Forecast says sun, but the lawn is soft - flat shoes welcome Everything else: {Link:week-of-details}
Saturday logistics: park at the mill lot, shuttles run 3-4pm and again after the last dance. Map: {Link:shuttle-map}
Dear {GuestFirstName}, a reminder for Saturday: guests are seated from half past three, and the ceremony begins promptly at four o'clock.
Weather check ☀️ Saturday looks perfect, but if the sky argues, everything moves indoors at the same times. We'll text you either way!
Hi {GuestFirstName} - if {PartyMembers} would like seats on the 3pm shuttle from the hotel, just reply SHUTTLE and we'll save them for you.
Short, single-purpose sends: where to be, when doors open, and where the party moves next. If it matters in the moment, it should fit one screen.
Hi {GuestFirstName} - tomorrow's the day! Doors open 3:30pm at the Willow Barn, and we start at 4pm sharp. Sleep well - see you there.
Today! Willow Barn, doors 3:30pm, ceremony 4pm. Map and parking: {Link:directions}
Good morning {GuestFirstName}. We look forward to seeing you today: guests are seated from 3:30pm, and the ceremony begins at 4pm. Directions: {Link:directions}
IT'S TODAY, people! Doors 3:30, vows 4:00, dinner at 6, dancing till late. Pace yourselves accordingly. Map: {Link:directions}
Ceremony's done - we're married! The party continues at the Harbor House from 6pm. Shuttle leaves the village green at 5:30: {Link:reception-map}
The wrap-up ideas guests love best: photos, farewells, and the blazer somebody left on a chair. These are the texts that extend the weekend by a week.
Hi {GuestFirstName} - thank you for celebrating with us! The first photos are up, and we'd love to see yours too: {Link:photo-album}
Our photographer's gallery is live - and the album has a spot for your pictures from the weekend too: {Link:photo-album}
Lost property report 🕵️ One navy blazer, two phone chargers and a single gold earring survived the dance floor. Yours? Reply and we'll get it home.
Dear {GuestFirstName}, before you travel: farewell brunch is served from ten until noon in the Garden Room. We would love to see {PartyMembers} once more.
Safe travels home, {GuestFirstName}! Having {PartyMembers} with us made the whole weekend. Photos to follow soon - watch this space.
Every template above follows the same five habits. Keep them when you edit the wording into your own voice.
Most guests don't have your number saved. Until they do, every opening text names who it's from - 'Wedding update from Rosa & Ben' - or it reads as spam and gets deleted.
Hotel block is one text. Dress code is another. A message that asks guests to do three things gets zero of them done - which is why the templates are grouped by moment, not stuffed into one announcement.
The first line should make sense on a lock screen with everything else cut off. Put the one fact first and the link last, where a thumb expects it.
Day-of and urgent texts should fit a single SMS segment - 160 GSM-7 characters - so nothing arrives split or out of order. That's what the live counter under every template is for.
The {GuestFirstName}-style placeholders in these templates are real merge tokens that resolve per guest when you send through a tool that supports them. Fill-in-the-blank [Name] templates mean hand-editing 140 texts.
None of these are etiquette crimes - they're delivery crimes. Each one makes the next text you send less likely to be read.
Five separate topics in one message means four of them get skimmed. If the rundown genuinely needs a list, keep it to three numbered lines and push the rest to a link.
Excitement is not an excuse to beat a guest's alarm clock. Keep sends between 9am and 9pm in the guest's own time zone - a scheduled send exists precisely so you can write it at midnight and send it at ten.
The classic group-text fail: 'Hi [Name]!' arriving verbatim on 140 phones. If your sending tool can't resolve a placeholder, delete it and write around it instead.
Out-of-town guests need the hotel block; local guests don't. Brunch invitees need the brunch text; everyone else is just confused by it. Scope each send to the guests it actually applies to - a text that clearly wasn't meant for everyone reads like it was meant for no one.
The text's job is to move a guest to the answer, not to be the answer. If you're pasting the schedule into SMS, the message has taken over the website's job - and it will split into five segments doing it.
Pick a tone and the library re-words itself. Then add your wedding date on the full planner and each text gets an exact send date.
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.
You can, but a group text shows every guest each other's numbers and every 'Congrats!!' reply lands on all of them. Copy buttons here are for pasting into individual threads or a sending tool that texts each guest separately - which is also what makes the merge tokens resolve.
They're merge tokens - placeholders that resolve to each guest's own details when the message sends through a tool that supports them. The templates use exactly six: {GuestFirstName}, {GuestLastName}, {HouseholdName}, {PartyMembers}, {{rsvpLink}} and {Link:...} short links. If you're texting by hand, replace them with the real names before you send.
SMS bills and delivers in segments: 160 characters for plain GSM-7 text, but only 70 once a single emoji flips the message to UCS-2 encoding - and long messages split into parts of 153 or 67. A text that silently arrives as three fragments is the most common wedding-text fail, so each template carries a live count measured the way carriers actually count.
Match the couple, not the occasion. Warm suits most couples for most moments; brief is best for pure logistics like parking; formal fits black-tie weddings and older guest lists; playful works when it sounds like how you already text. Whatever you pick, stay consistent - guests notice when the voice changes mid-planning.
No - those four moments have their own dedicated guides on this site, with wording written for their specific rules: sending wedding invitations by text, save-the-date text messages, RSVP reminder texts, and thank-you note wording. This page covers everything in between - the logistics, updates and celebration texts that carry your guests from the details drop to the photo share.
Five to seven across the whole engagement is the sweet spot - roughly one per moment on this page, plus your own must-haves. Fewer and guests miss logistics; many more and you train them to skim. The free planner computes the exact count and dates from your wedding date.
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.