Community-level routing
Use location, care interest and configured service areas to prepare the right destination.
For multi-community operators
Create a consistent first response across every community
A planned portfolio intake layer for routing each family to the right community while giving regional teams a clearer view of demand, follow-up and handover.
Planned workflow
01
Apply shared intake standards
02
Route context to the responsible community
03
Provide portfolio visibility without bypassing local ownership
The operator challenge
Consistency is difficult when every community has a different rhythm
Central standards matter, but so does local ownership. The product direction separates portfolio visibility from community-level access so teams can work in the right context.
Central reporting
Give authorised regional leaders a portfolio view of enquiry sources, timing and follow-up status.
Consistent standards
Define shared questions, handover expectations and escalation rules without erasing community nuance.
Role and community separation
Plan access around community, regional and central responsibilities as a future capability.
A bounded workflow
From first contact to responsible ownership
- 1
Apply shared intake standards
- 2
Route context to the responsible community
- 3
Provide portfolio visibility without bypassing local ownership
Continue exploring the intake journey