Citizen service navigation
Help residents reach the right service without another queue
Residents do not know your departmental structure, and they should not have to. They describe a problem and get transferred until someone can help, repeating details each time. This blueprint navigates the service catalogue conversationally, explains requirements in accessible language, submits complete requests, and leaves every statutory determination with a public servant.
- The team
- 3 AI worker roles escalating into 2 human decision owners.
- The process
- 6 orchestrated stages, each with a named decision owner.
- The channels
- Voice, Web chat, SMS, WhatsApp on one shared context.
The shift
What breaks today, and what changes
The challenge
- Residents navigate a complex service catalogue by transfer, repeating their details at each hop.
- Requests arrive incomplete, so cases bounce between departments before work can begin.
- Accessibility and language needs are handled inconsistently depending on who answers.
What changes
- Residents describe the problem in their own words and reach the correct service and department.
- Requests arrive complete, so departments open cases they can act on immediately.
- Accessible channels and languages are available by default rather than by exception.
The team
Every seat has one job and a defined level of autonomy
This is what gets configured in Team Canvas: role-scoped AI workers, the humans they escalate into, and a trust level on each connection that sets what a worker may do on its own. Trust starts tight and widens on evidence.
AI workers
Service navigator
Translates what a resident describes into the correct service and requirements.
- Owns
- Intent and navigation
- Trust level
- Acts within policy — published guidance only, never a determination
Request coordinator
Collects the minimum required information and submits a complete request.
- Owns
- Request completeness
- Trust level
- Acts within policy — data minimisation enforced
Status worker
Reports case status and expected next steps so residents stop chasing.
- Owns
- Status transparency
- Trust level
- Acts within policy — read-only against the case record
Human decision owners
Caseworker
Owns assessment, statutory determinations, and discretionary decisions.
Owns: All determinations
Safeguarding officer
Takes safeguarding, vulnerability, and emergency disclosures immediately.
Owns: Safeguarding response
The process
The conversation starts the work. The workflow finishes it.
Each stage records the decision that was made and the role accountable for it — which is what makes the run reviewable afterwards rather than a black box. Where the platform executes a stage rather than a person or agent performing it, that is named too, and accountability still sits with the role.
- 1
Understand the need
Which service and jurisdiction does this actually belong to?
Service navigator
- 2
Explain requirements
Is this published guidance, or does it require a determination?
Service navigator
- 3
Collect the minimum
What is the least information needed to make this request actionable?
Request coordinator
- 4
Check for risk
Any safeguarding, vulnerability, or emergency signal? Escalate now.
Safeguarding officer
Run by workflow
- 5
Route
Which department and priority band, and on what basis?
Request coordinator
Run by workflow
- 6
Keep informed
Has the case moved in a way the resident should hear about?
Status worker
Decision rules
The non-negotiables encoded in the workflow, not left to a prompt.
- Eligibility information is always framed as informational guidance, never as a determination.
- Safeguarding, vulnerability, and emergency disclosures escalate to an officer immediately.
- Data minimisation is enforced — only fields required for the specific service are collected.
- Accessible channel and language options are offered proactively, not on request.
Controls & guardrails
What makes this safe to run in production, and provable afterwards.
- Statutory and discretionary authority reserved for public servants.
- Data minimisation and public-record auditability on every interaction.
- Accessibility and multilingual provision as a default configuration.
- Mandatory safeguarding escalation paths that cannot be bypassed.
Platform capabilities
What this blueprint runs on
Nothing here is bespoke. Each blueprint is a configuration of the same platform, which is why the second one you launch reuses the governance you already reviewed.
Channels
- Voice
- Web chat
- SMS
Systems it reads and writes
- Case management system
- Service catalogue
- Identity & verification service
- Records management
Measurement
What we instrument from day one
These are the measurements the pilot puts in place, not benchmark results. You set the targets against your own baseline — and the same instrumentation is what decides whether a worker's trust level widens.
- First-time-right routing
- Measures how often a request reaches the right department without an internal transfer or re-route.
- Request completeness
- Tracks the share of submitted requests a caseworker can act on without going back to the resident.
- Accessible reach
- Records which channels and languages residents actually use, so provision follows real demand.
Correct department
Actionable on arrival
Channels and languages
Rollout
How this one goes live
A deliberately narrow start, supervised, with autonomy widened per role once the record supports it.
Weeks 1–3
Navigation and guidance
Help residents find the right service and understand requirements. No submissions yet, so navigation accuracy is proven first.
Weeks 4–6
Complete request submission
Enable submission for two or three high-volume services under data-minimisation rules, with caseworker review on every request.
Week 7+
Status transparency and reach
Add proactive status updates and extend accessible channels and languages based on measured resident demand.
Questions we get asked
Citizen service navigation, in practice
- Can it decide whether a resident is eligible for a service?
- No. Determinations — statutory and discretionary alike — are reserved for public servants. The navigator explains published requirements as guidance and is explicit that it is not making a decision on the resident’s case.
- How is resident data handled?
- Data minimisation is enforced in the workflow: only the fields the specific service requires are collected, and every interaction and access is recorded for public-record auditability under least-privilege access.
- What about residents who need accessible or non-English channels?
- Accessible channels and additional languages are offered proactively as part of the standard configuration, and usage is measured so provision can follow actual demand rather than assumption.
What changes in Government & public sector
Guidance is explicitly informational, accessibility and language options are first-class, and determinations stay with officials.
Read the full Government & public sector analysisRelated blueprints
Teams that run next to this one
Next step
Build this team around one measurable win.
We map your version of this process, compose the worker roles, connect your systems, and agree the escalation points with the people who own them — then run it supervised.