Useful guides.
Visible evidence.
Hospitality AI Playbooks is an independent directory sponsored by Ferociter. Sponsorship does not imply endorsement by a featured creator or platform.
What the labels mean
- Practitioner report: a named creator publicly described the workflow. Results are their claims, not our benchmark.
- Vendor example: a first-party vendor describes a capability or customer application. We have not independently reproduced it.
- Editorial adaptation: an original implementation idea supported by documentation or a broader example, rather than an exact reported deployment.
- User-supplied report: material provided to the editor whose original author or URL is not yet verified. Any reported savings are anecdotal.
What we add
Prompts, input checklists, setup steps, review requirements, and success measures are original editorial suggestions. We distinguish these additions from source claims. We do not claim that a prompt is tested, an integration is native, or a financial result is guaranteed unless evidence explicitly establishes it.
Dates, access, and updates
The launch edition was reviewed on October 11, 2026. X sources were added on October 12, 2026. This is a manually maintained library. Some X posts are visible through indexed excerpts while direct access may require a login. Connections, subscription features, prices, and source pages can change.
Privacy & local features
Search runs in your browser. Saved guides use local browser storage and do not sync across devices. This site has no signup form, tracking pixel, or access to your accounts. Hosting providers handle ordinary request logs. External links lead to other providers; Ferociter forms and services have their own data handling.
Source register
Vendor describes guest answers, translation, service tickets, and staff handoff. Our prompt and review process are editorial additions.
The visible X post reports an agent helping Booking.com accommodation partners respond to guest inquiries. The public embed truncates further details; it does not establish routing features, accuracy, or savings. The prompt and escalation checks here are our editorial additions.
Customer story describes call handling and contextual transfer to staff. Its results are vendor-reported, not an independent benchmark.
Case study describes pre-arrival WhatsApp information and links to hotel services. Our guide does not promise the same results.
Vendor describes digital booking conversations and lead qualification outside office hours. We do not use its ROI claim as a forecast.
Vendor describes response suggestions, translation, sentiment detection, and routing. Human decisions remain part of this editorial workflow.
Product page describes hospitality forecasting and decision support. This guide proposes a manual scenario review, not autonomous rate changes.
Y Combinator describes Conduit agents for leasing, onboarding, scheduling, and retention with human handoff. This service-scheduling checklist is an editorial adaptation of that broader announcement, not a tested Conduit setup or a claim of achieved savings.
The provider describes combining local events, pickup, pricing, and hotel web searches. Our calendar, prompt, and decision checklist are editorial additions; no uplift is promised.
Documentation describes leading and lagging event effects for accommodation. It supports considering surrounding stay nights, not a fixed uplift or guaranteed forecast.
The product documents flight data and configurable alerts. It does not validate our hotel-demand assumptions or identify travelers needing rooms.
The provider identifies airport delays and other events as potential hotel-demand inputs. This guide adds property-specific validation and staff decisions.
OAG describes using flight schedules and capacity for hospitality decisions and a Pestana integration with Power BI. Our weekly review workflow is an editorial adaptation, not a copy of that implementation.