Launch your first flow

Aurelia works best when the assistant is launched from the exact moments where guests hesitate: the homepage hero, destination browse, hotel detail, and booking handoff.

Teams designing the first end-to-end guest journey.7 min

This page covers

Homepage and hero entry pointsLet guests start in natural language before they know a destination or hotel name.Prompt launchers and hotel-aware actionsOpen the assistant with prefilled intent or a pinned hotel context.CMS and no-code triggersSupport marketing and content teams without forcing custom page JavaScript for every prompt.Keep page context accurateAurelia gets better when the page tells it what the guest is currently seeing.

Page details

Audience

Teams designing the first end-to-end guest journey.

Read time

7 min

Focus

Open Aurelia from hero search, hotel cards, or CMS-managed prompts and keep the page context aligned.

Homepage and hero entry points

Let guests start in natural language before they know a destination or hotel name.

The homepage is where Aurelia earns its place. Guests often know the occasion, the pace, or the type of trip before they know the destination. The first flow should therefore start with natural-language trip planning rather than forcing filters too early.

Use one primary search input with suggested prompts that reflect real guest language.
Route submitted hero prompts directly into the assistant instead of dropping guests into a dead-end search result page.
Preserve the brand journey by keeping the assistant visually integrated with the existing site experience.

Prompt launchers and hotel-aware actions

Open the assistant with prefilled intent or a pinned hotel context.

The prototype already includes a reusable launcher component for product-owned entry points. Use prompt launchers wherever a guest is likely to ask for fit, room advice, dining context, or a clean path into rates.

Launch Aurelia with an optional prompt and pinned hotel context.

import { ConciergeLauncher } from "@/components/concierge-embed";

<ConciergeLauncher
  label="Tell me why this fits"
  prompt="Tell me why The Mark fits a celebration stay."
  pinnedHotelSlug="united-states/mark"
/>;

Use pinned hotel prompts on hotel detail pages when the user is already deep in evaluation mode.
Use broad prompts on homepage and destination pages where the task is still trip planning.
Keep prompts short, literal, and guest-shaped so they feel native to the page instead of synthetic.

CMS and no-code triggers

Support marketing and content teams without forcing custom page JavaScript for every prompt.

Aurelia should not require an engineering release every time a content team wants to place a prompt on a destination module or hotel card. The prototype exposes a data-attribute trigger surface for exactly that use case.

Open the assistant from CMS-managed markup.

<button
  data-concierge-action="prompt"
  data-concierge-prompt="Can this hotel handle our celebration trip?"
  data-concierge-hotel="united-states/mark"
>
  Ask Aurelia
</button>

Why this matters for hotel groups

Hospitality teams frequently iterate on campaigns, landing pages, and seasonal merchandising. A data-attribute launcher makes Aurelia easier to place inside those surfaces without multiplying implementation overhead.

Keep page context accurate

Aurelia gets better when the page tells it what the guest is currently seeing.

Set page type
Distinguish homepage, destination, hotel, booking, and generic docs or marketing contexts.
Pass visible hotels
On browse pages, share the visible hotel set so shortlist and compare answers stay grounded to what the guest can actually see.
Pin the active hotel
On hotel pages, carry the current hotel slug into the conversation so follow-up questions remain specific.
Track active section
Dining, accommodations, and location sections should bias the prompt suggestions and answer shape.

PreviousInstallation NextWhat Aurelia does