Automation or AI? When a simple rule does the hotel job better

Automation runs fixed steps: the same input always produces the same result. AI composes an answer, so the same input can come back worded differently. Use a rule when the input is predictable and the right answer is fixed. Use AI when the input is free text and a person can check the draft before it leaves the hotel.

A vendor walks into the office and says the new tool uses AI to send the pre-arrival email. The email goes out three days before arrival, every time, with the same template. That is a rule with a calendar attached, and it has been doing the job for years. This article gives you a way to sort the difference in practice: a three-question test, a division of hotel tasks into rule, AI draft plus person, and person only, and the questions to ask before you sign anything.

What is the difference between automation and AI in a hotel?#

Automation runs steps a person defined in advance; AI composes an answer from patterns in text. The practical difference is who decides the answer: your written rule, or the model.

A rule has three parts: a trigger (a booking is confirmed), a condition (arrival is three days away), and an action (send the pre-arrival email). Nothing is composed; the text is a template somebody approved. Robotic process automation, usually shortened to RPA, is software that repeats what a person does on screen, click by click. It is still a rule, with no judgment inside it, and it breaks when the screen changes.

An AI assistant takes a question or a piece of text and produces wording it composes. Ask the same question twice and the wording can differ, which is useful for a draft and awkward for a policy. Both are software and both can be wrong, but the failure modes differ. A rule fails visibly: it did not fire, or it fired on the wrong condition. An AI draft fails quietly: it reads well and says something untrue.

This is why the automation vs AI question is really a testing and audit question. Rules are cheap to test: you can write down every input and check every output before the rule goes near a guest. An AI draft is tested by sampling real cases and reading each one. Rules are easy to audit: the log says which rule fired, on what data, at what time. An AI answer needs the question, the data it was given and the draft kept together, or nobody can reconstruct it later.

Why vendors call a rule AI#

A timed email with a template is automation, but "AI" sells better at the moment. The test is simple: ask the vendor to change one word of the output and show you where the decision lives. If the answer is a template setting, you are buying a rule. That is not a bad thing. It may be exactly what the task needs, and it is easier to verify than any composed draft. What you should refuse is paying an AI premium for a calendar.

How do you decide between a rule and AI? A three-question test#

Ask three things: is the input predictable, is the right answer fixed, and what does a mistake cost. Two yeses and a low cost point to a rule.

Question one: is the input predictable? A booking record, a room status and a timestamp are predictable. A guest's complaint email, a review and a phone call are not. Question two: is the right answer fixed? "Send three days before arrival" is fixed. "Reply to this review in the hotel's voice" is not, because two good replies can look nothing alike. Question three: what does a mistake cost? A wrong internal alert costs a phone call. A wrong sentence to a guest costs trust. A wrong charge costs money and a correction on the bill.

If your rule needs more than a handful of exceptions, either you have not found the rule yet, or the task is not a rule task. Write the exceptions down and look at them together. Then write the rule on one page before you buy anything: the trigger, the condition, the action, who is told, and how it is undone if it fires wrongly.

Run it by hand for two weeks. A person follows the rule manually and marks every case where the rule would have been wrong. That count is your evidence, and it costs nothing.

The same test works in reverse for AI. If the input is free text and a person can check the draft quickly, AI is a candidate. If nobody has time to read the output, AI is the wrong tool.

Three or more yes answers point to a rule.

Which hotel tasks does a simple rule handle better?#

Tasks with a fixed trigger and a fixed outcome: timed messages, threshold alerts, closing a rate at a level a person set, and the compliance steps that must happen the same way every time.

A pre-arrival message three days before arrival, with the hotel's own offer attached, is the classic case: the wording is a template, the timing is a rule, and the guest gets the same reliable sequence every time. If you want to improve what goes in that message, start with what to send in a pre-arrival email and when, not with the tool that sends it.

An alert when a room has been out of order for two nights, sent to the front office and housekeeping together, keeps the room from quietly disappearing from sale. Closing or opening a rate when it reaches a level the revenue manager set lets the person make the decision once and the rule execute it every night. This is not AI pricing, and it should never be described as one.

Night audit belongs here too: close the business day, void and reverse instead of deleting, and produce the same report in the same shape every night, so month-end comparisons hold. The guest identity notification at check-in, prepared and sent from the check-in flow, must carry the same fields in the same order for every arrival. Housekeeping assignment by floor and section, with a manual override for the day a section is short-staffed, and a group block pickup report at a fixed hour, so the sales manager reads the same number at the same time each day instead of asking for it.

