Service Requests
Public intake for service requests — potholes, dead trees, broken streetlights. Geo-pinned reports, auto-routed to the right crew, closed with a reply.
Open service-request queue with status filters and SLA pills. Staff view.
Residents submit geo-pinned reports with a photo from the resident portal. Auto-routed by district to the right department. SLA timers per category. Closes the loop with status updates back to the resident.
What you can do with service requests.
Geo-pinned reports with photo upload from the resident portal
Auto-routing by district, category, and on-call schedule
Per-category SLA timers (potholes 5d, downed tree 1d, etc.)
Status updates back to the resident by email or SMS
Heat map of recurring complaints by street and category
One-click conversion to a work order with the asset record attached
Service Requests — answered.
The questions we hear most when towns are evaluating this module. Anything specific to your charter, your state, or your existing vendor — we'll answer on the discovery call.
01 How do residents submit a request without creating an account? +
02 How does a request get to the right department? +
03 What happens when the SLA timer runs out? +
04 Can we close a request without converting it to a work order? +
The modules service requests talks to most.
Work-order dispatch, scheduling, status updates. Linked to the asset, the request, and the budget line — the public works crew's whole day on one screen.
GIS for small towns — every parcel one click from its tax bill, permits, complaints, and utility account. No separate ESRI license, no separate vendor.
Email, SMS, and push to residents — snow closures, water main breaks, meeting reminders. Multilingual, audience-segmented, with delivery receipts.
Run your town
on one system.
Thirty-minute discovery call with the actual builders. Bring last month's spreadsheets; we'll bring the questions.