Eighty-two percent. That is the share of inbound citizen queries an AI agent called Bobbi resolved in its first week across three English police forces, without a single hand-off to a human officer. The number matters less for policing than for what it telegraphs to the rest of government: the chatbot era, finally, is ending.
I say this with some scepticism about my own past. Anyone who has helped stand up a citizen-facing assistant inside a large national department knows the temptation to call any conversational widget a chatbot and declare modernisation complete. It is not. Bobbi, alongside Singapore's GovTech work and Estonia's interoperable agent network, signals that the next layer of public-sector AI will look very different from what most administrations are currently buying.
Chatbots answer. Agents act.
The technical distinction is sharper than the marketing suggests. A chatbot replies to a prompt. An agentic system is handed a goal — process this permit renewal — plans the steps, calls the databases, validates against the rules and executes the transaction. One produces text. The other completes a workflow.
This is why a recent World Economic Forum and Capgemini exercise mapping seventy core government functions sorts them more cleanly by workflow than by department. Eligibility assessment, document processing, fraud detection, permit issuance — these cut across ministries; they are the natural unit of analysis for an agent, not an org chart. Agents do not need to break silos. They operate outside them.
The chatbot habit is the trap.
The single most common mistake I see, both in India and abroad, is treating an agentic deployment as a chatbot upgrade. Same procurement template, same vendor, same knowledge base, a slightly cleverer model bolted on the back. That is not what the technology is for. The Capgemini survey of 350 public-sector organisations finds that ninety percent intend to explore or deploy agentic AI within two to three years, while Gartner forecasts that more than forty percent of those projects could be cancelled by 2027 — usually because the agency moved before understanding where the actual value sits.
The value sits in outcomes, not interactions. The right question is not can the bot answer this but what is the citizen actually trying to finish, and how many steps can we collapse into one supervised flow. An estimated one hundred and forty billion dollars in US federal benefits goes unclaimed each year because the application paths are too fragmented for the people who most need them. Most large administrations, India included, will find similar pockets if they look honestly: schemes whose stated reach far exceeds their actual delivery, not for want of policy but for want of plumbing.
What conversational AI for citizens actually teaches.
Citizen-facing conversational systems at national scale teach two unfashionable lessons. First, the volume of routine queries is far larger than any budget anticipated, and far more repetitive: a small set of questions accounts for most of the load. Second, when the citizen needs to complete something rather than learn something, the conversational layer hits a wall. The handover to forms, portals and back-office staff is where the experience breaks.
Agents are precisely the technology for that gap. In a direct-taxes context, an agent can read a notice, retrieve the relevant return, pre-fill a form against rule sets, cross-check historical filings and route only the genuinely ambiguous cases to a human officer. The administrator stays the architect. The agent does the clerical labour that nobody, on either side of the counter, particularly enjoys.
Bounded autonomy, glass-box defaults.
The discipline the field is converging on is bounded autonomy: being deliberate about what an agent is allowed to do, keeping a human meaningfully in the loop, and making every step auditable. The phrase that fits a public-sector context is glass-box governance. A chatbot answers, and the trail is shallow. An agent acts, and each action — every rule consulted, every database queried, every form submitted — should leave a perfect record. Used well, this is more accountable than the human-only system it replaces, not less.
The procurement template should change accordingly. Stop buying chatbots. Buy a workflow agent that ships with an audit log by default, with explicit, narrow permissions per task and a hard escalation rule for any case touching rights or material amounts. Bounded autonomy belongs in the contract, not in a vendor promise.
Where to start.
The most useful first move for any Indian department is unglamorous: pick one workflow that already exists end-to-end on paper or in disconnected portals — refund issuance, grievance redressal, a single notice-and-reply cycle — and rebuild it as an agentic flow with a human checkpoint at the decision. Measure completions, not interactions. Compare cost not to the chatbot it replaces but to the staff hours it returns. That number is what budget committees will eventually demand, and it is the only one that matters.
The chatbot was a useful detour. It taught millions of citizens that they could speak to the state in plain language and get a sensible answer. The agent is what turns that conversation into a completed transaction. The departments that grasp the difference now, and procure for it accordingly, will spend the next decade doing more with steadier headcount. The rest will spend it explaining why their bot still cannot actually do the thing.
#AgenticAI #PublicSectorAI #DigitalGovernance #GovTech #CitizenServices #AIinGovernance #IndiaAI

.jpeg)
.jpeg)
.jpeg)