Booking Funnel Analytics Agent
Tracks booking engine and guest app funnels and repeat-stay retention.
- Industry
- Hotel
- Department
- Product
- Team
- Strategy and Roadmap
- Kind
- Investigator
- Approver
- Director of Product
- Code
- PRD-06
It tracks the booking engine and guest app funnels, from search to room selection to payment, and repeat-stay retention, and explains why a step moved. It separates causes such as a payment gateway problem, a rate not loaded, a tracking break or a channel traffic change. **The problem it solves:** Why the booking or app funnel step or repeat-stay metric moved: the before and after figures, when it started, which hotels, devices and channels are affected, and what changed in releases, rates, payments, tracking or traffic.
How it works
6 steps, and a person signs off before step 6.
- 01Looks it up
Finds the record the request is about in the booking engine: funnel events, payment errors and bookings by step, device and hotel..
- 02Reads the request
Works out what is being asked and what a complete answer needs.
- 03Checks the facts
Checks figures, dates and rules against the source records, not from memory.
- 04Works it through
Weighs competing explanations against the evidence and shows which one holds up.
- 05Asks a person
Hands the work to Director of Product with its reasoning before anything goes out.
- 06Acts
Once approved, it acts in the product tracker: it files the diagnosis and opens a fix item. and records what was done.
What it works with
Your knowledge, your systems, your people.
Knows
The funnel definitions: each step of the booking and app journeys, baselines, the tracking plan and recent releases.
Reads from
the booking engine: funnel events, payment errors and bookings by step, device and hotel.
Acts in
the product tracker: it files the diagnosis and opens a fix item.
Hands back
An object with metric, before, after, change_percent, segments_affected, causes (a list, each with cause, evidence and likelihood) and next_steps.
Asks a person when
A payment or booking step drops 25 percent or more.
Settings
Your limits, set by your managers.
| Setting | Default | What it controls |
|---|---|---|
| Change worth explaining (%) | 10 | Smaller moves are noise. |
| Baseline (weeks) | 4 | Compared with this. |
| Check tracking first | On | When on, tracking is ruled out first. |
| Drop that is urgent (%) | 25 | A payment-step drop this large is urgent. |
Limits are settings, not code: a manager changes them without a developer.
Rules it always follows
- Explain moves of 10 percent against a 4-week baseline.
- Rule out tracking breaks first while on is true.
- A payment-step drop of 25 percent is urgent and goes to the Director of Product.
- Weigh releases, rate availability, payment errors, device and channel mix, with evidence.
See the Booking Funnel Analytics Agent agent on your own work.
We’ll run it on a sample of your work and show you what your approver would see.