Intro
Revenue managers have spent a decade fighting the same fight: protect ADR, hold direct booking share, keep OTA commissions from eating margin. The levers were familiar — rate parity, pricing rules, channel manager discipline, marketing alignment around peak windows.
AI answer engines moved one of the most important levers upstream, and most revenue management teams have not noticed yet.
When a guest now asks ChatGPT, Perplexity, or Google AI Overviews “best 5-star hotel in Marrakech for a long weekend in March”, the engine’s answer determines two things at once: whether the hotel is named at all, and whether the guest is sent toward the hotel’s own domain or toward an OTA listing. That second routing decision quietly sets the channel cost of the booking that follows.
This page explains what revenue managers should measure, what they should do about it, and where it fits in the monthly distribution review.
Score your AI distribution risk
Why AI visibility now touches revenue management
For most premium hotels, three to five engines now sit between intent and booking. The numbers vary by market and segment, but the pattern is consistent: a meaningful share of high-intent travel queries no longer ends on a search results page. It ends inside an AI answer.
Inside that answer, two things matter for the revenue manager.
The first is whether the hotel is mentioned. Absence is the cleanest form of OTA capture: if the engine names two competitors and skips the hotel, the guest will not arrive at all, or will arrive via the OTA that the engine cited as proof.
The second is which domain the engine cites. When the engine recommends the hotel but cites Booking, Expedia, or a meta-search aggregator as the source, the guest follows the cited link. The booking lands in the OTA channel. The hotel pays 15-25% in commission on a guest who, in the previous decade, would likely have arrived direct.
This is why AI visibility is no longer a marketing-only concern. It changes the input distribution that feeds the channel mix downstream. The revenue manager owns the channel mix. Therefore the revenue manager owns part of the AI visibility question.
The rest of this page is the practical version of that statement.
The five metrics to track
A revenue manager does not need eight dimensions. Five are enough to fold into a monthly distribution review.
- Citation share — the percentage of relevant AI prompts where the hotel is named in the answer. Tracked per market, per segment (leisure, MICE, long-stay), per engine. Read like share of voice in distribution: low and falling means future-bookings risk.
- Own-domain citation rate — among the prompts where the hotel is mentioned, the percentage where the engine cites the hotel’s own domain rather than an OTA, meta-search, or third-party listing. This is the cleanest leading indicator of direct booking share three to six months out.
- OTA capture risk — for each market, the share of citations going to Booking, Expedia, and aggregators. High and rising means the hotel is being recommended, but the commission line will absorb the benefit.
- Prompt coverage of high-intent queries — among the queries that historically convert (branded + city + 5-star, “best hotel near X for Y”, peak-season planning queries), how many produce a mention. Coverage gaps on high-intent queries are the highest-cost gaps.
- Fact accuracy — does the engine quote the right ADR positioning, the right room count, the right F&B offer, the right policy on children, pets, late check-out? Wrong facts cost direct bookings even when citation share is good.
Five numbers. One slide in the monthly distribution review.
Five revenue manager actions
The point is not to monitor. The point is to act.
- Add AI citation share to the monthly distribution review. One slide, five metrics, same cadence as channel mix and ADR. Treat it as part of the demand picture, not as a marketing report.
- Flag OTA-capture risk per market. When a market shows rising mentions but falling own-domain citation rate, that is a leading signal that the next quarter’s bookings will shift toward OTAs. Brief the GM and marketing before the shift hits the P&L.
- Test prompts before peak season. Six to eight weeks ahead of the booking window for each peak (Easter, summer, year-end, MICE shoulder), pull the prompt set for that market and check coverage, citation rate, and fact accuracy. Fix what is fixable before demand arrives.
- Coordinate with marketing on prompt set design. The prompt library is co-owned. Marketing knows the messaging. The revenue manager knows which segments and queries actually move revenue. The prompt set is wrong if it is built without revenue management input.
- Tie the verification cycle to commercial milestones. Quarterly retest for stable markets. Pre-peak retest for high-stakes windows. Post-rate-change retest when ADR positioning shifts and the engines need to relearn the brand.
These five actions sit on top of the existing distribution playbook. They do not replace it. They feed it earlier inputs.
When to escalate to marketing
Not every AI visibility problem is a revenue management problem.
Escalate to marketing when:
- Citation share is structurally low across all engines, not just one. That points to a content and authority problem on the hotel’s own properties — direct booking recovery territory.
- Fact accuracy drifts across multiple categories (ADR, amenities, policies, F&B). That points to outdated source content, weak schema, or thin own-domain coverage.
- A competitor consistently wins comparison prompts the hotel should be winning on objective criteria. That is a positioning and proof-points problem, not a pricing problem.
- The hotel is being correctly cited but with OTA URLs only. That is the OTA capture defense playbook, run jointly with marketing and digital.
The revenue manager’s job is to surface the signal early, not to fix the root cause alone. The distribution review is the right venue. The fix lives in marketing, content, and digital.
How this fits into Capston Core
Capston Core is the measurement and playbook layer for premium hospitality. Revenue managers are one of the three primary readers of the output, alongside marketing and ownership.
The metrics on this page come from the Capston Hospitality Scorecard and follow the Capston Core methodology for prompt design, capture, and verification. The escalation paths above connect to the direct booking recovery and OTA capture defense playbooks.
→ Back to Capston Core
FAQ
How often should a revenue manager look at AI citation share?
Monthly, inside the existing distribution review. Pre-peak windows get an extra retest six to eight weeks before the booking curve opens.
Is this not just marketing’s job?
Marketing owns the fix. Revenue management owns the consequence. If the channel mix is shifting toward OTAs because AI engines cite OTA URLs, the commission line shows up in revenue management’s P&L view first.
How is OTA capture risk measured?
Per market, per prompt set: the share of citations pointing to Booking, Expedia, and meta-search aggregators. Read alongside own-domain citation rate. Rising OTA share plus falling own-domain rate is the warning pattern.
What if the hotel has no marketing team large enough to act on the signal?
Then the prompt set, the verification cadence, and the escalation rules need to be written down once and shared with the agency or external partner. The revenue manager remains the signal owner — the execution moves outward.
Final CTA block
Bring AI visibility into your next distribution review.
Score your brand
Read the methodology