How to Use AI in the Hospitality Industry: Small Hotel and Café Jobs

Start with guest messages, then review replies, menu copy and, last, the rota. Guest messages return the most hours, and a draft-and-approve routine keeps promises and prices under your control. Automate sending only for answers that never change, and keep allergens, refunds, complaints and safety with a person.

That order comes from a worked month at a 12-room hotel with a café, where messages, reviews, rotas and menu changes add up to about 31 hours by hand. The numbers are illustrative, but the method isn't: count your own jobs, rank them by hours back against what a wrong output would cost, and begin where mistakes are cheapest to catch.

Follow me on Instagram@sagnikteaches

The 12-room hotel with a café: one month of jobs

The example is an independent hotel with 12 rooms at about 70% occupancy, so roughly eight and a half rooms a night. It has a ground-floor café open to the public from 8 to 3, an owner-manager, two part-time front-desk staff, three housekeepers and four café and kitchen staff. Four jobs eat most of the writing and planning time. The "with AI" column assumes a person reads and approves every draft, and the minutes are targets to test, not promises.

Connect on LinkedInSagnik Bhattacharya

At $25 an hour for the time involved, 18 hours is about $455 a month, against a tool cost of $20 to $50. The money isn't the interesting part. Look at which jobs the hours sit in: more than half of them are guest messages, which is why the usual advice to start with a menu or a social post chases the smallest number on the table.

Subscribe on YouTube@sagnikteaches

Ranking the four jobs by hours back and risk

Hours back isn't enough on its own, because a mistake costs different amounts in different places. Ask who sees the output, what a wrong version costs, and how quickly you would notice.

Guest messages win on both counts, because the output goes to one person and you can read it first. The rota ranks last despite 3 hours back, because staff notice an unfair rota at once and the legal rules on rest and hours are something a language model doesn't know for your location unless you tell it. The next sections take the jobs in order.

Guest messages: a fact sheet, a prompt and a no-promises rule

An assistant that answers from memory will invent a check-in time or a parking policy. Give it a one-page fact sheet and make that the only source: check-in and check-out times, what early arrival and late departure cost and when you can say yes, luggage storage, parking (spaces, height limit, price), breakfast and café hours, Wi-Fi, pets, accessibility, quiet hours, a summary of the cancellation policy, and a list of things you never do, such as holding a room without payment. Date it and give it one owner. Store it in a ChatGPT or Claude Project, or paste it in at the start of each shift. If you work in Gmail, Help me write can match your own tone on Workspace Business plans and Google AI plans, and on Microsoft 365 business plans Copilot Chat is included and works on Outlook mail. Before building anything, check whether your property management system already automates guest messages such as a pre-arrival email; Sirvoy and Little Hotelier both advertise automated guest communication.

You draft replies to guest messages for a 12-room hotel with a
café. Use ONLY the fact sheet in this Project.

Rules:
- Never confirm availability, upgrades, early check-in, late
  check-out or any price that is not on the sheet. Write
  [CHECK: what to check] instead.
- If the sheet doesn't cover the question, say we will check and
  list it under INTERNAL NOTE.
- If the message is a complaint, a safety or medical issue, an
  allergy, a payment dispute or a legal threat, do not draft a
  reply. Output ESCALATE and one line saying why.
- Under 90 words. Warm, plain, first name only. Never ask for card
  or ID details in a message.

MESSAGE:
Hi, we arrive tomorrow around 11am. Any chance of an early check-in?
Also is there parking for a van? Thanks, [first name]

An illustrative good draft says that check-in starts at 3 pm, that the guest will be texted by 1 pm if a room is ready earlier, that luggage can be stored free before then, and that parking is behind the hotel with six spaces on a first-come basis and a height limit, so would the guest tell you the van's height? It ends with a signature and, under INTERNAL NOTE, "[CHECK: room 7 turnaround before 1 pm]". The first versions from a model are rarely this clean. These are the slips I would watch for:

• "Early check-in is usually possible." The fact sheet says nothing of the kind. The model is being helpful. Delete it, because a guest who hears "usually" arrives at 11 expecting a room.
• "Free parking." The sheet gives spaces and a height limit but not a price. Either add the fact or remove the word.
• "We'll have your room ready." A promise the reception team may not be able to keep. The rule exists to stop it.
• A missed question. Guests pack two questions into one message, and models sometimes answer one. Read the draft against the message before sending.

A complaint shows the other half of the rule. A message saying the room next door was loud until 2 am and the guest barely slept should come back as ESCALATE with the reason "complaint, possible compensation". A person phones or writes personally, and decisions about refunds or credits stay with the manager. This tutorial sets out which hospitality jobs to delegate and which stay with staff.

