Civic & Government /Customer-service agent live field guide · 9 min

Council Enquiry Assistant

A 24/7 first responder for routine rates, waste, and permit enquiries that answers from the council's own published information with citations, and hands the complex or vulnerable cases to staff with the full context attached.

Open the live demo

theater/demos/civic-gov_council-enquiry-assistant.html · sandbox · read-only

Open

FIG. 1

The live demo, running on fabricated data. Open it to step through the full flow — every output is shown for a person to approve before anything happens.

How it would work

Reads the council's shared inbox, classifies and routes each enquiry, drafts a reply from published service standards, and holds anything sensitive for an officer to approve before a word goes out.

Input 01

The shared inbox

Inbound enquiries arriving by email and web contact form into one council inbox — rates, waste, roads, footpaths — each a free-text message with a sender, a channel and an arrival time.

Agent 02

Classifies, routes, drafts

Reads each message, infers intent, urgency, sentiment and location, routes it to the right team, opens a case reference, and drafts a reply from the council's published service standards.

Output 03

A draft and a routing, for review

A routed, case-referenced draft with its source standard cited — and an injury or vulnerable-resident message flagged and held for an officer to approve, edit, or escalate before anything is sent.

Where it works well

It surfaces the urgent message buried under twenty routine ones, and drafts the routine ones in seconds.

Best for a customer-service team running one shared inbox across rates, waste, roads and permits — high volume, mostly repeat questions.
It reads the whole queue at once and pushes the injured-resident, vulnerable-person and complaint messages to the top, with a routine reply already drafted for the rest.
At hundreds of enquiries a week, the recaptured hours go back into the calls that need a human voice, not into re-keying bin-day answers.

The slow, invisible cost of a council inbox is triage: a footpath-injury report from a distressed resident sits in the same queue as a transfer-station hours question, and on a busy morning the wrong one gets answered first.

Where it works badly

It is confidently wrong when it answers from a stale standard — and a polished, cited reply hides that the figure behind it changed.

Weak on the message that mixes a routine question with a complaint or an injury — it should flag and hand over, never smooth it into a tidy auto-reply.
Free-text is ambiguous: "my bin wasn't collected" could be a missed service, a contractor fault, or a damaged bin, and the wrong route sends the resident in a circle.
If most of your volume is genuinely novel or contested, the drafting saves less than the officer's own judgement already does.

The honest test

If you cannot say, today, which version of the rates schedule, fee table and waste calendar the drafts are answering from — this tool makes your out-of-date answer faster, not safer.

Point it at last year's rates schedule, a superseded waste calendar, or a fee that was indexed on 1 July, and it drafts a clean reply citing a service standard that no longer holds. The citation makes it look more trustworthy, not less. That is the trap.

What it doesn't do — and shouldn't

It drafts and routes. An officer approves. The injury message never auto-sends.

WHAT IT DOES

Routes each enquiry to a team and opens a case reference

Cites the published service standard the reply is drafted from

Flags injury, vulnerable-resident and complaint messages and holds them for review

WHAT IT WON’T

Send any reply on its own say-so

Acknowledge or admit liability on a public-liability or injury claim

Decide a complaint, a development application, or a hardship request

A reply from the council is the council's position. On a footpath-injury or public-liability matter, an unguarded acknowledgement can prejudice the council's insurer, which is exactly why those messages route to the liability team and hold rather than auto-answer. Personal information in the inbox is handled under the Privacy Act and, for a Victorian council, the Information Privacy Principles in the Privacy and Data Protection Act. The accountable officer stays on the decision because the consequence lands on the council, not the tool.

What your data has to look like

Published service standards as current structured content, and a routing map of who owns what.

Typical readiness

across orgs we see, before the first job

Rates, fees and waste schedules as current structured content

Needs shaping

A routing map of teams and what each owns

Usual weak point

Escalation rules for injury, vulnerability and complaints

Needs shaping

Published service standards with response times

Usual weak point

A case or CRM system to log and reference enquiries

Usually ready

The real first job

The published content is usually the weak point — schedules held as PDFs that went stale on the last fee indexation, and a routing map that lives in people's heads. Getting that content current, structured and owned is usually the real first job, larger and more valuable than the drafting layer on top. Once the standards are clean and the routing is explicit, every reply after that is faster and right by default.

Right fit if…

You run one shared inbox across rates, waste, roads and permits, high volume

Most of your enquiries are the same handful of routine questions

You can point to the current, in-force rates, fee and waste schedules today

You have clear teams to route to and explicit rules for what must reach a person

Walk away if…

Your fee tables and waste calendars live as last year's PDFs nobody owns

Most enquiries are novel, contested, or complaints rather than routine

You have no agreed escalation rule for injury or vulnerable-resident messages

You want a tool that answers liability and hardship matters without an officer

Open questions

The worried-buyer questions, answered straight

It can draft a wrong or risky reply — which is exactly why injury, public-liability and complaint messages are never sent on its say-so. When it detects a personal-injury report or a vulnerable resident, it routes the message to the council’s liability or relevant team and holds the draft for an officer, rather than acknowledging fault. Councils are routinely advised not to admit liability on a public-liability claim, so that boundary is deliberate. The tool surfaces and drafts; the officer decides what the council says.

It works from the message text plus your published standards and routing map. Free-text enquiries are genuinely ambiguous — “my bin wasn’t collected” might be a missed service, a contractor fault, or a damaged bin — so it classifies, shows its reasoning, and flags what it is unsure of rather than forcing a route. The messier your published content and routing rules are, the more it guesses; getting those current and explicit is usually the first piece of work, and the piece that pays off across every enquiry after.

No. It removes the triage and the re-keying — sorting the queue and drafting the routine bin-day and rates-instalment replies — so officers spend their time on the calls that need a human voice: the distressed resident, the complaint, the hardship request. Every reply is still approved by a person before it sends, and the injury and vulnerable cases are handed to them with the full context attached. The capacity it frees goes back into resident-facing work, not headcount.

Current to what is in force today. Council fees are commonly indexed on 1 July and waste calendars change with contractor and public-holiday schedules, so a reply citing last year’s figure is confidently wrong. The draft is only as good as the standard behind it. The honest test: do you know, right now, which version of the rates schedule, fee table and waste calendar these replies are drafted from?

Names, addresses and the details in an enquiry are personal information under the Privacy Act, and for a Victorian council under the Information Privacy Principles in the Privacy and Data Protection Act, with collection and disclosure limited to what is necessary. Any deployment runs against your own inbox, CRM and data handling, not a shared pool — we scope where the data sits and who can see it as part of the build. The demo here runs entirely on fabricated enquiries; Margaret Hughes is not a real resident.

No. It drafts to the service standards and routing rules you give it and flags the matters that must reach a person, but it does not certify compliance. Records of enquiries and decisions sit under your state’s public-records obligations, and the wording on a liability or statutory matter is the council’s position — an officer confirms it. The tool gets the routine reply most of the way there; the accountable officer closes the rest.

What it takes to build

3–4 weeks · 4 phases

Reused from template~70%

Bespoke to this skin~30%

stack · Claude · website CMS · CRM connector · review UI

What it would cost

Fixed scope, fixed price, fixed dates.

Bite-sized first piece

One contained change, low risk

Pilot build

Most builds land here

Embedded support

Scale on proof

Considering this for your council?

The honest place to start is a bite-sized first piece — one contained change, low risk. Tell us where the inbox hurts; we'll play it back, scope it, and show you what's possible.

Book a call How we work