UAE · ENBook a demo
HotelDesignAssistant

Booking Journey Design Agent

Designs the screens and flows of the booking engine, guest app and pre-arrival journey.

Booking Journey Design AgentProduct Design Agent · Product Experience
Industry
Hotel
Department
Design
Team
Product Experience
Kind
Assistant
Approver
Guest Journey Product Owner
Code
DSN-01

It turns a guest-journey brief, such as a room-and-rate selection change, an upsell step or mobile check-in, into a user flow and screen specifications built from the hotel group's design system, covering every state and breakpoint. It places the screens as a draft page in the design workspace, linked to the story, with the open questions for the guest-journey product owner.

How it works

6 steps, and a person signs off before step 6.

  1. 01Looks it up

    Finds the record the request is about in the product backlog: the guest-journey story, its acceptance criteria, linked designs and the current booking engine screens for the stage named..

  2. 02Reads the request

    Works out what is being asked and what a complete answer needs.

  3. 03Checks the facts

    Checks figures, dates and rules against the source records, not from memory.

  4. 04Works it through

    Prepares the draft, match, recommendation or reply, with its sources.

  5. 05Asks a person

    Hands the work to Guest Journey Product Owner with its reasoning before anything goes out.

  6. 06Acts

    Once approved, it acts in the design workspace: it creates the flow and screen frames as a draft page in the booking engine design file, linked to the story. and records what was done.

What it works with

Your knowledge, your systems, your people.

Knows

The guest-journey design guidelines: the design system's components, the booking engine's room, rate plan and add-on patterns, how taxes, fees and cancellation terms must be shown, breakpoints and the approved booking copy.

Reads from

the product backlog: the guest-journey story, its acceptance criteria, linked designs and the current booking engine screens for the stage named.

Acts in

the design workspace: it creates the flow and screen frames as a draft page in the booking engine design file, linked to the story.

Hands back

An object with flow (a list of steps, each with step, screen, guest_action and next), screens (a list, each with name, purpose, components, states (empty, loading, sold_out, error, success, each a sentence or null) and breakpoint_notes), price_display (one sentence on how rate, taxes, fees and cancellation terms appear), new_components (a list, each with name and why), personal_data (a list of fields with their reason) and open_questions (a list).

Asks a person when

The flow touches one of payment, stored cards, marketing consent, loyalty account deletion, ID or passport capture, hides a mandatory fee from the first price shown, or runs longer than 4 steps from search to confirmation.

ApproverGuest Journey Product Owner

Settings

Your limits, set by your managers.

SettingDefaultWhat it controls
Most steps from search to confirmation4A booking flow with more steps than this is flagged with a shorter alternative.
Show the total stay price including taxes and feesOnWhen on, every rate shown includes mandatory taxes and fees, with the breakdown one tap away.
Card entry only in the hosted payment fieldOnWhen on, no screen collects card numbers outside the payment provider's hosted field, keeping the flow out of PCI DSS scope.
Breakpoints to design for (px)360, 768, 1280Comma-separated viewport widths each booking engine screen is specified at.
Flows that need the approverpayment, stored cards, marketing consent, loyalty account deletion, ID or passport captureComma-separated. A flow touching any of these goes to the approver before it is placed.

Limits are settings, not code: a manager changes them without a developer.

Rules it always follows

  • Build every screen from the design system's booking components and list anything missing as a proposed new component, never as a one-off.
  • When on is true, every rate shows the total for the stay with tourism tax and mandatory fees included, and the cancellation terms sit next to the price, never behind a link only.
  • Count the steps from search to confirmation; a flow longer than 4 steps is flagged with a shorter alternative.
  • When on is true, card data is entered only in the hosted payment field and never shown, stored or typed elsewhere in the flow.
  • Marketing consent is a separate, unticked choice and never bundled with the booking terms.
  • Specify every web screen at each width in 360, 768, 1280, and the empty, loading, sold-out and error state of every availability or payment screen.
  • A flow touching payment, stored cards, marketing consent, loyalty account deletion, ID or passport capture goes to the Guest Journey Product Owner before it is placed.

See the Booking Journey Design Agent agent on your own work.

We’ll run it on a sample of your work and show you what your approver would see.

Booking Journey Design Agent · Hotel | Basinwright Industries