The routine is simple. A message arrives in whichever inbox you use, someone pastes it into the Project, reads the draft against the message, fixes anything on the list above and sends it, which takes about a minute. Only once the same answers have gone out unedited for a month should you automate any of them. The safe candidates are answers that never change, such as Wi-Fi, check-in times and parking details, sent as saved replies or scheduled pre-arrival messages. Anything involving judgement stays with a person. For more on a fuller messaging set-up, see how small hotels use AI to answer guest messages around the clock.

Review replies: a rule sheet before the first draft

A reply is public and permanent, so write the rules once and paste them into every prompt. Seven are enough: thank the reviewer for a specific detail they mentioned; never mention room numbers, dates, names or booking details, since reviews can be pseudonymous and the reply is public; never argue or explain away; acknowledge what the guest says happened; don't offer refunds or compensation in public, but invite them to contact you through a named address or number; use only facts from your fact sheet; and keep it to 60 to 90 words with varied openings so ten replies don't read like one.

Where you post matters less than you might think, because the rules are the same on Google, TripAdvisor and Booking.com. Each has its own reply box and guidelines, so read each platform's before you post. On Google, a reply can take up to 10 minutes to appear and occasionally much longer. Some accounts have also been shown AI-suggested replies in a Google test running since March 2026. If you see one in your profile, treat it as a draft and run it through the same rules.

Write a public reply to this hotel review. Rules: thank the guest for
one specific detail; never mention room numbers, dates, names or
bookings; don't argue, explain away or offer compensation; invite
them to contact [name] on [email or phone]; use only facts from the
fact sheet; 60 to 90 words; sign off as [name], manager.

REVIEW:
Room was tiny and the heating didn't work. Breakfast was lukewarm.
Not worth the price.

Without the rules, a model's first attempt looks like this (illustrative): "Thank you for your feedback. As a guest in Room 4, our cosiest room, you will know we pride ourselves on 5-star service. We're sorry you felt it wasn't worth the price." It breaks four rules at once. It names a room, which tells every reader who the guest was. It argues, by recasting "tiny" as "cosiest". It hides behind a slogan. And "you felt" suggests the guest imagined the cold radiators. The version with the rules reads: "Thank you for telling us. I'm sorry the heating wasn't working and that breakfast arrived lukewarm; neither is the standard we want. I'd like to understand more, so please contact me at [email]. [name], manager." It names the two things the guest named, does not defend, and moves the conversation out of public view.

A positive review has its own trap. For "Lovely little hotel, breakfast was the best part and the staff couldn't do enough," a draft that adds "our famous rooftop terrace" has invented a terrace. Fact-sheet-only is a rule for praise as well as complaints. For a deeper look at replies that don't sound canned, see how to reply to hotel reviews with AI. If you also ask guests for reviews, Google's policy prohibits incentives and prohibits asking only the guests you expect to be happy, so send the request to everyone.

Rota: a draft from constraints, and a check before it is posted

A rota is a puzzle with firm rules and soft preferences, and a language model is a decent first-draft solver and a poor referee. So give it everything as data, let it draft, and do the checking yourself. Start by turning occupancy into housekeeping hours with a sheet, because models handle hours and headcount badly. The method is your measured minutes per occupied room plus a fixed allowance for public areas. In this illustration, 25 minutes a room plus 90 minutes:

That is 34.3 housekeeping hours for the week. Now the prompt gets the data as fixed numbers:

Draft next week's rota, Monday to Sunday, from the data below. If a
rule can't be met, say which and why. Don't break it silently.

STAFF: OM owner-manager, front desk any day, covers every front-desk
shift the others can't (the 5-shift limit doesn't apply to OM).
FD1 front desk, not Tuesday, max 24 h. FD2 front desk, Wed to Sun
only, max 30 h. HK1, HK2, HK3 housekeepers (HK3 never Sunday).
K1, K2 café, any day. K3, K4 café Fri to Sun.
COVER: front desk one person on E (07-15) and one on L (15-22) every
day. Housekeeping hours per day: Mon 4.0, Tue 3.6, Wed 4.0, Thu 4.8,
Fri 6.1, Sat 6.5, Sun 5.3 on H shifts (09-14, 5 hours each). Café:
2 staff on C (07:30-15:30) Mon to Fri, 3 on Sat and Sun.
RULES: max 5 shifts per person per week; no more than 2 L shifts in
a row; weekends shared fairly; my rest-time rules are: [paste them].
OUTPUT: staff down the side, days across, shift codes in the cells;
then any unmet rules; then the number of people on each shift each day.

