Citizen Request Management in Local Government: Resolving Isn't Enough, It Must Be Traceable
Short answer: In the public sector the real problem isn't that requests go unresolved; it's that nobody knows where they are. As a request is handed from department to department, its history stays behind. The fix: pool every channel into one queue, carry the history along with the hand-off, put the statutory clock on a timer, and give citizens a tracking code instead of an account.
A request reaching a municipality is rarely one department's job. "The street light is out" goes to public works, "noise complaint" to inspection, "tax balance" to finance. For the citizen it is one institution; inside the institution the request changes hands. Every hand-off loses a piece of the trail.
Three ways the trail disappears
- Channel scatter. Requests arrive at the call center, the web form, the corporate mailbox,
social media, and sometimes a directorate's own line. The total is visible nowhere.
- Silence after hand-off. The request is transferred to one unit, which transfers it to
another. The citizen doesn't know where it is; neither does the institution.
- Unprovable resolution. The work was done, but "when, and by whom" has to be dug out of an
email archive.
The citizen journey: where it breaks
| Step | Typical today | What it should be |
|---|---|---|
| Submission | 4–5 channels, no shared record | Any channel, one record |
| Registration | A separate list per channel | One queue, one number |
| Routing | Hand-off by email | Hand-off into a queue, with history |
| Follow-up | "I called, they're looking into it" | Citizen checks with a tracking code |
| Closure | Verbal confirmation | Timestamped record |
Guest submissions: don't make citizens open an account
When someone must register, set a password, and then remember it, part of the submissions never happen and the rest move to the phone. Tixenta has a guest ticket flow: the citizen opens a request with an email address and a tracking code and follows it with the same code, protected against spam and bots. Call volume drops and the request enters the system.
Hand-offs between departments, without loss
Authorization in Tixenta is granted through the combination of role, organization, department and record ownership (RBAC + ABAC). In public sector terms: each directorate sees only its own requests, a hand-off drops the record into the new unit's queue, and the request's history travels with it. The receiving unit doesn't start from zero and doesn't ask the citizen the same questions again.
Putting the service standard on a clock
If legislation or an internal service standard sets a deadline, tracking it is not a manual job. Tixenta tracks first-response and resolution times; it warns before the clock runs out and raises an instant alarm on breach. Management sees the requests about to expire as a list; before the breach, not after.
An audit-ready record
Every state-changing action is logged automatically: creation, assignments, status changes, closure. The record cannot be edited afterwards. For an audit, an internal review or a freedom of information request, there is no document to produce; the record already exists.
Keep the data inside the institution
In public institutions, where data sits is usually a rule rather than a preference. Tixenta runs both as a cloud service (SaaS) and on the institution's own servers (on-premise). It is based in Türkiye, KVKK/GDPR compliant, with a Turkish and English interface and local support.
Affiliated entities and municipal companies
Municipal companies, affiliated agencies or separate legal entities don't need separate installations. Tixenta hosts multiple organizations under a single URL and isolates each one's data. Headquarters gets the consolidated report; entities cannot reach each other's data.
Make internal discussion part of the record
"Who will take this one?" is usually settled in a messaging group, outside the institutional record. Tixenta offers internal staff chat in the same platform; coordination happens inside the institution, next to the request.
Frequently asked questions
We already have a call center; does this replace it? No, it feeds it. The phone is a channel; what matters is that the call becomes a record sitting in the same pool as every other channel.
Does a citizen need to install an app to follow a request? No. An email address and a tracking code are enough.
Can it be installed on our own servers? Yes, on-premise deployment is supported.
Can several directorates see the same request? That depends on the authorization design; both isolation and shared visibility can be modeled.
Related reading
Tixenta unifies omnichannel intake, a guest ticket flow, fine-grained authorization and an immutable audit log in a single platform, available as SaaS and on-premise.