Live program
Member to Promoter.
Every stage needs a trigger, and every trigger resolves to one verified record.
Verify, visit, onboard, review, refer.
Use a data feed wherever 10 Fitness can provide one, and a controlled QR code or link everywhere else. Five rewarded stages run off one verified record, and the last stage turns the member into the source of the next one.
Reward the next right action.
Each stage runs on its preferred trigger, with a fallback behind it, and every reward matches back to the record created at stage 01.
A new member verifies, opts in, and gets rewarded in the same session.
Every later stage needs something to match against. This is where the anchor record and the retained Rewards Vault session are created.
- The new member scans the welcome code, or opens the link sent after joining.
- They enter name, mobile, and optional email, and agree to the SMS terms.
- A four-digit code arrives by SMS and is entered back — the record is now verified.
- The mystery reward is scratched, revealed, and banked in their Vault.
The club system reports the visit and the reward releases itself.
Getting a new member back through the door the first time is what turns a signature into a routine. Rewarding it removes the friction between joining and showing up.
- The check-in export arrives from the club system.
- The record matches the verified anchor created at Stage 1.
- The reward is released to the running balance with no screen for the member to complete.
- An SMS points them back into their Vault to claim it.
Follow-through, not intent.
Onboarding is where a new membership becomes a habit. Paying on completion rather than booking keeps the reward attached to the outcome that matters.
- The member books and attends their onboarding session.
- The trainer reveals the completion code at the end of it.
- The member scans while they are still in the club, and the reward releases against the same verified record.
- The feedback request is queued from this completion event.
Private feedback and public proof, kept separate.
Feedback from a verified new member is worth more than volume, and separating private feedback from public review requests keeps the program policy-safe.
- The onboarding completion event hands off to Review Boost.
- The member rates the experience and adds a comment.
- A public review request is offered separately, never conditioned on sentiment.
- Verified completion releases the reward into the same balance.
The new member becomes the promoter.
By this point the member has been verified, rewarded, and asked for their opinion. Referral is the natural next action, and it feeds the top of the same program.
- The member opens their private referrer hub, gated behind SMS.
- They share a personal link or code with a friend.
- The friend lands on a named invitation and verifies their own number.
- Only then does the referral reward pay — verified and consented on both sides.
The member experience
Joins, then scans the welcome code or opens the link, verifies by SMS, and scratches a mystery reward.
Comes in for the first visit. The check-in feed releases $10 with no screen to complete.
Finishes onboarding, scans the trainer’s completion code, and collects $10.
Shares feedback through Review Boost and collects $5, with the public review request kept separate.
Opens their referral hub and earns $5 for every friend who verifies.
Feed where there is one, QR or link where there is not.
Every stage has a preferred trigger and a fallback behind it, so the program runs at clubs with an integration and clubs without one.
Membership and check-in exports
The club system posts joins and check-ins. Rewards Vault matches each record to the verified anchor and releases the stage reward with no member screen.
Preferred where availableControlled codes in club
A welcome card, desk poster, or the trainer’s completion code. The member scans where the action happens, so the event is proven.
Runs with no integrationText or email link
Staff or the welcome sequence sends the link. Same verification, same anchor record, no club visit needed.
Remote fallback