The Citizen Services Operating Layer
An owned operating layer that runs constituent requests end-to-end across channels, with humans approving the decisions that carry consequences.
Where value leaks today.
Residents reach a public agency through a dozen doors — phone lines, walk-in counters, web forms, a half-broken app, an email inbox no one fully owns. Each door drops the request into a different queue with a different backlog, and the resident has no way to know whether anyone is actually working their issue. Staff spend their days re-keying the same information between systems that were never designed to talk, and the wait times that erode public trust are mostly a measure of how much manual stitching sits between intake and resolution.
Buying a chatbot or a portal does not close that gap. A tool answers the easy questions at the front and then hands the hard ones back to the same overloaded queues, so the bottleneck simply moves one step deeper. The vendor owns the model, the routing logic, and the data it learns from, which means the agency rents a thin layer of convenience while the structural problem — work that cannot move without a person carrying it — stays exactly where it was.
What a public body actually needs is an operating layer it owns: agents that take a request from any channel, do the legwork of classifying, enriching, and routing it, draft the response or the action, and stop at the points where a human must decide. The value leaks today because nobody owns the connective tissue. Kitsune forges that tissue as a system the agency keeps.
One governed flow — agents act, you approve what matters.
Residents get a single, tracked path from request to resolution, and staff stop carrying work that the system should move on its own.
One operating layer — eight governed jobs.
Each is a governed agent inside the same system, sharing context — not eight tools you stitch together.
Omnichannel Intake Agent
Pulls requests from phone, web, email, walk-in, and app into one governed queue with a single canonical record. No request lands in a silo no one watches.
Intent and Eligibility Classifier
Reads each request, infers what the resident actually needs, and flags likely eligibility for the relevant service. It tags urgency so emergencies never sit behind routine traffic.
Constituent History Resolver
Stitches a unified view from records scattered across departments so staff and agents see the full prior interaction, not a blank slate every time.
Response Drafting Agent
Composes the reply or service action in plain, accessible language matched to the resident's channel and preferred language. Drafts wait for human sign-off before anything sends.
Routing and Handoff Agent
Sends each item to the right desk with full context attached, and escalates anything that crosses a policy threshold to a named human owner.
Language and Accessibility Agent
Translates and reformats every outbound message to meet accessibility and multilingual obligations without a separate manual pass.
SLA Watchdog Agent
Tracks every open request against its service commitment and surfaces anything drifting toward a breach before the resident has to chase it.
Audit Trail Agent
Records who decided what and why at every gate, producing a defensible record for oversight without staff writing it up by hand.
Autonomy you can trust — because the control is built in.
The system acts on its own and every action stays legible, bounded, and reversible. You don't choose between speed and control; the control is what makes the speed safe.
Legible
See what was done, what was declined, and exactly what's waiting on you — nothing happens in a black box.
Bounded
Agents act only within the rules you set. Anything material or irreversible stops at a human gate.
Reversible
Every action is logged and undoable. A wrong turn is caught and rolled back, not discovered weeks later.
Owned
One operating system you own — not a swarm of rented agents you have to police. Built, run, accountable.
Residents get a single, tracked path from request to resolution, and staff stop carrying work that the system should move on its own.
What you're actually getting.
Is this a product or a build?
It is a build. Kitsune forges a citizen services operating layer around your existing channels and record systems, then hands you a system you own and run — not a seat in someone else's platform.
What stays in my control?
Every consequential decision routes to a human gate. Agents do the gathering, drafting, and routing; your officers approve what carries policy or legal weight, and the audit trail records each call.
How is this different from a portal or chatbot tool?
A tool answers questions at the front and hands the hard work back to your queues. The operating layer carries the request all the way through — classifying, enriching, drafting, routing, and closing the loop under your governance.
Does it work with our legacy systems of record?
Yes. The layer is forged around the systems you already run, reading and writing through them rather than asking you to rip and replace. The history resolver exists precisely to bridge fragmented legacy data.
How do we meet accessibility and multilingual duties?
Dedicated agents reformat and translate every outbound message to your accessibility standards as part of the pipeline, so compliance is built into the flow rather than bolted on after.
The same foundry, other domains.
Bring us the bottleneck.
We'll forge the operating layer around your friction — built, owned, and running.