Ownership
Every request has a clear current owner instead of disappearing into a shared inbox.
Ask without guessing who to email
A fictional intake experience that routes requests by purpose, sensitivity and urgency instead of forcing people to know the church org chart.
Design rule
Route metadata first.Collect the minimum information needed to get a request to the right role. Ask for sensitive details only inside the appropriate workflow.
Care request
This route could privately connect someone to meals, transportation, pastoral conversation or financial-assistance screening without exposing the full story to general staff.
This demonstration intentionally stores and transmits nothing.
What a real workflow should remember
Every request has a clear current owner instead of disappearing into a shared inbox.
General staff see routing status, not automatically the sensitive content inside every case.
The system records whether the person was contacted, transferred, resolved or needs follow-up.