Updated September 6, 2026. Originally published June 20, 2023.
Residents expect to report a problem, get a reference number, and see something happen. That expectation used to belong to big cities with a 311 line. It now belongs to every municipality, including the ones with a single clerk on the front desk and a public works crew of four.
The trouble is that the tools built to meet it were designed for cities of hundreds of thousands. This post looks at what a dedicated 311 system actually involves, what a small or mid-sized municipality actually needs, and how a civic relationship platform closes that gap at a price that fits a budget line rather than a capital project.
What a dedicated 311 system actually involves
311 began as a phone number: a single, memorable line for non-emergency city services, staffed around the clock. Everything that grew up around it reflects that origin.
- A call centre. The core of a traditional 311 operation is people answering phones, with the staffing, training, scheduling and telephony that implies. The software is often the smaller part of the bill.
- Enterprise integrations. 311 platforms are typically wired into a city’s asset management, work order, GIS and financial systems, each with its own implementation project.
- Per-seat licensing and professional services. Pricing models assume dozens or hundreds of agents, and the configuration work is usually scoped as a consulting engagement measured in months.
- A citywide launch. A 311 number is a public commitment. Cities market it, staff it, and measure it, which is exactly right for a city and exactly wrong for a town that needs something working next quarter.
None of that is a criticism. For a large city, the call centre model is the point: it takes pressure off departments by putting a trained person between the resident and the crew. The mismatch is one of scale. As Government Technology observed, scaling 311 down to smaller communities has never been straightforward, because the approach was never designed to be small.
What a small or mid-sized municipality actually needs
Strip the call centre away and what a municipality of 3,000 or 30,000 residents needs is surprisingly consistent. We hear the same list in almost every conversation with a CAO, a clerk or a public works director.
- Intake through the channels residents already use. A form on the website, an email address, a phone call logged by whoever answers it, and increasingly a text message. Not a new number to advertise.
- Routing to the right person without a hand-off. A pothole report should land with public works, a barking dog with bylaw, and a tax question with finance, automatically, without a sticky note crossing a desk.
- Visibility and accountability. Who has it, how long have they had it, and what happens if nothing happens. The most common reason a resident calls back is that nobody can tell them.
- A record. Every request, every note, every photo, every response, kept in one place, so the history survives staff turnover and a Council question can be answered from the system rather than from memory.
- Reporting that fits a Council agenda. Volumes by category, response times, hot spots on a map, in a form a department head can put in front of Council without a week of spreadsheet work.
Notice what is not on the list: a phone bank, a marketing campaign for a new number, or a systems integration programme. That is the whole opportunity.
The 311 alternative: a civic relationship platform
A civic relationship platform does for a municipality what a CRM does for a business. It treats every interaction with a resident as part of one relationship, rather than as an isolated ticket, and it is built for the size of team that will actually run it.
In practice that means three connected pieces working together:
- Citizen management. Who your residents are, how they prefer to be reached, and everything they have ever raised with you, in one profile.
- Case management. Every request captured from any channel, categorised, assigned, tracked to resolution, with tasks, due dates, notes and attachments along the way. This is the part that replaces the 311 ticket.
- Engagement. Getting information back out: status updates to the resident who reported the issue, notices to a neighbourhood, and the two-way conversation that stops the second and third phone calls.
The difference from a 311 system is not a shorter feature list. It is that the platform assumes the resident will report the issue themselves, that a small team will handle it, and that the system, not a call centre, does the routing, the reminders and the record-keeping.
What it looks like in practice
The clearest way to see the difference is to hear how municipalities actually use it. These are drawn from our recorded webinars with customers in New Brunswick and Alberta, which you can watch in full.
Tracking every request end to end. The Village of Salisbury, New Brunswick, expected to use the platform mainly as a public-facing tool. What they found was that the biggest value was internal: making sure every request that came in was seen through, and having a record of it at the end. Their CAO described it as the end of handing the sticky note across the desk.
Meeting residents where they are. The City of Campbellton, New Brunswick, serves an older population comfortable with the telephone. Rather than force everyone online, they printed cards with a QR code that takes residents straight to the reporting form, while the clerk keeps logging calls into the same system. Both paths land in one queue.
Accountability and institutional memory. The Town of Shediac, New Brunswick, adopted the platform for two reasons: accountability and historical knowledge. Before, a call to the receptionist became an email to whoever was responsible, and then nothing. Now the receptionist, who used to take the second, third and fourth call when nothing happened, is the system’s biggest champion.
Starting in one department and growing. Brazeau County, Alberta, began with public works and expanded from there, and the Town of Ponoka turned on the pieces that mattered to them first. Nobody launched everything on day one, and nobody needed to.
Watch the conversations in full: AccessE11 for New Brunswick and AccessE11 for Alberta. For what has changed in the product this year, see the Case Management update walkthrough.
What it costs, and what it does not
AccessE11 is built and priced for small and medium municipalities. It is licensed annually, priced by the population of the municipality, with a one-time setup fee. There are no per-seat charges, so adding a department or a seasonal crew does not change the bill, and there is no professional services engagement to get started. Ask us for the band that applies to your municipality and we will come back with a number, not a sales process.
The comparison that matters is not the licence line alone. It is that the licence is most of the cost. There is no call centre to staff, no telephony to procure, and no integration programme to fund before the first request is logged. Where a municipality already has an asset or work order system, AccessE11 connects to it through its API, but that is an option, not a prerequisite.
Where a dedicated 311 system still makes sense
Fairness matters here. If you are a city with a genuine 24-hour call volume, multiple agencies sharing one front door, and the budget to staff a contact centre, a full 311 operation is the right tool and a civic relationship platform is not a substitute for it. The point of this post is not that 311 is wrong. It is that most municipalities in North America are not that city, and the tools built for that city were never meant to scale down to them.
Frequently asked questions
Is a civic relationship platform the same thing as 311 software?
No. 311 software is built around a staffed call centre and citywide integrations. A civic relationship platform assumes residents report issues themselves through the web, email, phone or text, and that a small team resolves them, with the system doing the routing, reminders and record-keeping.
Do residents have to download an app?
No. Residents report through your website, by email, by phone to your existing staff, or by text message. Staff can use a mobile app in the field, including offline, but nothing is required of residents beyond what they already do.
How long does it take to get running?
Most municipalities are live within weeks, not months, because there is no call centre to build and no integration programme to complete first. Many start with one department and expand from there.
Can it connect to our existing work order or asset system?
Yes, through the AccessE11 API, when and if you want it to. It is not required to start.
What size of municipality is it built for?
AccessE11 is built and priced for small and medium municipalities, from villages with a single administrative office to regional municipalities with several departments. Pricing is by population, so it scales with the community rather than with the number of staff using it.
See it for yourself
The fastest way to judge whether a civic relationship platform fits your municipality is to watch one run. Our walkthroughs are an hour, free, and built around your own scenarios rather than a script. If we finish early, the rest of the hour is yours.
Book a walkthrough, or read how it works for elected officials, town managers and customer service teams, and see who already uses AccessE11.