The voucher question, and how to automate it

"I have a voucher, how do I use it?" is one of the most common and least automated questions a hotel or spa gets.

The reason is not that the question is hard. It is that the answer depends on facts the guest has not given you yet.

Vouchers come from many suppliers. Gift sites, credit card clubs, employer benefit portals, resellers, your own front desk. Each one sells packages that look similar and behave differently. One includes a night with breakfast. One is a treatment only. One is a cash value. One expires in twelve months, one in six, one was extended by a supplier notice your reception never saw. Until you know which one the guest is holding, there is no answer to give.

So most properties do the only thing they can. They ask.

Why staff hate it

Reception has to establish where the voucher was bought, which package it is, whether it includes a night, a meal or a treatment, and whether it is still valid. That is four questions before the conversation about dates even starts.

Each question is a round trip. The guest writes in the evening, reception answers in the morning, the guest replies at lunchtime. A booking that should take one exchange takes three days, and somewhere in the middle the guest either phones instead or books elsewhere.

It is also the kind of work that goes wrong quietly. A new receptionist recognises the supplier logo and assumes the package includes dinner, because the last three did. The guest arrives expecting a table, and nobody finds out until 19:00 on a Friday.

Worst of all, the same four questions get asked hundreds of times a year and never get easier. There is no learning curve on an interrogation.

Let the assistant collect the facts

This is a near perfect job for an assistant, because it is structured questioning with a known set of answers.

The assistant asks the guiding questions in order. Where did you buy it. Which package is written on it. Do you have the voucher number, or a photo of it. It matches the supplier and the package against a list you maintain, and it hands reception a clean request with the answers already filled in.

What reception receives is not "guest has a voucher, please handle". It is the supplier, the package name, the voucher number, what the package includes, the expiry date, the dates the guest wants, and the number of people. That is a request someone can act on in one minute without opening a chat history. It is the same discipline as turning a guest message into a ticket: the value is in the request arriving complete.

Two details make the difference between this working and this being annoying.

Ask in the guest's terms, not yours. Guests do not know your internal package codes. They know the name on the printed card and the colour of the website they bought it on. Your list should carry the supplier's own public names and the common misspellings, so that a guest writing the name of a gift site in Hebrew or in English lands on the same entry.

Accept a photo early. Long alphanumeric codes typed on a phone are a drop-off point. Let the guest send an image of the voucher and read the details from it. If the image is unclear, ask for the one field you actually need rather than making the guest start again.

The edge cases you must write down

The assistant is only as good as the rules you give it, and vouchers are made of exceptions. Write these down before you launch, not after the first complaint.

• Vouchers with no night attached should never trigger a stay confirmation. A treatment voucher that produces a booking confirmation email creates a guest who believes they have a room. This is the most expensive mistake on the list, and it is entirely preventable with one rule.
• Two coupons on one booking may need two bookings, or a person. Some suppliers forbid stacking. Some systems cannot hold two redemptions against one reservation. If your rule is "one voucher per booking", say so in the chat, politely, at the moment the guest mentions the second one.
• Expired vouchers go to a person, with the expiry date in the request. Never let an assistant refuse an expired voucher on its own. Many suppliers extend, many properties honour a near miss for a good guest, and that is a judgement call with a commercial cost. Hand it over with the date visible so the decision takes seconds. It belongs on the same list as the other requests you must not automate.
• Suppliers you no longer work with. When a contract ends, the vouchers keep arriving for a year. Decide the answer once, in writing.
• Cash value vouchers. These behave like partial payment, not like a package. Keep them on a separate path.
• Vouchers bought for someone else. The buyer's name and the guest's name will not match. Do not let that become an identity problem at the desk.

What to do this week

Open a spreadsheet. One row per supplier, one row per package. Columns for what it includes, what it excludes, validity, whether it stacks, and who signs off on an exception. Most properties find they have far more live packages than they expected, and that no single person knew all of them.

That sheet is the asset. The assistant is just the thing that reads it at two in the morning without getting tired. It is the same principle as treating a quote as the sale rather than as paperwork: the guest is ready to buy, and every extra round trip is a chance to lose them. If the voucher is redeemed against a stay, the guest then joins the ordinary journey, so make sure the sequence of messages they receive reflects what the package actually includes.

Takeaway

Give the assistant your supplier and package list, and let it do the questioning. Reception gets the answer, not the interrogation.