Voucher questions when the balance is invisible

How long is it valid, where can it be spent, does it cover this: those are properties of the voucher scheme and are identical for every holder. They can be answered fully, with a citation, and they are the bulk of what arrives.

How much is left on mine is a different species of question. A balance sits against one issued code in a system the assistant has no sight of, and it changes every time somebody spends. There is nothing to retrieve and nothing to calculate, and the reply has to say so rather than hedging.

The reason the split matters more here than it looks is that both halves usually arrive in the same message. Answering the easy half warmly and skating past the hard half reads as a balance check that came back positive.

Somebody planning to use a voucher is planning a purchase, and the moment to tell them it will not cover the thing they have in mind is now, while they can still choose differently. Held back, the same fact arrives at the point of payment in front of other people, which is where a small policy becomes a bad afternoon.

Write the exclusions as a short list rather than as a clause buried in terms. Retrieval works on passages, and a list of five excluded categories is a passage. A sentence beginning save where otherwise stated is not.

Expiry is where voucher conversations turn hostile, because the holder did not buy the thing and did not choose the date. State the period and the event it runs from, and state whether an expired voucher is simply dead or whether the team will look at it.

If you do sometimes extend, do not publish that as an entitlement, because then every voucher lasts forever. Publish that circumstances can be put to the team, and let the assistant collect the code, the purchase date and what happened. That is the difference between sounding rigid and being fair.

Somebody who has lost a card wants you to find it. The assistant cannot search for anything, and it should not imply that a person can either until your published position says so.

The useful shape is: here is what we can do about a lost voucher, here is what the team will want from you, and here is where to send it. Proof of purchase, the approximate date, the buyer's name and the amount are what turn this from an unanswerable request into a five minute job for somebody with access.

A balance, whether a specific voucher has already been spent, whether one that was posted ever arrived, whether a code was cancelled. None of this is in any document you could index, and a confident answer about somebody else's voucher is a disclosure as well as a guess.

Collect the code, the buyer and the purchase date, and get it to whoever can look. That handover is short and it resolves. An improvised reassurance does neither.

The closed branch, the discontinued service, the business that changed hands. Whether the value transfers, part transfers or lapses is a commercial and sometimes a legal question, and it is decided by a person who knows what was promised when it was sold. An assistant reaching for the nearest page about your current locations will answer the wrong question warmly.

It reads as helpfulness. Somebody asks whether their voucher covers a booking, the assistant matches on a cheerful page about gift cards being usable across the range, and says yes. The exclusion sits in a terms document that page never mentions.

They arrive, they are refused, and they have your own answer on their phone. The cost is not the value of the voucher, which you will probably honour anyway rather than have the argument. It is that somebody was told by your business that something was fine and then told at a counter, in public, that it was not. Publish the exclusions as a list, keep the marketing page out of the retrievable set, and set the caution level so a weak match returns your fallback instead of the friendliest nearby paragraph.