Broadcast

Perfect for urgent updates (elevator outage, Wi-Fi issues, maintenance) or planned announcements (scheduled water shutdown, building works), while still keeping messages personalized.

How to set up a Broadcast Message:

What is Broadcast in Guestway?

Broadcast is built for moments when you need to communicate fast, consistently, and at scale.

Instead of manually searching conversations and sending the same update one-by-one, you create a broadcast once, choose your delivery channels (OTA, Email, SMS — or all three), and target exactly the right guests based on where they’re staying and when they’re staying.

Messages can include template variables (like Guest First Name) so broadcasts still feel personal, even when sent to dozens (or hundreds) of reservations.

---

Common use cases

Immediate incidents (send now)

• Elevator is out of service

• Water leak / maintenance interruption

• Noise works in a specific building

• Wi-Fi outage

• Safety or access instructions

Planned events (schedule ahead)

• Scheduled water shortage next Sunday

• Planned building maintenance for a week

• Preventive reminders for specific check-in cohorts

---

How it works

1) Create a broadcast

• Give it a clear internal name (e.g., “Complex X — Elevator Out”)

• Write the message and add personalization variables (e.g., “Hi {{guest_first_name}} …”)

2) Choose your channels

Select at least one:

• OTA

• Email

• SMS (or all three)

3) Target the right guests with filters

You can filter by:

• Currently staying (perfect for real-time incidents)

• Date range targeting (perfect for planned events)

• Listings / complexes (send only to the impacted building(s))

Key logic: you can include or exclude guests based on whether they check in or check out on the selected dates — so you don’t message guests who already left.

---

Example 1 — Elevator outage (send now)

Scenario: This morning you learn the elevator is down in Complex X.

Setup

• Send: Now

• Audience: Currently staying

• Include: Check-ins

• Exclude: Check-outs

• Filter: Complex X / affected listings only

Message sample “Hi {{guest_first_name}}, unfortunately the elevator is currently out of service due to a technical issue. Please don’t use it — our team is handling it today. Thanks for your patience.”

---

Example 2 — Water shortage next Sunday (schedule)

Scenario: You know there will be a water outage on Sunday 21st in Complex X.

Setup

• Send: Scheduled

• Audience: Date range

• Start date: the day you want to begin notifying impacted reservations

• End date: 21st

• Logic: include guests who are staying during that period (include check-ins, exclude check-outs as needed)

• Filter: Complex X / impacted listings

This ensures you notify:

• Guests who will already be in-house

• Guests arriving before the outage …and you avoid guests who have checked out and don’t need the info.

---

Why teams love it

• Speed during incidents: one message, sent everywhere in minutes

• Less noise: only the right guests get the update

• Consistent communication: same wording and instructions across channels

• Personalized at scale: template variables keep it human

• Operational clarity: easy to document what was sent, when, and to whom

If you want, I can also write a tight FAQ section for the page (delivery channels, scheduling, “who receives what,” and best practices for incidents vs planned works).