Unified inbox: email, SMS, push, in-app — one thread
Parents ping the studio. The studio replies. The channel stops mattering. Christina stops triaging two inboxes.
The story
Parents reply to texts; email gets ignored. If 2-way SMS is gated to a top tier or billed per message, you either upgrade, pay overage, or fall back to one-way blasts nobody reads.
Today, parents email the studio for things they should be self-serving — balance questions, schedule questions, class change requests. Christina ends up doing work the parent portal should be doing for them, plus answering the email anyway.
Pirouette unifies the channels. A parent texting, emailing, pushing through the portal, or messaging in-app all land in the same thread, claimed by whichever front-desk staff picks it up. Per-message thread on the kid's record so the history follows the family.
What this looks like in practice
- Email / SMS / push / in-app collapse into one thread per family
- First-claim locks routing — no two staff coordinating the same parent
- Per-kid message history on the student record
- Teacher-to-parent messages route through the broadcast engine — teacher never sees the parent's phone
Related
Studio composes one broadcast. Each parent receives it on their preferred channel — push, SMS, email, or in-app — based on category.
Teacher opens the app, sees today's class roster, taps a kid, the kid is present. No drilling, no laptop, no end-of-day catch-up.
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.