Public Grievance Portals: Beyond Ticket Routing

A vendor demoed an agent that resolved 62 percent of grievances without an officer. Resolution, on inspection, meant a polite paragraph and an auto-close. One of the closed items was a pension stoppage. Another was a caste-certificate delay. The department already had CPGRAMS and a state portal. The vendor had built a shadow closer that made the dashboard green and the citizen furious.

Centralised Public Grievance Redress and Monitoring System (CPGRAMS) at pgportal.gov.in is DARPG's 24x7 public grievance system, connected to central ministries and to states. Most states also run their own portals, sometimes integrated, sometimes merely adjacent. Those systems already have categories, time limits, appeal paths and political visibility. An agent that ignores them is not innovation. It is a second, unofficial CPGRAMS.

This guide is for DARPG-facing nodal officers, state grievance cells and collectors. It is written on 17 August 2026. It is not a DARPG circular and not legal advice. Appeals and public-service guarantee Acts (where a state has one) still run on their own clocks.

Start from the portal that already exists

List the official doors: CPGRAMS, the state portal, the department's own inbox, the collectorate's paper receipt, sometimes a CM helpline. The agent is a clerk behind those doors, not a fifth door that closes tickets the others cannot see. If you add a chat on the department site, every conversation that is a grievance should create a numbered ticket in the official system. A chat without a number is how you lose appeals. Do not promise that the bot is CPGRAMS. It is not. GIGW-shaped pages should link the official portal in the same viewport.

Grievance work an agent may take versus what remains a public duty.

Task	Agent role	Officer / system role
Help the citizen pick a category	Suggest two categories with reasons	Citizen or operator confirms; portal records it
Draft a first reply from a signed pack	Draft only	Nodal officer sends or rejects
Find the last similar closed case	Retrieve if the corpus is lawful and de-identified as required	Officer decides if it is actually similar
Translate a grievance	Draft translation labelled as such	Do not treat the translation as the legal text without a rule
Close / dispose	Never	Always a named competent user in the official portal
Mark not a grievance	Suggest, with a reason	Nodal officer, especially if it is an RTI or a service request

Routing is where politics hides

Wrong routing is the oldest grievance-cell failure. An agent that sends land issues to agriculture because the text said field will recreate it at machine speed. Suggest two desks, show the words that drove the suggestion, and let the nodal officer pick. Never auto-route to a minister's office or a collector to show seriousness. That is how you drown the only desks that can actually act, and how you create a political log you did not intend. VIP flags, if your portal has them, are a policy. Do not let a model invent a VIP flag from a surname.

Narratives are personal data and sometimes more

A grievance is a story: names, relatives, account numbers, medical facts, caste, land. It is personal data under DPDP. It may also be defamatory, or a crime report that belongs in an FIR path, or an RTI request in disguise. Do not train on grievance narratives. Do not embed them in a vendor host. If you retrieve similar cases, design a de-identified index the DPO will sign, or do not retrieve. A suicide threat, a missing child, or a violence report is not a classification exercise. Write break-glass routing to a human now, before you go live.

Quality is not deflection

Measure time to first human-quality reply, appeal rate, and re-open rate. Do not measure bot resolved. Auto-close is a way to lie to DARPG and to yourself. Sample weekly for courtesy, correctness against the signed pack, and whether the official ticket exists. A fluent answer that never entered CPGRAMS is a miss.

Two rooms you can walk into

Green dashboards versus numbered files.

Objections you will hear — and what to do with them

These are the lines that stall the file. Answer them in the room, then put the answer in the note.

CPGRAMS is slow, so we need our own AI portal.

Build speed inside the official door — drafts, better categories, officer assist. A faster unofficial closer will be treated as concealment when a case lands in the House.

The model can detect duplicates better than clerks.

It can suggest duplicates. Merging or closing as duplicate is still an officer act. Wrong merges hide live injuries.

We will train on last year's grievances to learn tone.

Last year's grievances are full of personal data and sometimes hate. Use a redacted style guide the cell writes. Do not donate the district's wounds to a model.

Citizens prefer chat to forms.

Then chat is a front end that still emits a form — a numbered ticket. Preference is not a licence to skip the number.

A five-week grievance assist that cannot close

If you do not have a nodal officer who will sit the sample, do not start.

1. Week 1: inventory doors — CPGRAMS, state portal, helplines. Write the rule: no number, no answer that looks like a disposal.
2. Week 2: DPA, training ban, break-glass for harm. De-identified similar-case decision (yes with design / no).
3. Week 3: category suggestion + draft reply on a signed pack. No close tool. No VIP invention.
4. Week 4: GIGW-shaped chat on the government domain, link to pgportal.gov.in and the state portal.
5. Week 5: weekly sample on ticket-created, correctness, courtesy. Kill auto-close if anyone added it.

How this shows up in the file

Subject: Agent assist on public grievances. Official doors remain CPGRAMS (pgportal.gov.in) and the state portal. Every chat-borne grievance shall create a number in an official system. The agent may suggest categories and draft replies. It may not close, dispose, merge, or escalate to a political office. Narratives are personal data; training is banned. Break-glass for harm is named. This is not a DARPG circular.

What we will and will not claim

Prcept AI will draft inside your portal and refuse a close tool. We will not sell you a green deflection rate built on ghost files. If we cannot connect to the official number, we should not face the citizen.

This article is informational field guidance for Indian universities and public institutions, not legal, procurement, audit or engineering advice. Confirm against the live Gazette, GFR, state financial rules, GeM terms, UGC text, GIGW, DPDP commencement, departmental manual and your counsel before you file it.

How to sequence this in a state, not a slide

“Public Grievance Portals: Beyond Ticket Routing” is a department problem. A P1 CIO/CTO should name the legacy system, the officer who owns the file, and the citizen charter clock before buying “grievance portal AI government”.

CPGRAMS and state grievance portals already exist. Use an agent to draft and classify inside those systems. Do not build a shadow closer that skips the desk. Do not invent league tables of states. Read tenders and policies. Election Model Code of Conduct can freeze a rollout. NIC is a partner, not a villain. SDC readiness is GPU, power, ops and egress — not a logo.

• Audit the legacy store first.
• Keep mutation and money as officer actions.
• Map SLAs to the citizen charter.
• Budget change requests after go-live.

Close this loop before the next CAB

Put “Public Grievance Portals: Beyond Ticket Routing” on the next change-advisory or bid-opening agenda as a single line item with an owner. If it cannot earn a line item, it will not earn a control. The owner should be a P1 CIO/CTO, not “the vendor.”

Revisit the item when the model, the GeM term, the region, or the SI changes. “grievance portal AI government” is not a one-time workshop. It is a watch item. Date the last check. Unsigned watch items are souvenirs.

What must be true before you file this

If “Public Grievance Portals: Beyond Ticket Routing” is only a heading, it will not survive a file inspection. A P1 CIO/CTO should be able to attach one artefact that proves “grievance portal AI government”: a log export, a clause, a scored row, a dated notice, or a refusal rule.

Write three dated sentences: what was decided, who owns it, and when it will be re-checked. Unsigned sentences are souvenirs. Dated sentences are controls.

• Name the owner of “grievance portal AI government” inside the institution.
• Attach one artefact a stranger can open next year.
• Revisit when the model, the notice, or the SI changes.
• Do not treat a vendor slide as evidence.