Built for public works and resident services
Every report lands with the right crew.
Every resident hears what happened.
A resident takes a photo, drops a pin, and describes the problem in their own words. Resident Requests identifies what kind of issue it is, checks whether it has already been reported, routes it to the department and crew responsible for that location, and keeps the resident informed until the work is closed. Your staff decide what is done and when, and every step is on the record.
- Photo and map on every report
- Duplicates merged
- Routed by location and type
- Residents kept informed
What it changes for your office
Residents report problems everywhere. The work only starts when it reaches a crew.
Requests arrive by phone, by email, through a council office, and on social media. Staff retype them into a work order system, residents call back to ask whether anyone came, and the same streetlight is reported eleven times. Resident Requests gives every report one front door, one record, and one path to the people who fix it.
For the call center and front desk
Staff take a phone report in the same form residents use online, with the map and the categories already in place. They no longer decide which department owns a location, because the routing rules do that, and when a resident calls to ask about a request, the status and the crew notes are on the screen.
For crew supervisors
Supervisors receive requests already sorted by type and location, with duplicates merged and photos attached. They plan the day from a map of open work, assign crews, and close requests with a photo of the finished repair, and the resident is told without anyone writing an email.
For council offices and the city manager
Every request carries its council district, so a council member can see what was reported in their district, how long it took, and what remains open. The city manager can see where service targets are met and where a department needs more capacity.
The product
Autessa Resident Requests, what your team works in.
Intake and Duplicate Detection
Each report is read for what it describes, where it is, and when it was seen. When another open request covers the same problem at the same place, the new report is linked to it rather than becoming a second work order, and the new resident is added to the list of people who receive updates. When the system is not sure that two reports describe the same thing, it asks a person.
Routing and Assignment
The service catalog your city maintains says which department owns each kind of problem, and the map says which crew covers each area. A pothole on a city street goes to Streets, a pothole on a state route goes to a staff member who refers it on, and a missed pickup goes to the hauler for that route. Supervisors can reassign any request, and the reason is kept.
Resident Updates
Residents receive a message when their request is received, when it is scheduled, and when it is closed, in the language they chose and by the channel they prefer. When a request is closed without work, such as a pothole on a private road, the resident is told why and who to contact. Staff write the closing note, and the system sends it.
Service Targets and District Reporting
Every request type carries the service target your city has set, and every request shows how long it has been open against that target. Department heads see what is about to slip, and council offices see the same figures for their own districts. The reports come from the work itself, so nobody assembles them at the end of the month.
In practice
The details that decide whether residents trust the system.
Three of them, handled the way a public works department already handles them: who owns the problem, what counts as done, and how residents are treated when the answer is no.
On ownership
Every request has one owner at every moment
A request is always assigned to a named department and, once scheduled, to a crew or a person. When the routing rules cannot decide, such as a location on a boundary between the city and the county, the request goes to a staff member rather than waiting in a shared inbox.
On closure
A request is closed by the person who did the work
The system does not close requests on its own. A crew member or supervisor closes each one with a note and, where your department requires it, a photo of the finished work, and a resident who disagrees can reopen it within the window your city sets.
On referrals
A request outside the city is referred, not dropped
When a problem belongs to another agency or a private owner, the resident is told who is responsible and how to reach them. The referral is recorded on the request, so the city can show what it received and where it was sent.
Below: a request the routing rules would not assign on their own, because the location sits on a jurisdiction boundary.
Defensibility
When a resident or a council member asks what happened, the answer is a lookup.
Resident requests become public questions quickly. A council member asks why one district waits longer than another, a resident says they reported a hazard weeks before an accident, or a reporter asks how many streetlights are out. The question is not only whether the work was done. It is whether the city can show when it knew, who was responsible, and what it did.
Resident Requests keeps that record as it works. Every report records what the resident submitted, the category and location, any merge with an existing request, the routing decision and the rule behind it, every reassignment, and the person who closed it. The log is append-only, so the timeline produced for a council meeting or a claim is the one recorded at the time.
One pothole report, from the photo to the finished repair.
The same record across a district, ready for a council briefing.
See it route your own requests.
Bring a month of the requests your city received and the list of who handles what. We will set up Resident Requests with your service catalog and walk your staff through how each request would have been merged, routed, and reported.
FAQ
Questions we are glad to answer.
Does it replace our work order system?+
It does not have to. Resident Requests can create work orders in the system your crews already use and receive their status back, or crews can work directly in it. Either way, the resident sees one request from start to finish.
How does it decide where a request goes?+
It follows the service catalog and the map your city maintains, which say which department owns each type of problem and which crew covers each area. When the rules do not give a clear answer, the request goes to a staff member to assign.
Can residents report by phone or in another language?+
Yes. Call center staff enter phone reports in the same form residents use online, and residents can submit reports and receive updates in the languages your city supports.
Will it close requests automatically?+
No. Requests are closed by the crew member or supervisor who did or reviewed the work. Duplicate reports are linked to an open request, and a staff member can split them apart if the link was wrong.
Where does our data go?+
Resident Requests runs in your own Autessa Private Cloud, an environment your agency controls, with keys your agency holds. Resident reports, photos, and contact details are not used to train models for anyone else.