Online grievance systems such as the centralised public-grievance portal have made it far easier for citizens to raise a complaint. The harder part comes next: someone has to read each grievance, work out which office and which rule it concerns, decide how urgent it is, and draft an answer that actually resolves it. In most departments that work is still done by hand, one grievance at a time.
Where the time goes
- Grievances arrive through several channels and in several languages
- Routing depends on knowing which office owns which scheme or service
- Urgent cases look like routine ones until someone reads them
- Replies are drafted from scratch, so quality and consistency vary
What triage agents can safely do
The engine our grievance triage reuses was built to triage complaints at scale for an insurer under regulatory scrutiny. It scores frustration and impact, decides whether a complaint is in scope, assigns one of four priority levels and escalates the most critical the same day — with an analyst able to override every decision. The same pattern fits government grievances: read, mask, classify, route, prioritise, draft.
Who does what in a grievance squad
Agent designs from our AI & Agentic Engineering practice
| Agent | What it does | Who decides |
|---|---|---|
| PII Guard | Masks personal data before any AI processing | Data protection officer sets the policy |
| Grievance Triage Agent | Detects language and topic, routes and prioritises | Grievance officer can reassign |
| Reply Drafter | Drafts a reply citing the rule it relies on | Grievance officer edits and sends |
| Charter Timeline Watcher | Warns before a timeline lapses | Nodal officer acts |
Note: Designs, not delivered public-sector results.
Measuring what matters
Disposal time is the obvious measure, but it rewards closing grievances rather than resolving them. Track reopened grievances and repeat complaints from the same citizen or location alongside it, and the incentive points the right way.