Guests only need the events they're invited to - one text per event, sent to that event's list, never a full-itinerary blast. The sixteen texts below are grouped by event, and each one opens with exactly who should receive it, from the arrival welcome to the farewell brunch.
Who gets it: every guest, on the day they arrive. This is the welcome text - a hello, a thank-you for travelling, and one link that holds the whole weekend. It doesn't restate your website; it proves the channel works before the first real logistics text needs it.
Hi {GuestFirstName}, welcome to Savannah - we're so happy you made the trip! Everything for the weekend, event by event with addresses, is here: {Link:weekend-guide} - Nora & Wes
Welcome! Your welcome bags are at the Grand's front desk under your name. Weekend details: {Link:weekend-guide}
Dear {GuestFirstName}, welcome to Savannah. We are so pleased you have arrived. The weekend's events, with times and addresses for each, may be found here: {Link:weekend-guide}
{GuestFirstName}! You made it 🎉 The best weekend of our lives has officially begun. Times, addresses and where to find coffee: {Link:weekend-guide}
The free planner's multi-event mode builds the weekend version of the send plan - eight dated sends from save-the-date to photo share, including the welcome-drinks text scoped to weekend guests only - each labeled with who gets it, on which day, with a live segment count on every body.
Who gets it: the welcome-party list, and nobody else. If twenty people are invited to Thursday drinks, twenty phones get this text - everyone else never hears about a party they weren't asked to.
Hi {GuestFirstName} - we're kicking the weekend off early with you! Welcome drinks Thursday, 7-9pm on the Harbor House rooftop. Come as you are: {Link:welcome-party}
Tonight: welcome drinks, Harbor House rooftop, 7pm. Casual - come straight from the airport if you have to.
The weekend starts early for you, {GuestFirstName} 🍸 Rooftop drinks at the Harbor House, 7 tonight. First round is on us.
Who gets it: the rehearsal-dinner list only - usually the wedding party, close family, and sometimes every out-of-towner. Same rule as the welcome party: the details go to that list alone, including any ride arrangements.
Dear {GuestFirstName}, a reminder that the rehearsal dinner will be held on Friday at 6pm at Marchetti's, 41 Bay Street. We look forward to the evening with {PartyMembers}.
Rehearsal dinner tonight: Marchetti's, 6pm. A car leaves the Grand lobby at 5:30 - reply CAR if {PartyMembers} need seats.
Hi {GuestFirstName} - Friday night is the small one: dinner with family and the wedding party at Marchetti's, 6pm. Toasts welcome, early night encouraged.
Who gets it: the full guest list - the only texts of the weekend that do. Keep them to doors, start time and rides; the minute-by-minute schedule belongs on your website, not in a text thread.
Hi {GuestFirstName} - the big one's tomorrow! Ceremony at Foxhall Farm, doors open 4pm and we start at 4:30. Staying at the Grand? Shuttles leave at 3:45. See you there!
Shuttle note for today: pickups outside the Grand at 3:30 and 3:50. Doors at Foxhall Farm open 4pm.
Dance floor closes at 11 😢 Return shuttles to the Grand run 9:30, 10:30 and a final boarding call at 11:15 from the front gate.
Who gets it: whoever's invited to brunch - at some weddings that's every guest, at others just family and the hotel block. Scope it like every other event: the invite goes to the brunch list, not the whole thread.
Hi {GuestFirstName} - don't disappear on us! Farewell brunch tomorrow, 10 to noon in the Orangery at the Grand. Come as you are, leave whenever your flight insists.
Brunch is on: the Orangery, 10 to 12. Coffee is already brewing.
Dear {GuestFirstName}, it has been a joy to share this weekend with {PartyMembers}. Should your travels allow, breakfast is served in the Orangery from 10 o'clock until noon.
A wedding weekend is an audience problem, not a wording problem. Five habits keep every guest hearing about exactly their events and nothing else.
Every event gets its own message, sent only to that event's guest list. The moment a text covers two events, someone receiving it isn't invited to one of them - and now you're fielding awkward questions instead of RSVPs.
Guests attending three events over three days can't parse 'Tonight at 7!'. The first line names the event - 'Welcome drinks tonight', 'Rehearsal dinner tonight' - so the text makes sense on a lock screen mid-weekend.
The arrival welcome, the day-before note, and brunch if everyone's invited. Everything else - welcome party, rehearsal dinner, per-hotel shuttles - is a subset send. If you're about to text all 140 guests, check which of the three this is.
'The usual lot' and 'the place on Bay Street' mean nothing to someone who landed two hours ago. Weekend texts carry addresses, pickup points and times as if every reader arrived yesterday - because most of them did.
Each text moves one audience to one event; the full weekend schedule stays on your wedding website behind a single link. A text that tries to be the itinerary splits into five segments and answers nobody's actual question.
Every one of these comes from treating the guest list as one audience when a wedding weekend has four or five of them.
The fastest way to make 120 people feel uninvited to something. Subset events go to subset lists - which means building those lists before wedding week, not scrolling your contacts on Thursday afternoon.
One message covering all five events splits into five-plus segments, arrives as fragments, and still gets you the same questions - because nobody rereads a wall of text to find their shuttle time. Send one text per event instead, each at the moment it's needed.
Locals know the parking situation and how far the venue is from downtown; the aunt who flew in does not. If most of your list is from out of town - the usual case for a full wedding weekend - write every text for the guest who knows nothing.
Guests need doors, start time and their ride - not the minute-by-minute timeline. Build the day-of schedule with the free wedding timeline generator and keep it on your website; if you want a schedule text sent on the morning, that's exactly the kind of send Text My Wedding handles for you.
Enter your wedding date and the planner drafts the weekend send plan - the all-guest anchors plus the welcome-drinks text that goes to weekend guests only, each send labeled with its audience and dated from your day, every body token-ready and segment-counted before you copy it.
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}
Welcome to town, {GuestFirstName}! Join us tonight at 7pm at the venue for welcome drinks - come as you are.
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.
No. Each guest should only ever be texted about events they're invited to - one text per event, at the moment it's useful. The full itinerary lives on your wedding website behind one link in the welcome text, so anyone who wants the overview has it without every phone receiving a five-event wall of text.
Build the per-event lists before wedding week: welcome party, rehearsal dinner, hotel block, brunch. Texting by hand, that means separate individual threads - never a group chat, which exposes numbers and reply-alls everyone. A sending tool with guest groups does the same scoping automatically: you pick the event's group and the text goes only to those guests.
The welcome text lands as guests arrive or on check-in day. Subset events get their details three to five days out, plus a short same-day reminder with the address and time. The day-before note goes to everyone the night before the ceremony, and the brunch reminder lands Sunday morning. The free planner dates the all-guest anchors and the welcome text from your wedding day automatically.
They get exactly three texts: the arrival welcome, the day-before note, and brunch if they're on that list. That's the point of scoping by event - a Saturday-only guest never hears about the rehearsal dinner, so there's nothing to feel excluded from and nothing in their thread that doesn't apply to them.
By text, guests only need doors, start time and their ride - the minute-by-minute run-of-show is a planning document, not a message. Build it with the free wedding timeline generator and publish it on your wedding website. If you do want guests to get a schedule text on the morning, Text My Wedding can schedule and send that for you along with the rest of your weekend plan.
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.
