Most restaurant referral programs fail for a boring reason: nobody asks. A card in the bill folder is not an ask, and a line on the website is not an ask either. The program works when a server, a host, or the phone system makes a specific request at a moment when the guest is already pleased, and when the reward is easy to explain in one sentence.
Decide what counts as a referral
Write the definition down before anything else. A referral is a new guest who arrives, mentions the name of an existing guest, and has not been to the restaurant before. A guest who brings friends along on their own booking is not a referral, and treating it as one burns the reward budget on visits that would have happened anyway.
The test is simple: could a host confirm it in ten seconds at the door? If the answer requires a spreadsheet and an argument, the definition is too complicated and staff will stop applying it.
The ask belongs at the end of a good meal
The moment to ask is when the plates are cleared and the guest has said something positive, not when the bill is presented. A server who has just been told the short rib was excellent can say, plainly, that the restaurant runs a referral and what it gives. That is a real ask, and it comes from a person the guest already trusts.
The same ask belongs on the phone. When someone calls to book and mentions a birthday or an anniversary, the person answering can mention the referral in the same breath. Elevoi answers those calls around the clock, captures the caller's details, and books the table, so the ask is not limited to the hours the host stand is staffed.
Keep the reward simple and the rules shorter
Pick one reward and describe it in a single line. A dish the kitchen does well, a dessert for the table, or a set menu are all easy to picture and easy to hand over. Cash-equivalent rewards invite the guest to compare value, and anything conditional invites a conversation at the door.
Set the rules in plain language: one reward per new guest, the referral has to be mentioned when booking, the reward applies from the second visit, and the program can change with notice. Post the rules where staff can see them, because the person at the door is the one who has to defend them.
Track it without buying software
Start with a named code, one per referrer, and a note field on the reservation. That is enough for a program that produces a handful of referrals a week, and it keeps the cost near zero. As volume grows, move to a single code plus the referrer's name, or to a booking page that asks how the guest heard about the place.
Review the log monthly. Referrals that never convert, meaning the guest was named but never came in, usually mean the referrer is being generous with the program rather than the restaurant. Referrals that convert and then return are the signal that the ask is landing with the right people.
Make the referred guest feel expected
A referred guest arrives with a recommendation in hand, which is a different experience from a walk-in. Note the referrer's name on the reservation and use it: the host can thank them for coming on someone's recommendation, and the server can mention it once. Small recognition is what turns a first visit into a second.
Then close the loop with the referrer. A short text saying their friends came in, and that the reward is noted, is the message that produces the next referral. Without it, the program drifts into a one-time favour.
Keep consent and privacy intact
Record only what the program needs: the referrer's name, the new guest's name, and the date. Do not ask the referrer for a friend's phone number and text that friend, because a message from a restaurant they have never visited reads as spam and can breach Canadian anti-spam rules. The referral has to originate with the guest who is coming in.
Related: the AI receptionist for restaurants and cafés hub, and the loyalty program for restaurants and cafés for guests who already come often.