How to Tell Guests Your Wedding Shuttle Times

# How to Tell Guests Wedding Shuttle Times (So They Make the Bus)

The shuttle leaves the hotel lobby at 3:45 PM. Your guests think it leaves "around 4." Three of them are still at the pool, two are looking for the exact pickup spot, and one wrote the time on a cocktail napkin that is now in the trash. The bus pulls away with empty seats, and a handful of people you flew across the world to be there are now figuring out a taxi in a country where they do not speak the language.

The fix is not a fancier sign in the lobby. It is putting the exact time, the exact spot, and a clear "be there by" instruction directly into each guest's hand, on the device they actually check, at the moment it matters. This guide gives you the wording, the timing, and the small details that decide whether everyone makes the bus.

How do I make sure guests actually know the shuttle time?

Send the shuttle time as a text, not just on the website or a welcome bag card. Include three things every time: the departure time, the exact pickup spot, and a "be there 10 minutes early" buffer. Texts are read within minutes by nearly everyone, so a message sent the morning of reaches people where they already are.

A wedding website is a one-time read. Guests look at it once or twice while planning, then forget the URL. By the wedding weekend it is not open on anyone's phone. A printed itinerary in the welcome bag is lovely and worth doing, but it lives in a hotel room while your guest is standing in a lobby wondering where the bus is.

Text is different. Studies commonly cite SMS open rates around 98 percent, with most messages read within minutes, compared to roughly 20 percent for email. That gap is the whole reason a shuttle reminder works as a text and fails as an email. If you want the deeper logic on why texting beats every other channel for the wedding weekend, I wrote about it in wedding guest communication without an app.

What exactly should a shuttle text say?

A good shuttle text answers four questions in one glance: when, where, what to do, and what happens if you miss it. Keep it to a few short lines. Put the time first, name the pickup spot precisely, add a buffer, and tell people how to reach you. No paragraph, no decoration, just the facts a half-distracted guest needs.

Here is wording you can copy and adapt. Each one assumes the guest already knows it is your wedding, so you can skip the long intro.

The day-before heads up:

Hi! Quick logistics for tomorrow. The shuttle to the ceremony leaves the Hotel Pienza lobby at 3:45 PM sharp. Please be in the lobby by 3:35. It is about a 20 minute ride. Text us back if you have any questions. See you there.

The morning-of reminder:

Good morning! Today is the day. Shuttle to the venue departs the lobby at 3:45 PM, so plan to be down by 3:35. Look for the white van with the "Carmela & Jacob" sign. Can't wait to celebrate with you.

The return shuttle:

Last call info: return shuttles to the hotel leave the venue at 10:30 PM and again at 11:45 PM (the last one). If you miss both, find us or the venue host and we will sort out a ride. Thank you for being here tonight.

The "running behind" variant, for the morning of, when there is a delay:

Heads up, the shuttle is running about 15 minutes late. New departure is 4:00 PM from the lobby. No rush, you have not missed it. We will be right here.

The morning-of message is the highest-attention moment of the entire weekend, so it is the one to get exactly right. For more on building out the full set of wedding-day texts, see wedding-day guest communication and the wedding-day timeline communication guide.

When should I send each shuttle message?

Send shuttle details in three waves: once in the welcome message a day or two before, once the night before with the next-day plan, and once the morning of, two to three hours before departure. The morning-of text is the one people act on. The earlier ones set expectations so nobody is surprised.

Here is a simple schedule you can lift directly.

Across the whole experience, roughly five to seven messages keeps guests informed without making them feel nagged. Shuttle reminders fit naturally inside that count alongside the welcome text and the thank-you note. If you want to plan the full cadence, when to send wedding text messages walks through the timing of every message, and wedding itinerary text wording covers the broader weekend schedule.

How do shuttle times work for a destination wedding across time zones?

At a destination wedding, send shuttle times in local time, spelled out, and time each reminder to land at the right local hour for guests who are physically there. A guest who landed yesterday is on local time. The cost of getting this wrong is not a late arrival, it is a guest stranded in a foreign country, on the wrong shuttle, in the wrong time zone.

Two practical rules. First, always write the time zone or anchor it to the venue: "3:45 PM local time, lobby of Hotel Pienza." Do not assume everyone's phone has switched over, and do not make people do mental math. Second, your reminders need to fire on local time, not on your home time zone. If you are scheduling a batch of texts from back home, a morning-of reminder set for 9 AM your time could hit a guest's phone at 3 AM where they are sleeping.

This is exactly the kind of detail that gets messy when you are managing it by hand from a group chat. Phone group chats also cap out around 20 to 25 people, trigger reply-all chaos, and expose everyone's number to strangers, which is the last thing you want for a guest list. For a fuller destination playbook, see destination wedding guest coordination and how to tell guests about a destination wedding. If guests still need flight and hotel logistics too, wedding guest flight and hotel info by text pairs well with shuttle messaging.

