A phone call in the first week of January
A guest rings to book the spa day her sister gave her for her birthday. She reads out the code. Your receptionist looks it up and sees that the voucher expired three weeks ago. The guest says she never knew there was an expiry, the voucher was an email forwarded by her sister and the date was at the bottom in small print. She asks to speak to the manager.
The manager, who has had four of these calls this week, extends it. Last week a different manager refused a similar request. Both decisions are recorded, if at all, in a note on the booking. Nobody could tell you how many vouchers are about to expire this month, or whether the recipients know.
The voucher knows its date, the recipient does not
Vouchers are usually sold to the giver and redeemed by someone else. Your system holds the buyer's email. The recipient, who is the person who actually needs to book, is often unknown until the day they call.
- Expiry is printed on the voucher but never communicated again.
- The buyer's email is the only contact, and the buyer has long forgotten.
- Vouchers bought for a package that has since changed carry unclear terms.
- Extension decisions depend on which manager is on shift.
- Peak seasons (after Christmas, before summer) bring a wave of late bookings for vouchers that are about to lapse, when availability is already tight.
Disputes, discretion and full diaries
Every dispute takes a manager away from the floor. Inconsistent decisions get noticed: guests compare notes, and a refusal after a friend got an extension turns into a public review. A cluster of near-expiry vouchers all trying to book the same fortnight means guests cannot get a date and feel cheated even when the voucher is still valid. Some spas quietly extend everything to avoid the argument, which just moves the problem.
How we build voucher expiry tracking
- We import your voucher records from your spa system, online voucher shop and any paper voucher book, into one register with code, value or package, sale date and expiry.
- At purchase, the giver can add the recipient's name and email, and choose whether the recipient hears from you directly.
- Reminders go out at points you choose, for example three months, one month and two weeks before expiry, to the recipient if known and the buyer if not, with a link to book.
- Your extension policy is written as rules: who can extend, by how long, whether a fee applies, and whether the package value changes. Reception sees what the rule allows when a guest rings.
- Every extension or refusal is logged with who decided and why, so the next call about the same voucher starts from the facts.
- A monthly view shows vouchers due to expire, so you can see a booking surge coming and open availability for it.
| Voucher situation | Today | With tracking |
|---|---|---|
| Expiring in six weeks | Nobody knows | Recipient reminded with a booking link |
| Expired last month | Manager decides on the spot | Policy shown, decision logged |
| Package discontinued | Argued case by case | Substitute rule applied |
| Recipient unknown | Only buyer's old email | Buyer asked to pass it on |
The rules themselves are yours. What your voucher terms say, and what consumer law expects of them, is a matter for your own adviser. We make sure the terms you set are applied the same way every time.
After the reminders go out
Recipients book earlier, spread across the year rather than in a rush at the end. When someone does ring with an expired voucher, reception can see the reminders that were sent and the policy that applies, and offer what the policy allows without escalating. The manager sees a weekly summary of extensions instead of being pulled into every one.
Is this how your January goes?
- Expired voucher calls reach the manager most weeks.
- You do not collect the recipient's contact details at purchase.
- Extension decisions vary depending on who answers.
- Voucher bookings bunch up just before expiry dates.
- You cannot list next month's expiring vouchers in a few clicks.