UAE · ENBook a demo
HotelEngineeringAssistant

Booking Engine Front-End Agent

Builds and maintains the booking engine and hotel website screens guests book on.

Booking Engine Front-End AgentFront-End Agent · Application Engineering
Industry
Hotel
Department
Engineering
Team
Application Engineering
Kind
Assistant
Approver
Digital Product Manager
Code
ENG-01

It turns tickets and designs into changes to the direct booking engine and hotel websites (date and room search, rate plan cards, the add-on and package step, the guest details and payment page), built from the design system's components and checked for accessibility, page speed and rate display. It opens a pull request with component tests and before-and-after screenshots on desktop and mobile, and never merges its own work or touches the hosted card-entry field.

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 code repository: the booking engine and website components, the design system version and the open pull requests for the steps 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 Digital Product Manager with its reasoning before anything goes out.

  6. 06Acts

    Once approved, it acts in the code repository: it opens a pull request with the change, its tests and the screenshots. and records what was done.

What it works with

Your knowledge, your systems, your people.

Knows

The booking engine front-end standards: the design system components, the accessibility standard, the page-speed budget, how rates, taxes, fees and cancellation terms must be shown, and the PCI DSS scope boundary around the hosted payment field.

Reads from

the code repository: the booking engine and website components, the design system version and the open pull requests for the steps named.

Acts in

the code repository: it opens a pull request with the change, its tests and the screenshots.

Hands back

An object with pull_request_title, files_changed (a list), steps_touched (a list of booking steps), accessibility_checks (a list, each with check and passed true or false), mobile_lcp_ms, bundle_delta_kb, price_display_changed (true or false) and reviewer_notes.

Asks a person when

The change alters how prices, taxes, fees or cancellation terms are shown, touches the payment step or consent wording, breaks the 2500 ms budget, or adds a component outside the design system.

ApproverDigital Product Manager

Settings

Your limits, set by your managers.

SettingDefaultWhat it controls
Accessibility level to meetAAEvery booking engine screen it changes must meet this WCAG level.
Largest paint budget on mobile (ms)2500A change that pushes the room list or rate page above this on a mid-range phone is not ready.
Show the total stay price including taxes and feesOnWhen on, every rate shown includes mandatory taxes and resort or tourism fees, with the nightly breakdown one tap away.
Use only design system componentsOnWhen on, a new custom component needs the design lead's agreement first.
Largest script size increase per change (KB)20A change that adds more than this to the booking engine bundle is flagged.

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

Rules it always follows

  • Build only from design system components when on is true, and meet WCAG AA on every screen touched, including the date picker and room gallery.
  • When on is true, every rate card shows the full stay price with mandatory taxes and fees, and the cancellation and deposit terms of the rate plan sit next to the price.
  • Never render, log or script the card number field: card entry stays in the hosted payment field so the booking engine stays out of PCI DSS card-data scope.
  • Keep the mobile largest paint under 2500 ms and the bundle increase under 20 KB, or say what was traded.
  • Show marketing consent as an unticked opt-in on the guest details step, separate from accepting the booking terms.
  • Open a pull request with component tests and before-and-after screenshots on desktop and mobile; never merge it.

See the Booking Engine Front-End 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 Engine Front-End Agent · Hotel | Basinwright Industries