KB Draft: What to Expect During Yada Onboarding

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

A practical onboarding overview for new Yada customers covering data setup, integrations, training, campaigns, Journeys, Signals, Loyalty, and support.

Implementation Phases

• Workspace setup: confirm admin access, users, billing, brand settings, and support contacts.

• PMS setup: connect Hostaway or another supported PMS and verify listing, reservation, contact, and calendar sync.

• Messaging setup: configure the channels that will be used, such as email, SMS, WhatsApp, OpenPhone, or PMS messaging.

• Training setup: review listing details, guidebook content, brand voice, signatures, do-not-say rules, and AI accuracy settings.

• Marketing setup: import historical contacts, segment audiences, create Campaigns, configure Journeys, and turn on Signals review.

• Loyalty setup: configure the loyalty program, points rules, reward options, and guest portal flow where applicable.

How Many Campaigns and Journeys Start Initially

A practical launch should start with a small set of high-confidence workflows: one past-guest campaign or warm-up, the core pre-arrival/post-stay Journeys that fit the property, and a small number of Signals or upsell automations that can be monitored closely.

The exact number should depend on data quality, channel readiness, consent, and how much operational review the team wants at launch.

Customer Time Investment

The largest customer time investment is usually gathering clean historical data, confirming brand/offer rules, reviewing listing content, and approving the first campaigns and journeys.

Yada should do as much configuration as possible with the customer reviewing outputs rather than having the customer build every workflow themselves.

Ongoing Support

Customers should have a named onboarding contact and a recurring working session during launch. For Yada customers, position this as the Marketing Mastermind.

Long-term support should include email support, knowledge base documentation, product walkthroughs, and scheduled strategy sessions when the account is expanding or launching new modules.