FLATWHITE AI · HOSPITALITY AUTOMATION & INTELLIGENCE

One day. Many possibilities.

Concrete situations. Traceable sources. People who decide. Explore possible workflows using entirely synthetic data.

A DAY AT THE HOTEL

One message.
A whole hotel.

Open a request. Check its sources. Decide what happens next.

Playable examples. Fictional data.
REQUESTS01—06

Systems lend a hand. Your team stays responsible.

Explore the architecture
THE HANDOVER

One guest request. A considered draft.

  1. Task
  2. Plan
  3. Sources
  4. Approval
  5. Outcome
Front deskREQUEST / 01
RECEIVED · EXAMPLE

“We arrive late on Saturday and are bringing our dog. Is late check-in possible? And could we use the spa?”

THE PLAN

Identify the requests, consult approved arrival and pet policies, flag the spa question and prepare a reply for reception to review.

THE KNOWLEDGE BEHIND IT
Check-in policy v3 · approvedPet policy v2 · approvedSpa FAQ v2 · approved
REPLY / ACTION · DRAFTReview required

Thank you for your message. We will be happy to coordinate late check-in with reception. We have noted your request to bring your dog and your interest in the spa. Our team will personally confirm the arrival instructions, applicable conditions and spa availability.

The exact arrival time, pet conditions for this reservation and available spa appointments are unconfirmed. No commitment is made.
The draft is ready. Your team decides what happens next.
REFERENCE WORKFLOWREAD → DRAFT → APPROVE
authorized_event → validate_scope → approved_knowledge
skill: prepare-guest-reply
sources: demo-doc-0-0, demo-doc-0-1, demo-doc-0-2
policy: minimum_data · role_scoped · no_pii_logs
action: draft_only → human_approval → simulated_result
guards: idempotency · bounded_retry · timeout_handoff
trace: demo-reception-001 · source_version=3

Reference architecture. No connection to live hotel systems.

A spa request. An honest answer.

  1. Task
  2. Plan
  3. Sources
  4. Approval
  5. Outcome
Concierge & spaREQUEST / 02
RECEIVED · EXAMPLE

“Which wellness options would suit a quiet afternoon? Could you reserve a treatment for us?”

THE PLAN

Find relevant information in the approved service catalogue, ask for the preferred time and prepare a request for the spa team.

THE KNOWLEDGE BEHIND IT
Spa service catalogue v2 · approvedSpa FAQ v2 · approvedSpa reception handover · workflow v1
REPLY / ACTION · DRAFTReview required

We would be happy to introduce our approved wellness options. Which afternoon are you considering, and for how many people? Our spa team will then check suitable appointments and confirm the services and prices. No reservation has been made yet.

Appointment availability, individual suitability and current prices are unverified. The assistant does not provide medical advice.
The draft is ready. Your team decides what happens next.
REFERENCE WORKFLOWREAD → DRAFT → APPROVE
authorized_event → validate_scope → approved_knowledge
skill: prepare-spa-enquiry
sources: demo-doc-1-0, demo-doc-1-1, demo-doc-1-2
policy: minimum_data · role_scoped · no_pii_logs
action: draft_only → human_approval → simulated_result
guards: idempotency · bounded_retry · timeout_handoff
trace: demo-spa-001 · source_version=3

Reference architecture. No connection to live hotel systems.

An observation. A task with an owner.

  1. Task
  2. Plan
  3. Sources
  4. Approval
  5. Outcome
HousekeepingREQUEST / 03
RECEIVED · EXAMPLE

“There is a damp patch in the corridor. Please have it checked and inform the responsible shift.”

THE PLAN

Record the report without guest details, flag its potential safety implications and ask the responsible supervisor to review and assign it immediately.

THE KNOWLEDGE BEHIND IT
Staff report · fictionalHousekeeping SOP v4 · approvedSafety and escalation plan v2 · approved
REPLY / ACTION · DRAFTReview required

Task draft: inspect the damp patch in the corridor. Owner: shift supervisor to confirm. Status: query / urgent human review. Secure the area under the applicable safety procedures; trained staff determine the cause and any further action.

The cause, risk and responsible person are unconfirmed. No automatic technical instruction and no task falsely marked complete.
The draft is ready. Your team decides what happens next.
REFERENCE WORKFLOWREAD → DRAFT → APPROVE
authorized_event → validate_scope → approved_knowledge
skill: create-maintenance-task-draft
sources: demo-doc-2-0, demo-doc-2-1, demo-doc-2-2
policy: minimum_data · role_scoped · no_pii_logs
action: draft_only → human_approval → simulated_result
guards: idempotency · bounded_retry · timeout_handoff
trace: demo-housekeeping-001 · source_version=3

