AI agent for civil servants
Municipal Service Routing Agent
Every service request reaches the department that accepts it, the first time where possible.
What it does
Residents' service requests, such as potholes, broken lights or noise, bounce between departments. When a request arrives, this agent extracts the issue and checks the location against the map. If it finds an emergency indicator, such as a downed power line, it stops normal routing and follows the emergency protocol. Otherwise it applies the routing rules, creates a work order with evidence for the right department and watches for acceptance. If the department rejects ownership with evidence, the agent chooses the next allowed route or escalates. A coordinator approves any message to the resident. Edge case: a report of a leaning tree near a school is on a state road, so it is rerouted to the state highway contact.
How it works
Follow the arrows from top to bottom. The orange dashed arrow is the loop: when a check fails, the agent goes back and tries again.
Read the steps as a list
- Resident request arrives
- Extract the issue and validate the location
- Does it contain an emergency indicator?If not: continue normal routing. Back to step 2.
- Create a routed work order with evidence
- Track acknowledgement
- Did the department accept ownership?If not: choose the next allowed route or escalate. Back to step 4.
- Coordinator approves resident communicationsThe agent waits here for your OK.
- Routed task with ownership history
How it decides
It picks the department from context, location and rules, watches for acceptance, and reroutes on evidence-backed rejections.
- Department: from issue type, location and rules.
- Emergency: hand off to the protocol, no normal routing.
- Reroute: only on rejection with evidence.
Make it yours
Every agent is a starting point. You choose these settings for your own situation.
- Routing rules per issue type and area
- Emergency keywords that trigger the protocol
- Hours to wait for acceptance before escalating (default 24)
- Who approves resident updates
- Escalation contact per department
What keeps you in control
It always asks you first
- Resident communications
- Emergency dispatch
- Routing policy changes
Hard limits
- Emergency cases follow the protocol, not the agent.
It stops when
- Done: department accepted.
- Escalated: no department accepts.
Set it up
We guide you through the set-up, step by step
Members get the full set-up guide for this agent. No technical skills needed: you copy, paste and upload.
- One set of instructions to paste into your AI, with the clicks for ChatGPT, Claude, Microsoft 365 Copilot, Gemini and Grok
- The agent then walks you through connecting your own data, one source at a time
- A downloadable copy with the flow chart, the rules and the full guide