Broadcasts that respect how each parent wants to be reached
Studio composes one broadcast. Each parent receives it on their preferred channel — push, SMS, email, or in-app — based on category.
The story
Mike sends one snow-day announcement. Some parents want it texted. Some want a push. Some only check email. Today, the studio sends three versions and someone misses one.
Pirouette is one composer, one send. Each parent's notification preferences split routing per category — billing goes by text, schedule changes go by push, broadcasts go by email, emergencies override everything. The studio sees per-recipient delivery status.
What this looks like in practice
- One composer, one send — channel decided per recipient
- Per-category preferences: billing / schedule / broadcasts / closure / emergency
- Per-recipient delivery state visible to admin
- Emergency category overrides preference — always reaches every parent
Related
Parents ping the studio. The studio replies. The channel stops mattering. Christina stops triaging two inboxes.
Your balance. Your kid's schedule. Your kid's progress. No drilling, no emailing the front desk, no calling.
Want to see this running on your studio's data?
Walk through a demo with us. We'll show this feature in context against the day-to-day workflow your studio actually has.