Reference architecture. No connection to live hotel systems.

Many booking channels. A shared foundation.

  1. Task
  2. Plan
  3. Sources
  4. Approval
  5. Outcome
ReservationsREQUEST / 04
RECEIVED · EXAMPLE

“How do direct bookings and OTA bookings compare over the last completed reporting period?”

THE PLAN

Combine approved exports for the same period, verify definitions and currencies, and keep missing commission data visible.

THE KNOWLEDGE BEHIND IT
Example PMS export · fictionalChannel mapping v1 · approvedMetric glossary v2 · approved
REPLY / ACTION · DRAFTReview required

Report draft: direct and OTA bookings are listed separately for a common reporting period. Missing commissions and unreconciled cancellations are flagged. A reliable net comparison requires these data to be completed and reviewed.

Commission data in this example are incomplete. No net-revenue figure is invented and no rate change is made.
The draft is ready. Your team decides what happens next.
REFERENCE WORKFLOWREAD → DRAFT → APPROVE
authorized_event → validate_scope → approved_knowledge
skill: summarize-channel-performance
sources: demo-doc-3-0, demo-doc-3-1, demo-doc-3-2
policy: minimum_data · role_scoped · no_pii_logs
action: draft_only → human_approval → simulated_result
guards: idempotency · bounded_retry · timeout_handoff
trace: demo-revenue-001 · source_version=3

Reference architecture. No connection to live hotel systems.

A campaign. Traceable attribution.

  1. Task
  2. Plan
  3. Sources
  4. Approval
  5. Outcome
MarketingREQUEST / 05
RECEIVED · EXAMPLE

“Which enquiries and bookings can we actually attribute to our last campaign?”

THE PLAN

Match approved campaign and UTM data to confirmed bookings. Separate measured attribution, estimates and missing data.

THE KNOWLEDGE BEHIND IT
Example campaign export · fictionalUTM convention v1 · approvedAttribution rules v2 · approved
REPLY / ACTION · DRAFTReview required

Analysis draft: bookings with confirmed attribution are listed separately. Visits without a reliable booking link remain unattributed. No ROAS is claimed for incomplete channels. Suggestions for the next report are ready for review.

Not every visit can be linked to a booking. Consent gaps and missing channel data limit the conclusions.
The draft is ready. Your team decides what happens next.
REFERENCE WORKFLOWREAD → DRAFT → APPROVE
authorized_event → validate_scope → approved_knowledge
skill: prepare-campaign-brief
sources: demo-doc-4-0, demo-doc-4-1, demo-doc-4-2
policy: minimum_data · role_scoped · no_pii_logs
action: draft_only → human_approval → simulated_result
guards: idempotency · bounded_retry · timeout_handoff
trace: demo-marketing-001 · source_version=3

Reference architecture. No connection to live hotel systems.

One morning. What matters in view.

  1. Task
  2. Plan
  3. Sources
  4. Approval
  5. Outcome
ManagementREQUEST / 06
RECEIVED · EXAMPLE

“What needs our attention today — across arrivals, open tasks and distribution?”

THE PLAN

Read approved daily summaries and task records, check freshness and completeness, and summarise the most relevant items with sources.

THE KNOWLEDGE BEHIND IT
PMS daily overview · fictional example dayOpen tasks · fictionalChannel report · last confirmed update
REPLY / ACTION · DRAFTReview required

Daily brief draft: arrivals need a coordinated handover. One open operations report awaits human review. The channel report is not current, so it is not interpreted as today’s trend. Management should confirm ownership and next steps.

Not every source is current. Missing information remains explicit; no live figures are simulated.
The draft is ready. Your team decides what happens next.
REFERENCE WORKFLOWREAD → DRAFT → APPROVE
authorized_event → validate_scope → approved_knowledge
skill: prepare-daily-hotel-brief
sources: demo-doc-5-0, demo-doc-5-1, demo-doc-5-2
policy: minimum_data · role_scoped · no_pii_logs
action: draft_only → human_approval → simulated_result
guards: idempotency · bounded_retry · timeout_handoff
trace: demo-brief-001 · source_version=3

Reference architecture. No connection to live hotel systems.

All actions are simulated. No messages are sent and no hotel data is changed.

Every workflow.
A clear purpose.

Concept examples for a future pilot. The actual scope depends on your hotel, data and approvals.

Guests & communication

One guest request. A considered draft.

A reviewable reply and three open questions for reception. Your team decides what goes to the guest.

Sources and oversight

