KB Draft: Signals and Journeys for Booking Conversion

Draft status: KB draft created from the Refuge Bay onboarding questions. Review with Product/CS before publishing.

How Yada identifies conversion opportunities, triggers follow-up, recommends next actions, and supports availability-based messaging.

What Yada Can Detect

Yada Signals can detect availability and intent patterns such as unbooked weekends, gap nights between bookings, seasonal return opportunities, local past guests near available inventory, and guidebook activity like early check-in, late checkout, transport, or check-in card views.

These signals are based on real calendar, stay, contact, and guidebook data rather than fake scarcity counters.

Follow-Up Automation

Signals can generate suggested outreach, while Journeys can automate timed messages across the guest lifecycle.

Journey templates include upsells for early check-in, late checkout, pre-stay night extensions, and post-stay night extensions. Journey execution checks availability before sending availability-dependent messages.

Booking.com-Style Urgency

Yada can message around real scarcity, such as a specific weekend being open, a gap night that could be filled, or a guest viewing an intent-heavy guidebook card.

Yada should not show claims like active viewers or artificial limited-availability pressure unless that data is actually captured and available for the property.

Alternate Accommodations and Add-Ons

Yada can recommend follow-up based on known listings, availability, guest history, and Signals. Add-ons such as early check-in, late checkout, transport, and loyalty rewards can be handled as Journeys, Offers, Tasks, or manual Opportunities depending on the workflow.

If a guest reply shows interest, Yada can promote that response into an Opportunity for the team to work.