Gift card calls are easy revenue handled badly at most restaurants. They spike around the holidays and every gifting occasion, they're usually taken by whoever picks up, and the payment often gets captured in the least safe way available: a card number read aloud and written on something.
The short answer is that the gift card isn't the risk — the payment capture is. Move the payment to a secure link or a compliant processor and most of the problem disappears, along with a fair amount of staff time.
What callers actually want to know
Most gift card calls are informational, not transactional. The common questions:
- Do you sell gift cards
- What denominations, and is there a minimum or maximum
- Can I buy one over the phone, online, or only in person
- Can it be mailed, emailed, or picked up
- Does it expire, and can it be used for delivery or only in-house
- Can I check a balance
Every one of those has a fixed answer, which means most of this volume shouldn't require a person at all. Publishing them on your website and in your listing removes a share of the calls, and an agent that answers them accurately handles most of the rest. The ones that need a person are the actual purchases, and even those are better handled by pointing the caller at a checkout.
The payment problem
Here's the failure pattern worth naming plainly. A caller wants a $200 gift card. Staff takes the card number over the phone, writes it on a pad or a napkin, runs it later or hands it to a manager. That slip of paper is now a liability that has nothing to do with whether the order was legitimate — it can be photographed, lost, or misused, and it pulls your operation into the sensitive scope of payment security rules.
The better patterns, roughly in order of preference:
- Send a purchase link. Text or email the caller a link to your gift card checkout. They enter their own card into a proper payment page, and no card data ever touches your restaurant.
- Capture through a compliant, tokenizing processor so what you hold is a token and a transaction record rather than a card number.
- Take it in person if the caller prefers, and treat the call as a reservation of intent rather than a sale.
What should never happen is a card number on paper. We cover the general shape of safe phone payment in collecting payment over the phone safely and the compliance context in PCI compliance for restaurant phone payments.
Why gift cards attract fraud
Gift cards are a known fraud target for a structural reason: they convert credit into stored value almost instantly, and stored value is hard to claw back. Someone using a stolen card number to buy gift cards is turning stolen credit into something spendable well before the chargeback arrives — at which point you've lost both the value and the payment.
The patterns worth a second look:
- An unusually large gift card order from a first-time caller
- Urgency, especially pressure to complete the purchase immediately
- A request for multiple cards in specific denominations
- A caller who wants the codes read to them over the phone rather than a physical card or an email to the purchaser
- Any story that explains why the normal process can't be followed
None of these prove fraud. Plenty of legitimate corporate gift card orders look like several of them at once. They're a reason to add one verification step, not to refuse the sale. A callback to the number on file, or insisting on a payment link the purchaser completes themselves, filters most of it without insulting real customers. The broader treatment is in reducing phone-order fraud and chargebacks.
Set a policy before you need one
Decide these in advance and write them down, because they're bad decisions to make live on a call with someone applying pressure:
- A dollar threshold above which a gift card purchase requires manager approval or a callback
- Whether codes are ever read aloud over the phone (many operators say no)
- Whether phone purchases are completed by link only
- How balance checks are handled, and what identifying information you require
A written policy is also what protects staff. "Our policy requires a manager to approve orders over $X" is an easy thing for an employee to say and a hard thing for a pressuring caller to argue with.
Where an AI agent fits
The informational calls are a clean fit. Do you sell gift cards, what denominations, how do I buy one, can I use it for delivery — an agent answers these instantly and identically, including after hours when a gifting decision is actually being made.
For the purchase itself, the sensible pattern is that the agent captures intent and sends a secure purchase link rather than handling card details on the call. That's both safer and simpler, and it means the transaction runs through the same checkout as your online sales.
Whether to let an agent complete high-value gift card purchases unattended is a policy call. Given the fraud profile, a threshold that routes larger purchases to a person is a reasonable default. Ask any vendor how the payment step actually works and where the card data goes before you enable it. What to ask before buying an AI phone system has the broader question list.
The bottom line
Gift card calls are worth capturing and easy to handle badly. Most of the volume is questions with fixed answers, so publish them and let whatever answers your phone handle them directly. For purchases, get the card off the call: send a secure link or capture through a compliant tokenizing processor, and never write a number down. Know the fraud pattern — large, urgent, first-time, codes-read-aloud — and set a dollar threshold that routes those to a person, in writing, before someone is pressuring your staff on a Friday night. Handled that way, gift cards are one of the easier revenue streams to run off the phone.