Identify the requests, consult approved arrival and pet policies, flag the spa question and prepare a reply for reception to review.

The exact arrival time, pet conditions for this reservation and available spa appointments are unconfirmed. No commitment is made.

  • Check-in policy v3 · approved
  • Pet policy v2 · approved
  • Spa FAQ v2 · approved
Spa, dining & events

A spa request. An honest answer.

A useful reply grounded in approved hotel knowledge; the spa team handles the actual booking.

Sources and oversight

Find relevant information in the approved service catalogue, ask for the preferred time and prepare a request for the spa team.

Appointment availability, individual suitability and current prices are unverified. The assistant does not provide medical advice.

  • Spa service catalogue v2 · approved
  • Spa FAQ v2 · approved
  • Spa reception handover · workflow v1
Hotel operations

An observation. A task with an owner.

A traceable report with priority and handover. The supervisor confirms ownership and action; completion is recorded.

Sources and oversight

Record the report without guest details, flag its potential safety implications and ask the responsible supervisor to review and assign it immediately.

The cause, risk and responsible person are unconfirmed. No automatic technical instruction and no task falsely marked complete.

  • Staff report · fictional
  • Housekeeping SOP v4 · approved
  • Safety and escalation plan v2 · approved
Bookings & revenue

Many booking channels. A shared foundation.

Comparable data with visible gaps and sources, ready for the revenue team’s assessment.

Sources and oversight

Combine approved exports for the same period, verify definitions and currencies, and keep missing commission data visible.

Commission data in this example are incomplete. No net-revenue figure is invented and no rate change is made.

  • Example PMS export · fictional
  • Channel mapping v1 · approved
  • Metric glossary v2 · approved
Marketing & reputation

A campaign. Traceable attribution.

An honest campaign overview with supporting sources and open questions. Your team retains budget and publication decisions.

Sources and oversight

Match approved campaign and UTM data to confirmed bookings. Separate measured attribution, estimates and missing data.

Not every visit can be linked to a booking. Consent gaps and missing channel data limit the conclusions.

  • Example campaign export · fictional
  • UTM convention v1 · approved
  • Attribution rules v2 · approved
Management & reporting

One morning. What matters in view.

A concise, source-backed overview in place of disconnected lists. Management prioritises the next steps.

Sources and oversight

Read approved daily summaries and task records, check freshness and completeness, and summarise the most relevant items with sources.

Not every source is current. Missing information remains explicit; no live figures are simulated.

  • PMS daily overview · fictional example day
  • Open tasks · fictional
  • Channel report · last confirmed update
03 / THE PEOPLE IN YOUR HOTEL

Every shift.
Well supported.

Six roles for everyday hotel work. Together, we define what gets prepared and who approves it.

Guest services

Finds the answer.
Names the source.

Arrival, dining, spa: approved answers to the questions your guests ask.

What can be prepared

  • Answer FAQs with sources
  • Structure service requests
  • Hand over to staff

Confirmed knowledge only. No invented availability or medical advice.

Front office

One message.
A thoughtful draft.

Organise the request, check permitted context and prepare a reply for the front desk.

What can be prepared

  • Identify requests
  • Check permitted booking context
  • Prepare multilingual drafts

A staff member reviews the content, conditions and sending channel before any message.

Housekeeping & maintenance

An observation
becomes a task.

Ownership, priority and feedback stay with the task.

What can be prepared

  • Prepare task drafts
  • Suggest the responsible team
  • Summarise handovers

A supervisor confirms tasks. Hazards and critical repairs are escalated to trained people.

Sales & events

A proposal.
Ready for review.

MICE enquiries become structured proposal drafts. Your team confirms the terms.

What can be prepared

  • Structure an event brief
  • Find approved packages
  • Prepare a proposal draft

The responsible team confirms prices, room availability and binding offers.

Marketing & management

Sourced numbers.
Visible gaps.

Bring campaigns, channels and reviews together. Make missing data explicit.

What can be prepared

  • Prepare campaign reports
  • Group review themes
  • Identify sources and gaps

No unsupported attribution. Copy, budgets and external publication require approval.

Team & standards

The right guidance.
For the right role.

Staff find current standards with a document, a version and an access check.

What can be prepared

  • Explain SOPs with sources
  • Check document versions
  • Flag knowledge gaps

Role-based access. No unrelated HR or finance data; outdated rules are not presented as current.

Concept examples for individually developed solutions. No already-connected agent platform.

LET’S TALK ABOUT YOUR HOTEL

Where does your
time go?

Tell us about the task that keeps your team busy every day.

YOUR
PROJECT