How do I reach guests who never check the website or reply?

Reach the non-repliers by texting them directly. A text does not require anyone to open an app, log in, or remember a link. It arrives on the phone they are already holding. For the handful who never confirm, a short morning-of text with a clear pickup spot is the single most reliable way to get them on the bus.

You do not need read receipts or a head count to make this work. You need the message to actually land. That is the quiet problem with destination weddings: the people most likely to miss the shuttle are exactly the ones who skim the website and never reply, and a text is the one thing that still reaches them. If you are also chasing confirmations, the wedding RSVP reminder templates and how to RSVP by text posts give you wording for that, and destination RSVP deadlines run earlier than you might expect, often 8 to 10 weeks out, because guests are booking flights and your final headcount drives shuttle vehicle size.

The part where the message has to actually arrive

Everything above assumes the text gets delivered. For a local wedding, you can send these from your own phone, and that is genuinely fine. The trouble starts when guests are abroad and your numbers need to cross borders, switch time zones, and land reliably for every single person, including the relative on a foreign SIM card.

This is where I built Dearest Guest. You write your shuttle messages once and schedule the whole timeline, the welcome text, the night-before plan, the morning-of reminder, the return-shuttle note, and each one sends at the right local time for your guests. There is no app for them to download. It is a normal text on their own phone. Messages reach guests anywhere in the world, which is the natural fit for a destination wedding. You can edit, add, or cancel any message right up until it sends, with no per-message fees, so a 15-minute shuttle delay is a quick edit, not a problem.

The piece I care most about is delivery. Some couples came to us after trying other wedding-texting apps where messages quietly did not arrive, and at a destination wedding a text that does not land can strand someone overseas. Every message is human-reviewed, and we actively monitor delivery so messages do not silently fail. We guarantee your messages get delivered. Ilayda reviews every one, and support is one message away. Reply forwarding means a guest's "where's the bus?" comes straight back to you, so you are never out of the loop.

If you want the mechanics, how it works walks through setup, pricing is simple at 3 dollars per guest one time, and destination weddings covers the international side in detail. If you would rather assemble it yourself, the wedding text message templates library has a starting point for every message, and destination wedding welcome text samples and destination wedding travel reminder texts cover the messages that surround your shuttle notes.

A quick shuttle checklist before you finalize

Run through this before the weekend, whether you send by hand or schedule it.

1. Confirm exact times with the shuttle company in writing. Departure and return, every run.
2. Name the pickup spot precisely. "Lobby of Hotel Pienza," not "the hotel." Add what the vehicle looks like if you can.
3. Build in a 10-minute buffer. Tell guests to be there early, then the driver leaves on your real time.
4. Set reminders to local time. Especially the morning-of one. This is the message people act on.
5. Plan for the late guest. A return-shuttle "if you miss both, find us" line prevents the end-of-night stranding.
6. Give one reply-to contact. A number guests can text back, so questions reach a human, not a void.

Venue-specific logistics vary, so if you are planning in one of the popular destinations, the Italy destination wedding guide, Mexico destination wedding guide, and Tahiti destination wedding guide cover transport realities region by region. And once everyone is safely on the bus and the day is done, collecting wedding photos from guests is a nice way to close the loop.

Frequently Asked Questions

How far in advance should I tell guests the shuttle time?

Give them the time in three waves: in a welcome text two days before, in the night-before plan, and again the morning of about two to three hours before departure. The earlier sends set expectations so nobody is caught off guard, and the morning-of text is the one people actually act on to make the bus.

Should I put shuttle times on the wedding website or just text them?

Do both, but rely on the text. Guests view a wedding website once or twice while planning, then forget the URL, so by the weekend it is not open on anyone's phone. A text reaches them where they already are, which is why printed cards and websites are nice backups but a morning-of text is what fills the seats.

What should I do if the shuttle is running late?

Send a short text the moment you know, with the new departure time and a calm "you have not missed it" line. If you scheduled your messages through a tool that lets you edit right up until send, you can update the reminder instead of sending a confusing second message. Always give guests one number to text back so questions reach a person.

How do I handle shuttle times for guests in different time zones?

Always write the time in the venue's local time and anchor it to a place, like "3:45 PM local, lobby of Hotel Pienza." More importantly, make sure your reminders fire on local time, not your home time zone, so a morning-of text does not land at 3 AM for a guest who is already at the destination. This is the most common destination slip-up.

Can I send wedding shuttle texts without making guests download an app?

Yes. The whole point of texting is that it works on the phone every guest already has, with no app, login, or link to remember. With Dearest Guest you write the messages once, schedule the full shuttle timeline to send at the right local time, and they arrive as normal texts anywhere in the world.

How many total messages should I send my guests?

Roughly five to seven messages across the entire experience keeps guests informed without feeling nagged. Shuttle reminders fit inside that count alongside the welcome text, the night-before plan, and the thank-you note. The goal is one clear message at each moment that matters, not a steady stream of pings.