Choosing Your Level Rewards
Pins, certificates, wristbands — and why the front desk moment matters.
Written By Dave Hemann
Last updated About 2 months ago
When a student completes a Level, something should happen. Musician Quest tracks the milestone - you choose how to celebrate it.
How Level rewards work
Every Quest is divided into Levels, and completing a Level is the big milestone moment in a student's journey. The reward itself is entirely your choice:
Collectible enamel pins - one design per Level, worn on a lanyard, jacket, or instrument case
Certificates - printed and presented, great for recital programs and family photos
Wristbands - colored by Level, popular with younger students
Or anything else that fits your studio's brand and culture
The front desk moment
Whatever reward you choose, we strongly recommend making the award a moment - not something mailed home or handed over quietly at the end of a lesson.
The final step of the teacher lesson loop is walking the student to the front desk when a Level completes. The front desk staff congratulates the student, presents the reward, and the family sees it happen at pickup. That thirty seconds does more for retention than almost anything else in the system - it's public, it's earned, and every other student in the lobby sees where the path leads.
Practical tips
Stock rewards before launch. Nothing deflates the moment like "we'll have your pin next week." Order enough of your first few Levels' rewards to cover your early completions.
Expect early Level completions. Students who start above Level 1 by proficiency won't need Level 1 rewards - but students who choose to start at Level 1 to collect everything will move through early Levels quickly.
Keep designs consistent. A collectible set - where Level 7's reward visibly belongs to the same family as Level 1's - gives students a reason to want the whole run.
Was this helpful?
More in Getting Started
What is Musician Quest?The Three Account TypesYour Setup Path - From Signup to Your First Family EmailStill need help? Ask the team