Where does an AI draft plus a person do better?#

Where the input is free text and the output is wording: complaints, review replies, plain-language questions about the hotel's own numbers, and translation.

Complaint replies and review responses are the clearest case. AI produces a first draft; a person edits the tone, removes any promise the hotel cannot keep, and sends it. Questions about the hotel's own data in plain language, such as how last night compared with the same night last year, are also a good fit; the value is in the question being answered in words, not in a new report. If this use interests you, asking plain-language questions about your own hotel data is worth a separate read.

A first draft of the morning briefing, written from numbers a person already trusts, gives the duty manager a starting point before the meeting. Translation into guest languages works well as a draft, checked by someone who actually reads that language, because a polite sentence in the wrong register is worse than a plain one.

One limit matters more than the rest. The assistant only knows what the system hands it. It does not know tonight's rates, tonight's availability or a policy changed this morning unless the data is passed with the question. Why an AI assistant does not know tonight's rates explains this in detail.

Keep the draft and the final text side by side. The difference between them is the clearest record of what your team had to correct, and it is the best training material you will get.

Which hotel tasks should stay with people?#

Decisions with money, law or a person's feelings attached: rates, refunds, compensation, staff matters, and any promise the hotel has to keep.

Setting the rate and the floor is a person's decision; a rule can execute it all night, but a person decides what the floor is and why. Refunds, complimentary nights, upgrades given away, and moving a charge from one account to another are judgments about relationships, not calculations. Anything with a fiscal or legal consequence, meaning what goes on the invoice, what is sent to an authority and what is kept as a record, needs a person's confirmation before it leaves the building.

A distressed or angry guest standing at the desk needs a human being in the room, and no draft improves it. Hiring, rosters and discipline stay with people, because a team member will remember them for years. Negotiating with a travel agency or a corporate account stays with people, because the other side is reading the room as much as the numbers.

And the moment two rules conflict, a person takes over. A repeat guest asks for a rate below the floor. A rule cannot weigh loyalty against margin; a person can, and should write down the reason.

How do a rule and an AI draft work together?#

The rule does the timing and the trigger, the AI composes the wording, and a person approves anything that leaves the hotel.

For example, a room has been out of order for two nights. The rule raises the alert, the AI drafts the note to the front office and to the waiting guest, and a person reads it and sends it. For example, a rate reaches the floor the revenue manager set. The rule closes it, the AI drafts one line of explanation for the morning briefing, and the revenue manager reads it before the meeting.

The rule keeps the AI inside its lane. It decides when the assistant is asked and which data it is given, so the draft starts from the hotel's own numbers rather than from memory. Every step leaves a record: which rule fired, what the assistant was given, what the person changed, what was sent and when.

A message already sent to a guest cannot be undone, so the approval step sits before sending, never after. Everything else can be reversed and corrected. Start with the rule alone, and add the draft only when the writing itself is the slow part, not when the deciding is.

For a wider view of where AI fits in a hotel and what its limits are, see a practical guide to AI uses, limits and safeguards in hotels.

What should you ask a vendor who says AI?#

Ask which rule the tool replaces, what it does with an unusual input, and who checks the output before it reaches a guest.

Show me the same question twice. Does the answer change, and does the change matter for a guest or for the bill? What data does it read, and where does that data come from? An assistant that answers from general knowledge rather than your system is a writing aid, not an operations tool.

Which actions does it take alone, which need one person's confirmation, and which need two? Ask for the list, not the principle. Can you see the record of what it did last Tuesday, and can you undo it? If the answer is no, the tool is not ready for anything that touches money or a guest. What happens when it is wrong: who is told, how quickly, and what the guest is told?

Can you turn the AI part off and keep the rule? A tool that only works as a package is a tool you cannot step back from on a bad night. And ask for the same demonstration on your own data, with two awkward cases you choose. A demonstration on a clean sample proves very little.

What to do next#

Pick one task this week, write it as a rule on a single page, and run it by hand for two weeks before you buy anything. The test in this article sorts the work: fixed trigger and fixed answer go to a rule, free text goes to an AI draft with a person behind it, and money, law and people stay with people. When a task arrives dressed as AI, check first whether it is a rule, because a rule is the cheapest thing you will ever have to test and audit.