Christina's homepage
Search bar dominant. Shift handoff visible. Today's queue, pending actions, end-shift-to-Diane in one action.
The story
The front desk has a single working surface — not a generic dashboard with twenty tiles. The search bar is on top because Christina's first move when a parent walks up is always a name lookup. Everything she needs after that — balance, kid schedule, payment-promise history, recent interactions — opens with one tap on the result.
Shift handoff is a first-class tile, not a buried feature. Christina writes a short note for Diane at end of day; Diane reads it on open. The 'end shift to Diane' action is a single button — not a workflow.
What this looks like in practice
- Search-bar-dominant — name lookup is the first action of every interaction
- Family record opens in one tap: balance, kids, payment-promise log, recent notes
- Shift-handoff tile at the top, end-of-day cash-out in one action
- Unified inbox: parent emails, schedule questions, billing questions, sub requests
- Stored-card 'tap to charge' on the parent's record — Christina never types card info
Related
Parents ping the studio. The studio replies. The channel stops mattering. Christina stops triaging two inboxes.
Stripe charges the stored card on the billing date. Christina doesn't push autopay. Diane doesn't push autopay. Nobody pushes autopay.
Parents enter their own card. Christina handles the next person. Rush-hour stops being a single-threaded bottleneck.
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.