The OM line matters. Two part-time desk staff can't fill 14 front-desk shifts a week, so without the owner in the data a model either reports a gap it can't fill or quietly stretches someone past their maximum. Listing the owner as cover of last resort also shows, shift by shift, how much of the desk you are working yourself. Models slip in predictable ways here too (illustrative). They schedule someone on a day they can't work, usually the one mentioned in a half-sentence. They treat 4.0 hours as "one housekeeper" when a 5-hour shift is more than the day needs, so you must decide whether to shorten shifts or accept the surplus. And the final count line is sometimes wrong even when the grid is right. So check the grid yourself against a short list: availability, cover per shift per day, maximum shifts, rest gaps and the closing-shift rule. A COUNTIF under each day's column (for example, counting the cells equal to "L") compares cover with the requirement in seconds. Paste the rota into a fresh chat, ask it to list every violation of the rules, and then check the list as well; two passes catch more than one. Working-time and rest rules differ by place and change, so write yours into the prompt from an adviser or official guidance rather than relying on the model. For roles specific to hotels, this tutorial goes through front desk, housekeeping and breakfast scheduling.

Menu copy: words from the kitchen, allergens from the card

Menu wording is a low-risk job with two traps, and both are about claims. The division of labour is simple. The kitchen supplies the facts of each dish, the AI turns them into appetising lines, and a named person copies the allergen line from the recipe card. The AI never writes, edits or "checks" an allergen line.

KITCHEN NOTE: Brown butter pear tart. Sweet pastry, almond
frangipane, roasted pear, served warm with cream. Price 7.50.

FIRST DRAFT FROM A GENERIC PROMPT:
Our award-winning, locally sourced and eco-friendly pear tart,
lovingly baked fresh daily, is a slice of heaven on a plate.

AFTER EDITING:
Pear tart: almond frangipane in sweet pastry with roasted pear,
served warm with cream.
Contains: wheat, egg, milk, almond. [copied from the recipe card]

Four phrases in the first draft are claims. "Award-winning" is false unless you have won one. "Locally sourced" and "fresh daily" need to be true for this dish. "Eco-friendly" is a generic green claim, and EU rules on green claims, in force for consumers since 27 September 2026, ban generic ones such as "eco-friendly" unless you can show recognised excellent environmental performance. If you sell to consumers in the EU, that applies to a menu as much as to a poster. The test I use is whether you could point to an invoice, a certificate or a kitchen practice that proves the phrase. If not, it goes. "Slice of heaven" fails a different test, which is that nobody remembers it.

The allergen line needs its own process. A model can format an allergen matrix from your recipe cards, but a named person verifies every row each time the menu changes, and keeps a dated copy. Guests asking "does the soup contain gluten?" get an answer from staff reading the matrix, not from a chatbot. The rules on allergen information differ by place, so check yours. For weekly specials, give the AI the chef's list and the day's stock and ask for three outputs: the board text, a two-line social post and a staff briefing. Add the allergen lines yourself. For prompts aimed at coffee shops and cafés, this tutorial has ten for menus, posts and rotas.

When a chatbot or an automatic reply is worth adding

Everything so far is drafting, with a person pressing send. There are two later stages. The first is automatic sending of fixed answers, which is low-risk. The second is a bot that answers open questions on its own, which needs rules and a test.

• Tell people it is a bot. If you have guests in the EU, the AI Act's duty to tell people they are talking to a chatbot has applied since 2 August 2026.
• Keep a route to a human. WhatsApp's Business Messaging Policy requires prompt, clear and direct escalation paths when automation replies, and lists in-chat transfer to a human agent, a phone number, an email address and web support as examples.
• Choose a bot built for the job. Meta's platform terms (section 4.7) bar providers whose primary product is AI itself, such as a general-purpose assistant, from the WhatsApp Business Platform. A bot built for a business task such as bookings or support, where the AI is incidental to the service, sits outside that bar, but confirm it with your provider.
• Know what messages cost. The free WhatsApp Business app is a separate, manual product. On the paid platform, template messages you start are charged per delivered message at rates that vary by the guest's country. Since 1 October 2026, service messages beyond 1,000 a month per business number, and utility template messages sent inside an open customer-service window, are also charged. A hotel sending about 360 replies a month would sit inside the free 1,000, but check how your provider counts them.
• Test it on real questions. Score any bot on thirty genuine guest messages, including the awkward ones, before it goes live.

The longer treatment of WhatsApp rules, templates and handover is in this tutorial on WhatsApp for small hotels.

A four-week start, one job at a time

Adding all four jobs in one week is how a trial gets abandoned. This sequence puts the biggest saving first and gives each job time to settle. It needs about eight hours of set-up across the month in the example hotel: two for the fact sheet, two for the guest-message prompt and test, one for the review rule sheet, one for menu wording and two for the rota data.

