The staff workflow in Nanocreator World
An approved participant receives a reward code. Staff use the Google email authorized by the business owner to access the staff page. Authorizing the correct account matters: knowing the campaign exists is not the same as having redemption access.
- Open the staff page and sign in with the authorized Google account.
- Enter the customer’s 16-character reward code and choose Check code.
- Read the displayed business, customer name, reward, terms, and expiry.
- Confirm the customer is present and the business can provide the listed benefit.
- Choose Confirm & fulfill reward, wait for the success message, and hand over the reward.
Checking a code does not redeem it
The preview lets staff inspect the reward before committing. Use that opportunity to resolve an item or location question. Do not click the fulfillment button as a way to learn what the reward is.
The successful redemption message is the handoff signal. A screenshot of an old preview is not the same as a fresh check. Single-use codes help prevent the same code being fulfilled twice; they do not establish that every aspect of the campaign is fraud-proof.
Give staff an exception checklist
A calm, consistent response protects both the customer relationship and the reward record. Do not improvise a second code or secretly mark another participant redeemed to balance the till.
| Situation | Next step |
|---|---|
| Already-used code | Check the existing record with the manager; do not fulfill it a second time automatically |
| Expired code | Explain the displayed expiry and escalate any disputed promise |
| No staff access | Ask the owner to authorize the correct Google email; refresh access |
| Reward unavailable before confirmation | Pause and ask the manager to resolve the fulfillment issue |
| Network response unclear | Recheck the recorded state before trying to fulfill again |
| Success shown but item cannot be delivered | Record the exception and have the manager resolve the customer obligation |
Rehearse the awkward moments
Use fictional data for training. Have one teammate play a customer with an already-used code and another play staff. Practice explaining that a manager needs to check the record without accusing the customer of wrongdoing.
Also rehearse an unavailable item. Confirming redemption before checking stock creates a different problem from discovering the shortage during preview. Decide who can approve an operational remedy, and document it separately from the software event.
Reconcile records with actual fulfillment
At the end of a shift, review any exceptions, the rewards actually handed over, and unresolved customer promises. Keep reward costs separate from the face value customers see on the menu.
When reviewing the campaign, distinguish approved rewards, redeemed codes, and fulfillment problems. A code marked redeemed is an operational record; it does not by itself prove a new purchase or a profitable additional visit. Use the measurement guide to connect these records to a clearly defined cohort.
Check the full reward journey.
See where owner approval ends and customer reward redemption begins.
Walk through the productPlanning your spend? Use the reward-budget calculator. Ready to see the product? Walk through the campaign flow.