Citizen Services9 min
Most municipalities already confirm that a report was received, but almost none show what happens next. This article explains why operational transparency, with statuses, evidence and public data drawn from the same workflow, is the most direct lever for rebuilding trust in municipal services.
Citizen Services7 min
A citizen-service platform does not mature when every report receives a case number. It matures when classification, location, deduplication, department ownership, SLA logic, field evidence, and follow-up operate through governed routing rules.
José Campillo
Citizen Services7 min
Municipal service deadlines only create value when they are tied to ownership, evidence, escalation, citizen communication, and operational correction. This article explains why SLAs in citizen service must behave like governance rules, not countdown clocks.
José Campillo
Citizen Services7 min
Municipal citizen service does not become reliable when a report receives a folio or a status update. It becomes reliable when intake, routing, field execution, evidence, closure, citizen follow-up, and analytics operate as one verifiable loop.
José Campillo
Citizen Services8 min
When the same streetlight, pothole, or leak enters by phone, app, chat, and service desk as four different records, the municipality does not see demand clearly. It sees noise. This article explains why case identity and deduplication are operational prerequisites for reliable routing, SLA management, and service analytics.
José Campillo
Citizen Services9 min
A citizen portal does not transform municipal operations on its own. The real shift happens when reports, routing rules, departments, crews, contractors, evidence, and SLAs operate on top of the same case. This article explores why that interoperability layer has become an operational requirement for local public services.
José Campillo
Citizen Services8 min
Outsourcing crews, concessionaires, or external vendors does not remove municipal accountability. If acceptance, evidence, SLA tracking, and closure live in emails, PDFs, or separate portals, the institution loses traceability, contract control, and the ability to answer citizens with rigor.
José CampilloA resident reports a broken streetlight on her block. She gets a message with a case number and the phrase "your report has been received." Two weeks go by. The streetlight is still out, or maybe it already works, but nobody told her. When she calls again, the person who answers does not know what happened to the case.
From the municipality's point of view, the report was handled: it entered the system, it was assigned, and perhaps a crew already did the work. From the resident's point of view, the government did not respond.
That gap between what the institution does and what the public gets to see is one of the most expensive problems in municipal citizen services. Not because the work does not exist, but because it stays submerged. And what cannot be seen, as far as trust is concerned, did not happen.
An acknowledgment confirms that the report arrived. An answer shows what was done with it.
The 2025 National Survey on Government Quality and Impact (ENCIG) by Mexico's national statistics institute, INEGI, published in May 2026, offers an uncomfortable picture of how the urban population perceives the services that depend on the municipality.
Among basic public services, streets and avenues rank worst: only 23.7% of people aged 18 and over living in urban areas of 100,000 or more inhabitants said they were satisfied, down from 27.2% in 2023. Street lighting fell from 43.4% to 41.1%, and parks and gardens from 43.3% to 42.0%. On a 0 to 10 rating scale, streets and avenues scored 5.1 and street lighting 6.1.
There is an even more revealing figure. When the survey asks about specific characteristics of the streets and avenues service, only 10.9% of the population says potholes and storm drains are repaired promptly, compared with 13.1% two years earlier.
And when the ENCIG measures satisfaction with procedures and requests people made in person, requests for municipal services (paving, street repair, street lighting, park maintenance, water trucks) show 38.9% satisfaction, below emergency medical care and emergency calls to the police.
These numbers do not say that municipalities are not working. They say that asking the municipality for something is, for most people, an unsatisfying experience. Part of that dissatisfaction comes from the service itself. Another part comes from not knowing what happened.
The OECD Survey on Drivers of Trust in Public Institutions in Latin America and the Caribbean, with results published in 2025 and covering Mexico, provides the other half of the argument.
According to that study, 43% of respondents in the region believe a public service would improve if many people complained about it. That is less than half, but the OECD highlights something important: people who believe their feedback leads to improvements tend to place more trust in local government and the civil service. The report's regression analysis finds that this perception is associated with a higher likelihood of high or moderately high trust in local government.
The OECD's recommendation is direct: track service performance metrics and strengthen feedback loops that connect what people report to decision making, so that improvements are visible.
The key word is visible. For most people, the most frequent contact with local government is not an election or a social program. It is a pothole, a leak, a streetlight or an illegal dump. If that contact ends in silence, people learn that reporting is pointless.
There is empirical research that measures exactly this effect. Ryan Buell and Michael Norton of Harvard Business School, and Ethan Porter of George Washington University, studied what they call operational transparency: designing the service interaction so that the public can see the work government normally does out of sight.
In one of their studies, Boston residents interacted with a website that visualized service requests, such as potholes and broken streetlights, along with the city government's work to resolve them. Those residents became 14% more trusting and 12% more supportive of government than those who did not see that information.
The most interesting finding for a decision maker is a different one. One group was also shown the growing backlog of requests the government was failing to resolve. That group ended up no less trusting than the group that received no transparency at all. Showing what was pending, alongside the work done, did not penalize trust.
In another study, using data from the Boston city government's own mobile app, users who received photos of the government addressing their requests submitted 60% more requests, in 40% more categories, over the following 13 months than users who did not receive those photos. The effect persisted for months.
The conclusion is practical: a photo of finished work is not a communications flourish. It changes people's willingness to keep reporting, and a municipality that receives more and better reports sees the problems in its territory sooner.
In daily operations, a lack of transparency is rarely a decision. It is a consequence of how the workflow is built.
The case says "in progress" for weeks because nobody updates the system when the crew goes out to the field. Or it says "closed" because someone closed a batch of cases at the end of the month. The status exists, but it does not describe what happened on the street.
The crew takes a photo of the repaired pothole and sends it to a messaging group. The photo proves the work, but it is not linked to the case. For the public and for the comptroller's office, that evidence does not exist.
If notifying the resident is a manual task, it gets done when there is time. In high-volume weeks, which are exactly the weeks when the most people report, nobody notifies anyone.
Some municipalities publish service figures. The problem is how they produce them: someone exports data, cleans it in a spreadsheet and uploads it to a portal once a month. Those figures do not match what the operations team sees, they are not kept up to date, and nobody can trace a dashboard number back to the cases behind it.
For fear of criticism, what was resolved gets published and what is pending gets left out. As the Boston evidence shows, hiding the backlog does not protect trust. What does damage it is the public discovering on its own that the dashboard does not tell the whole story.
Operational transparency is not a nice-looking portal or a social media campaign. It is a property of the workflow: what the public sees comes from the same record the institution operates on.
In practice, it involves at least five things.
The case changes state when something verifiable happens: it was assigned to an agency, the crew accepted the work order, arrived on site, finished the job, a supervisor validated it. Not when someone remembers to move it.
The photo, the field note or the inspection record stays attached to the case it resolved. That way the closure can be reviewed, and the same evidence can be shared with the person who reported it. We cover this in depth in Closing the loop in citizen services.
When the case changes state, the person who reported it receives the update through the channel they used. If the case is reassigned or delayed, they are told as well. A "we are still working on this, the estimated date has changed" builds more trust than silence.
Public figures, such as cases received, resolved and pending, and response times by service type and area, are calculated on the same cases the operations team manages. Every number can be broken down to the cases that make it up, with the appropriate privacy safeguards.
A dashboard that only shows what was resolved is advertising. One that also shows the backlog, with its age and location, is an accountability tool and, for management, an operational tool.
When the status reflects the real work, management stops learning about problems from social media or a council member's phone call. When the evidence is linked to the case, supervising crews and contractors no longer depends on anyone's word. When notifications go out on their own, the contact center receives fewer "what is happening with my report?" calls, which resolve nothing and consume operators' time.
Agora, Intello's citizen services platform, is designed around this idea: what the public sees and what the municipality operates come from the same system.
Agora brings omnichannel intake (web, app, chat, phone and walk-in counter) into a single workflow, with deduplication and automatic classification so the same problem does not turn into ten cases. It keeps full traceability for every case: who did what, when and with what result. It manages geolocated work orders for in-house crews and external contractors on the same platform, so field progress is recorded in the case.
On that foundation, Agora includes a public dashboard with active cases, resolved cases and performance metrics, so the municipality can show with data that it is working. For management, it offers real-time dashboards, territorial heat maps and performance metrics that show what works and what needs adjusting.
The point is not to have one more dashboard. It is for the public dashboard, citizen follow-up and internal management to stop being three different versions of reality.
Before investing in a new portal, it is worth answering honestly:
If several answers are no, the problem is not public relations. It is how the service workflow is built.
An acknowledgment is the start of a conversation, not its end. Municipalities that turn every report into a visible answer, with real statuses, evidence and public data drawn from the same workflow, will have residents who report more, trust more and better understand what their government does.
If your municipality is reviewing how it keeps residents informed about urban services, see how Agora connects intake, field work, evidence and public transparency, see how Tribuna applies the same traceability to public safety and municipal justice, or request a demo.