1. Week one: guest messages. Write the fact sheet with the front-desk team, because they know the real answers. Set up the Project, then draft every reply for a week and note each edit you make. The notes become rules in the prompt.
2. Week two: review replies. Paste the rule sheet into the prompt and clear the backlog of unanswered reviews. Aim to reply to each new one within two days, a target I'd choose for its own sake rather than because any study says so.
3. Week three: menu and specials. Write wording from the kitchen's notes, run the claim test on every phrase, and add allergen lines from the recipe cards by hand.
4. Week four: the rota. Draft next week's rota from data, run the checks, and compare it with the rota you would have made yourself. Don't post an AI rota until you have done that comparison at least twice.

Move on only when the previous job's drafts need under a minute of editing and no guest or staff member has pointed out a mistake. If one job stalls, leave it and carry on with the next, because they are independent.

A month-end check on guests, staff and drafts

• Minutes per guest message. Time twenty. The target in the example is about 1.2, and a figure above 2 means the fact sheet has holes.
• Edits caught per ten drafts. Invented claims, missing questions, risky promises. The count should fall week by week; if it doesn't, the rules in the prompt aren't capturing the edits you make.
• Median time to answer a guest. Note the arrival and reply times for a sample of messages. Faster is plausible as a reason guests rate you well, though a month can't prove it.
• Review replies within 48 hours. A share you can count, for example from 40% to 90% (illustrative).
• Rota changes after posting. Count swaps and corrections. A rise means the draft is missing constraints.
• Guest or staff complaints traced to an AI draft. The target is zero. Any one is worth a look at which rule was missing.

At the example's figures, the first month returns about 14 hours, because each job starts a week after the one before, for about 8 hours of set-up. Later months return the full 18, roughly $455 of time at $25 an hour for a tool bill of $20 to $50. The measure that matters more is quieter. When 12 guests a day get a clear, correct, friendly answer in minutes, the owner gets evenings back and the front desk gets time to look up from the screen at the person in front of them.

Questions from small hotel and café owners

Do I need a paid AI plan for a small hotel?

Often the free plans of ChatGPT, Claude or Gemini are enough for a dozen guest messages a day, but limits change, so test a busy week first. Paid individual plans have listed at about $20 a month. Business plans that don't train on your content by default need two seats, roughly $40 to $50 a month. Microsoft 365 business plans include Copilot Chat, and Gmail's Help me write can match your own tone on Workspace Business plans.

Is it safe to paste guest details into a chatbot?

Paste as little as possible. Use first names, leave out passport or ID numbers, card details, full addresses and health information, and keep the booking reference only if you need it. On personal plans check the model-training switch in privacy settings, and list the tools you use in your privacy policy. Anything that needs the full record belongs in your booking system, not in a prompt.

Can AI translate replies for international guests?

It is usually good enough for a friendly draft in widely spoken languages and less reliable in rarer ones. Keep the original message, ask the model to flag phrases it is unsure of, and have a fluent speaker check anything about cancellation terms, allergens or safety before it goes out. Never let a translation be the only record of a promise.

What if my staff worry AI will replace them?

Say plainly which jobs AI will take: drafting repeat replies, first-pass rotas, menu wording. Involve the team in writing the fact sheet, because they know the real answers, and make clear that nobody's hours are being cut to fund it. Don't use AI to monitor staff, and keep rota drafts open to review and swaps.

Further reads

• Where Should a Small Hotel Start With AI? — A shorter first-steps view for a small hotel.
• ChatGPT for Hotels: What It Can and Cannot Do at the Front Desk — What ChatGPT can and cannot do at the front desk.
• Hotel AI Guest Messaging Tools Compared for Independent Properties — Guest messaging tools compared for independent properties.
• Hotel Guest Complaints Handling: Service Recovery Scripts With AI — Scripts for the complaints you keep with a person.
• How to Train Front-of-House Staff to Work Alongside AI — Bring front-of-house staff along with the change.
• AI Chatbot Online for Hospitality: Questions a Café Can Safely Automate — Which café questions a chatbot can safely answer.
• Hotel Shift Handover Notes With ChatGPT: From Desk Logs to a Daily Report — Turn desk logs into a daily handover report.
• AI in Hospitality Management: Catch Supplier Price Creep on Invoices — Photograph or export supplier invoices, log every line in a price-history sheet and flag items up past your threshold before the next order goes in.
• Hotel Breakfast Food Waste: Predict Buffet Demand With AI — A worked breakfast-covers forecast from occupancy, with an accuracy test, buffet replenishment rules and a five-minute waste log for a small hotel.
• AI Tools and AI Development: The Complete 2026 Guide — the AI hub, including every tutorial in the AI-for-business series.

Sources: Google Business Profile and review-policy help pages; WhatsApp Business Messaging Policy and Meta's WhatsApp Business Platform terms; EU AI Act transparency provisions (Article 50); EU Directive 2024/825 on green claims; OpenAI, Anthropic, Google and Microsoft help pages.