Wendy’s Smoky ’Shroom Sprint: a big invitation with a small prize pool

For Wendy’s New Zealand, Gamify describes an endless runner supporting a menu launch, with daily prize draws. The pool held 20 burger vouchers and 10 combo upgrades. Its report gives the play total above. [1]

The distinction between a game objective and a reward rule matters. One tells the player what to do on screen. The other tells them what participation can deliver. When the two are easy to confuse, the promotion may attract attention while leaving people with a different expectation from the one the business intended.

Our practical takeaway is to write the reward sentence first. Then check the invitation, start screen and result against it. Someone should not discover only after playing that the pictured product was a chance to win, rather than something they had earned.

Our reading of the Wendy’s format is that the prize gave the menu launch an event rhythm. A daily draw can provide a reason to check again while a runner provides something to practise. Those are two different reasons to return, and neither requires every participant to receive a burger.

That does not mean a small prize pool is inherently disappointing. It means the size and rule belong in the invitation. Keep the photograph, the value of the reward and the actual terms aligned. A picture of a whole meal should not quietly turn into a small add-on at collection.

The named burger also keeps the reward close to the launch. A generic gadget might attract prize seekers while saying little about the menu. Our adaptation changes the promise: a limited stock of fixed meal bonuses makes fulfilment simpler for a small food business. That is a deliberate change from Wendy’s draw, not a claim that one rule is universally better.

A person can replay because the game is enjoyable, because they want a better score or because the invitation remains on their phone. None of those reasons necessarily produces another transaction. Keeping play and purchase separate makes a campaign easier to improve.

If your objective is a future visit, design a future-use offer. Put the invitation into today’s bag, name the next eligible purchase and make the destination easy to find. For a mobile food business, a reward is useful only if the customer knows where and when to come back.

Use this approach at a recurring stop with a credible next service date. An invitation to return is weak when the business will not be nearby again. A game cannot solve that location problem, but a clear schedule link can remove avoidable uncertainty from the offer.

For this kind of pilot, collect evidence in stages: game starts, finished rounds, issued codes, redeemed codes and qualifying later orders. A higher play count alongside unchanged redemptions asks a different question from strong redemptions with increasing reward costs.

Staff can record an order reference when a customer uses the offer. This gives you an associated purchase to inspect alongside your ordinary sales records. It is stronger evidence of a visit than a score or a saved screenshot, though it still does not isolate the campaign from everything else affecting sales.

Give the offer time to mature before judging it. Looking at codes issued yesterday and expecting them all to have returned today can make a workable repeat-visit campaign look weak. Review a completed offer window and compare similar locations or service periods.

Start with a quantity your team can fulfil comfortably. Add publication, print and administration costs to the cost of rewards actually handed over. Keep different currencies separate and count a missing amount as unknown. The useful output is a known cost for a specific customer experience.

After the pilot, decide what to change from the stage that stalled. A weak response to the bag insert may need a better invitation. A saved code that nobody uses may need a more relevant purchase condition or clearer next-stop information. Increasing the prize is only one possible answer.