# Setting KPIs and governance to track AI performance post-launch
Six months after a hotel chain launches an AI chatbot for guest service, the deflection rate (percentage of queries resolved without a human agent) still looks great on the dashboard: 78%. Nobody notices that guest satisfaction scores for chatbot-handled interactions have quietly dropped from 4.2 to 3.6 out of 5. The model is doing its job on paper. It has stopped doing its job in practice. This is the gap that post-launch governance exists to catch.
Most AI business cases in travel and hospitality are built and approved on a single metric: cost saved or revenue lifted. That number gets the project funded. It rarely tells you whether the tool is still healthy a year later. This lesson covers what to measure instead, and how to organize the governance around it.
Cost-per-interaction or RevPAR (revenue per available room) uplift figures are snapshots taken at launch, often under ideal conditions: clean training data, a motivated pilot team, a narrow set of guest queries or booking patterns.
Six months on, several things typically drift:
None of this shows up in a static cost-savings figure. You need metrics designed to detect decay, not just confirm the initial win.
Model drift (or model decay) is the decline in a model's predictive accuracy over time as real-world datareal-world dataRWD, données collectées en dehors des essais cliniques contrôlés : dossiers médicaux, claims d'assurance, données de dispositifs connectés, base des Real-World Evidence (RWE). diverges from training data. Two flavors matter:
Track: prediction accuracy against actual outcomes on a rolling basis (weekly or monthly), not just at launch. For a dynamic pricingdynamic pricingAutomatically adjusting prices in real time based on demand, competition or user behaviour to optimise revenue, margin or conversion.Voir la définition complète → or demand-forecasting model, compare forecast versus actual occupancy or fare fill rate. A hotel revenue team might set a threshold: if forecast error (mean absolute percentage error, MAPE) rises above 8 to 10% for three consecutive weeks, trigger a model review. These thresholds are illustrative; each property or airline route network needs to calibrate its own baseline.
Deflection rate and average handling time measure efficiency. They say nothing about whether the guest actually got what they needed. Pair them with:
Airlines using AI for rebooking during disruptions (a real use case at carriers like Delta and Lufthansa) should watch NPSNPSNet Promoter Score (NPS) measures customer loyalty by asking how likely customers are to recommend a brand, then subtracting detractors from promoters.Voir la définition complète → (Net Promoter ScoreNet Promoter ScoreNet Promoter Score (NPS) measures customer loyalty by asking how likely customers are to recommend a brand, then subtracting detractors from promoters.Voir la définition complète →, a loyalty metric based on likelihood to recommend) specifically for AI-assisted rebookings versus agent-assisted ones. If the gap widens, that is a governance signal, not a footnote.
A tool nobody uses generates zero ROIROIReturn on Investment: the ratio of net profit to the cost of an investment. A 300% ROI means each dollar invested returns $3.Voir la définition complète → regardless of how accurate it is.
Especially relevant for pricing and recommendation models. Dynamic pricingDynamic pricingAutomatically adjusting prices in real time based on demand, competition or user behaviour to optimise revenue, margin or conversion.Voir la définition complète → tools should be periodically audited to confirm they are not producing systematically different outcomes for comparable guests based on protected characteristics or proxies for them (device type correlating with income, for instance). This is both a governance and, increasingly in the EU, a regulatory concern under the EU AI Act framework for high-risk systems, and worth documenting even where a system isn't formally classified as high-risk.
You don't need a 40-person AI ethics board to govern a hotel chatbot. You need three things:
1. A named owner. Someone (often a product or operations lead, not just IT) accountable for the tool's performance after launch, not just its delivery.
2. A review cadence. Monthly for high-traffic tools (booking assistants, dynamic pricingdynamic pricingAutomatically adjusting prices in real time based on demand, competition or user behaviour to optimise revenue, margin or conversion.Voir la définition complète →), quarterly for lower-stakes ones (back-office document processing).
3. A pre-agreed trigger list. Specific thresholds that automatically prompt a review or rollback, decided *before* launch, not debated under pressure when something breaks.
Example trigger list for an airline's AI-based rebooking assistant:
Metric Threshold Action
--------------------------------------------------------------------
CSAT (AI-handled rebookings) < 3.5 / 5, 2 wks Flag for review
Escalation rate > 35% Flag for review
Forecast/actual fare deviation > 12% MAPE, 4 wks Model retrain review
Staff override rate +15pp vs baseline Trust auditThis is a governance artifact, not a technical spec. It should live in a shared document that operations, IT, and finance all sign off on, and it should be revisited every 6 to 12 months as the tool matures.
Vérification des acquis
1. In the hotel chatbot example, the deflection rate stayed high while guest satisfaction declined. What does this scenario primarily illustrate?
2. Why do cost-per-interaction or revenue-uplift figures calculated at launch tend to become poor indicators of AI performance over time?
3. A hotel's PMS undergoes a major upgrade, changing the data format feeding an AI recommendation engine. From a governance perspective, what is the most important implication?
4. Select ALL correct answers about factors that can cause AI performance to 'drift' after launch, according to the lesson.
Sélectionnez toutes les réponses correctes.
5. Select ALL correct answers about why a single launch-time business case metric is insufficient for long-term AI governance.
Sélectionnez toutes les réponses correctes.
Take the hotel chatbot from the opening scene. At launch, the business case assumed:
Monthly saving estimate: 7,800 queries deflected × ($4 − $0.50) = $27,300/month saved.
That number alone still looks good at month six. But now layer in the quality signal: CSATCSATCustomer Satisfaction Score, a direct measure of satisfaction captured right after a specific interaction or experience, usually on a short rating scale.Voir la définition complète → for AI-handled queries has dropped from 4.2 to 3.6, and internal data shows guests with a bad AI experience are 20% more likely to leave a negative online review, which correlates with measurable booking loss in comparable published hospitality studies (see Cornell's Center for Hospitality Research for related methodology on review sentiment and revenue). If even a fraction of that 78% deflected volume is now generating detractors, the "savings" are partly offset by reputational cost that never appears in the original ROIROIReturn on Investment: the ratio of net profit to the cost of an investment. A 300% ROI means each dollar invested returns $3.Voir la définition complète → model.
The governance lesson: cost savings and experience quality must be reported side by side, every review cycle, not as separate dashboards owned by separate teams.
🎬 [VIDEO: "How Airlines Use AI for Customer Service and Disruption Management" - youtube.com - search for recent airline AI ops case studies covering real-time rebooking and chatbot performance monitoring]