TotalApp Docs

Citizen Service Requests & Code Enforcement

How TotalApp turns a pothole report, an abandoned-building complaint, or a hotline call into a routed work order, a validated public lien, or a resolved ticket — with terminology that matches how your municipality actually names its own hotline.

How this group of screens works

The Citizen Service Requests & Code Enforcement group brings together the three screens that carry a citizen complaint from intake to resolution: Triage & Automated Service Routing, Nuisance Abatement & Public Lien Tracker, and Citizen Service Request Triage & Automated Dispatch.

All three run the same background pattern used elsewhere in Government Operations: a semantic search over the relevant standards — municipal service routing guidelines and issue taxonomies, or nuisance abatement acts and cost recovery law — followed by an AI layer that synthesizes what it means for the specific ticket or case in front of you: whether it's a duplicate of something already reported nearby, which department should own it, and what the legal recourse looks like.

The first and third screens share one detail worth calling out: they read and write the exact same ticket ledger. A request logged in Triage & Automated Service Routing shows up immediately in Citizen Service Request Triage & Automated Dispatch, and vice versa. What differs between them is how each one names things for the person using it — covered in their own sections below.

At a glance

  • Triage & Automated Service Routing — classifies incoming citizen reports, flags geographic duplicates, and auto-assigns a work order and SLA clock
    Screen ID: gov-311-triage-automated-routing · Doc path: /gov/311-triage-automated-routing
  • Nuisance Abatement & Public Lien Tracker — tracks municipally-performed cleanup/demolition costs through to formal cost recovery against the property owner
    Screen ID: gov-nuisance-abatement-public-lien · Doc path: /gov/nuisance-abatement-public-lien
  • Citizen Service Request Triage & Automated Dispatch — the same triage board, with a screen title that adapts to your municipality's own hotline branding
    Screen ID: gov-citizen-service-triage-routing · Doc path: /gov/citizen-service-triage-routing

1. Triage & Automated Service Routing

Call Classification & Automated Work Order Routing Board

Requests reported by citizens through the call center, web/mobile portal, or messaging channels — potholes, broken streetlights, illegal dumping, park and garden damage — are semantically classified against a location and topic library. The AI engine detects duplicate reports by geographic proximity, automatically assigns the resulting work order to the responsible department (Public Works, Code Enforcement, Parks & Recreation), and starts the statutory resolution SLA countdown.

Why this screen runs a background duplicate-detection check

The same pothole gets reported by five different residents through five different channels on the same day. A background check against the location and issue-category library flags when an incoming report is a geographic duplicate of one already on file, so field crews get one work order instead of five, and the SLA clock isn't reset by a follow-up call about the same problem.

At a glance

  • Screen ID: gov-311-triage-automated-routing
  • Doc reference path: /gov/311-triage-automated-routing
  • Path in the app: /government/311-triage

2. Nuisance Abatement & Public Lien Tracker

Derelict Property & Public Cost Recovery Tracking Screen

When a property owner fails to remedy a condition that threatens public safety — a derelict structure, an illegal dump site, an overgrown hazardous lot — and the municipality performs the cleanup or demolition itself, the resulting cost is semantically tracked back to the owner. The AI engine verifies the statutory notice period was observed, calculates the municipal remediation expense owed, and legally validates the process of recording unpaid costs as a public lien against the property's deed.

Why this screen runs a background notice-validity check

A public lien filed without properly observing the statutory default notice period can be challenged and thrown out, leaving the municipality to absorb a cleanup cost it was legally entitled to recover. A background check against the governing nuisance abatement acts and cost recovery regulations confirms the notice timeline held before the lien is drafted and attached to the deed.

At a glance

  • Screen ID: gov-nuisance-abatement-public-lien
  • Doc reference path: /gov/nuisance-abatement-public-lien
  • Path in the app: /government/nuisance-abatement

3. Citizen Service Request Triage & Automated Dispatch

Classification & Automated Service Routing Board

All requests submitted by citizens through the call center (311, or your municipality's own hotline), web portal, and mobile apps — potholes, broken streetlights, illegal dumping, noise complaints, and more — are semantically classified by service category. The AI engine detects and merges duplicate reports from the same area using geo-cluster matching, then auto-assigns the resulting work order to the responsible municipal department (Public Works, Code Enforcement, Parks & Recreation) and starts the statutory resolution SLA countdown live.

This screen shares its full ticket ledger with Triage & Automated Service Routing above — the same requests, the same AI diagnostic, the same dispatch action. The one thing that changes is the screen's own name: it reads your municipality's configured country and switches between “311 Service Requests & Triage”, “ALO 153 / Citizen Request Management”, or a neutral international title, so front-line staff see the vocabulary their residents actually use.

Why this screen's title changes by country

A dispatcher in a US or Canadian city thinks in terms of “311.” A dispatcher in Turkey thinks in terms of “ALO 153.” Rather than force one naming convention on every tenant, this screen reads your organization's country setting and presents the screen under the name your own staff already use for the hotline — while the underlying ticket data, AI diagnostic, and dispatch workflow stay identical to Triage & Automated Service Routing.

At a glance

  • Screen ID: gov-citizen-service-triage-routing
  • Doc reference path: /gov/citizen-service-triage-routing
  • Path in the app: /government/citizen-request-triage

Screen reference

ScreenScreen IDPath in the appBackground check
Triage & Automated Service Routinggov-311-triage-automated-routing/government/311-triageYes — service routing guidelines, issue classification taxonomy, spatial deduplication parameters
Nuisance Abatement & Public Lien Trackergov-nuisance-abatement-public-lien/government/nuisance-abatementYes — nuisance abatement acts, statutory notice periods, cost recovery regulations, lien attachment protocols
Citizen Service Request Triage & Automated Dispatchgov-citizen-service-triage-routing/government/citizen-request-triageYes — same as Triage & Automated Service Routing (shared ticket ledger)

Frequently Asked Questions

What's the difference between Triage & Automated Service Routing and Citizen Service Request Triage & Automated Dispatch?
They work on the exact same ticket data, run the same AI diagnostic, and offer the same dispatch action. The only difference is presentation: Triage & Automated Service Routing keeps a fixed title and only swaps the hotline-channel label by country; Citizen Service Request Triage & Automated Dispatch swaps its entire screen title by country. Use whichever one matches how your team refers to the workflow — a ticket created in one appears instantly in the other.
Does the AI diagnostic replace a dispatcher's or code enforcement officer's judgment?
No. It surfaces likely duplicates, routing recommendations, notice-timeline risks, and draft lien language for a human reviewer — it does not replace the dispatch decision or the legal sign-off your agency already requires before a lien is filed.
What happens after Dispatch Work Order or Attach Public Lien?
Dispatch Work Order commits the assigned department and advances the ticket's workflow state — it stays available, since a ticket can be re-routed more than once. Attach Public Lien freezes the final abatement cost, marks the case as lien-attached, and the action then disappears from that row, since a lien is filed once per case.
Do I need a special role to use these screens?
You need a Government domain role — these are Operational screens, not governance screens, so any role-holder can use them; only Roles and the Public Personnel & Bargaining Unit Roster require admin. See Roles & Capabilities.