Messaging System Refresh
Redesigning how parents, teachers, and admins communicate with role-based channels that protect privacy without sacrificing connection.
COMPANY:
Procare Solutions
TEAM:
Designer, PM, Dev Lead
My Role:
Product Designer
TIMELINE:
9 months
status:
Shipped
Problem
Messaging is one of Procare's most-used features. So when it needed work, that work mattered.
The existing system had one messaging area with no role separation. Directors had no way to message parents privately about billing, behavior escalations, or enrollment without that conversation being visible to their own staff. Everything lived in the same flat list, which meant sensitive conversations either happened in the product without privacy, or got routed out to email instead.
The feature existed. It just wasn't built for the reality of how a childcare center actually operates.
I don't want teachers seeing conversations about billing or behavior issues
Research
Director Interviews
Directors needed a private channel for sensitive conversations: billing, behavior escalations, enrollment. This was less about security and more about trust and role clarity. They didn't want to route those conversations outside the product. They just needed a place inside it that teachers couldn't see.
Teacher Feedback
Teachers wanted a professional communication channel that kept boundaries clear without requiring them to share personal contact information. Parents were reaching them directly, and there was no in-product alternative that felt right for that relationship.
Parent Surveys
Parents were confused about who they were reaching. One communication channel for everything made interactions feel unreliable. They never knew if they were messaging the teacher or the office.
Known pain points
How we got to a solution
The question wasn't whether to separate the channels. Research made that clear. The question was how to surface that separation in the UI without adding cognitive load for users who just wanted to send a message.
We went back and forth between two directions.
Design decisions
One home for messaging
Messaging lived in two places. Parent messages were buried inside Parent Connection. Staff messages were inside Staff Management. We consolidated both under a new top-level Messaging nav item with two sub-items: Parent Messaging and Staff Messaging.
Privacy by architecture, not by permission
Teachers don't see Office Chat because it doesn't exist in their context. Not because of a settings toggle. The access boundary is built into the architecture — structural privacy that just works.
Context clarity
The tab label tells a parent who they're reaching before they type anything. Office Chat = administration. Classroom Chat = their child's teacher. The label tells parents exactly who they're reaching before they tap.
Split panel: context without context-switching
The chat panel and student details panel live side by side. Admins never have to leave a conversation to pull up family info. Directly addresses a workflow observed repeatedly: open message, navigate to profile, lose the thread, start over.
Testing + Impact
Privacy satisfaction scored higher than overall satisfaction in post-launch testing. Directors and parents trusted the channel separation before they fully trusted everything else about the feature. The structure worked before everything else caught up.
What's Next
