Feature Adoption Agent
Tracks uptake of new features and flags gaps.
- Industry
- Hotel
- Department
- Product
- Team
- Discovery and Delivery
- Kind
- Investigator
- Approver
- Director of Product
- Code
- PRD-10
It tracks uptake of new guest features, such as mobile check-in, digital keys, the pre-arrival upgrade offer or in-app dining orders, and explains why one lags its target. It separates guest causes from hotel ones, such as front desk staff not offering it or a lock system not supported. **The problem it solves:** Why a released guest feature is adopted less than its target: the adoption at each stage, the release date by hotel, the eligible stays, staff and hardware readiness, and the feedback received.
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 guest messaging and CRM platform: feature use per eligible stay by hotel, with PMS check-in records..
- 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 on the feature. and records what was done.
What it works with
Your knowledge, your systems, your people.
Knows
The adoption targets: definitions of adoption per feature, targets, the hotels where each is live and staff training status.
Reads from
the guest messaging and CRM platform: feature use per eligible stay by hotel, with PMS check-in records.
Acts in
the product tracker: it files the diagnosis on the feature.
Hands back
An object with feature, adoption_percent, target_percent, by_hotel (a list), causes (a list, each with cause, evidence and likelihood) and next_steps.
Asks a person when
The diagnosis recommends pulling the feature or retraining a hotel's staff.
Settings
Your limits, set by your managers.
| Setting | Default | What it controls |
|---|---|---|
| Default target (% of eligible stays) | 25 | Target when none is set. |
| Judge after (days) | 45 | Adoption is judged after this. |
| Lag worth explaining (%) | 20 | A shortfall this large is explained. |
| Least eligible stays | 300 | Fewer are not judged. |
Limits are settings, not code: a manager changes them without a developer.
Rules it always follows
- Judge after 45 days against 25 percent unless a target is set.
- Explain a shortfall of 20 percent; need 300 eligible stays.
- Compare hotels: a lag at only some hotels points to staff, training or hardware there.
- Weigh awareness, eligibility, usability and hotel process causes with evidence.
See the Feature Adoption Agent agent on your own work.
We’ll run it on a sample of your work and show you what your approver would see.