Citizen Services9 min
Many citizen reports arrive with references like «across from the store» or «by the park», and the crew loses the visit searching for the spot. This article explains why location must be captured as data rather than as a description, and which operating rules make every report land on a verifiable point on the map.
Citizen Services8 min
Many municipalities measure how many reports they close, but few measure how often the same problem returns to the same place. This article explains why recurrence is the most useful signal citizen services leave behind and how to turn it into preventive maintenance and better investment decisions.
José Campillo
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.
José Campillo
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é CampilloA resident calls to report a streetlight that is out. The person answering types what they hear: "Hidalgo Street, by the park, across from the store." The report enters the system, gets a case number and is assigned to the street lighting crew.
The next day, the crew arrives on Hidalgo Street. There are two parks on that street and three stores. They walk the block, check the poles, and find no dark streetlight at a glance because it is daytime. The case is closed as "not located."
That night the streetlight is still out. The resident calls again, now angrier. To him, the municipality did nothing. To the municipality, the crew went out and did its job. Both are right, and both lost.
This is a problem that rarely shows up on citizen service dashboards: the report had an address, but it did not have a location. An address describes a place in words. A location pins it down as data, and that determines whether the crew reaches the right spot and whether the city's map tells the truth.
INEGI's 2025 National Survey of Government Quality and Impact (ENCIG), conducted in urban areas of 100,000 inhabitants or more, shows that several services that depend on a field visit are still poorly rated. Only 41.1% of the population aged 18 and over said they were satisfied with street lighting, down from 43.4% in 2023. Streets and avenues received the lowest average score of all basic services: 5.1 out of 10.
The same survey reports that only 10.9% perceive prompt repair of potholes and storm drains. We already looked at that figure from the angle of recurrence in a filled pothole is not a repaired street. Here we care about another side of the same problem: before anything can be repaired, someone has to find it.
When people describe a place, they use what they know: the store, the school, the house painted green, "where the tree used to be." Those references work between neighbors. They do not work in a system that has to assign, group, measure and compare thousands of reports.
A location that is useful for operations has at least three layers:
A point. Coordinates that place the report on the map without ambiguity. That is what makes it possible to calculate distances, see which other reports are nearby and assign the case to the right zone.
A normalized address. Street, number or cross streets, neighborhood, locality and postal code, always written the same way and taken from a catalog, not from whatever each operator manages to type. That is what lets a person read the case and understand it.
A reference to the asset, when one exists. The streetlight number, the water connection, the container or the street segment. That is what makes it possible to know that today's problem is happening to the same object that failed three months ago.
A report with all three layers is data. A report with a paragraph of references is a note someone will have to interpret, and every interpretation is a chance for error.
Mexico has a standard for this. On November 22, 2024, INEGI published in the Official Gazette of the Federation (DOF) the Technical Standard on Geographic Addresses, in force from the following day, which replaced the 2010 version. Its purpose is to set out the components and characteristics of the information that makes up a geographic address in order to identify any parcel or property, so that it is integrated into administrative records in a structured, systematic, standardized and consistent way.
The standard stresses a point that matters for citizen services: that records can be linked to one another. An address captured with the same components in the property tax roll, the street lighting catalog and the reporting system makes it possible to cross-reference information that today lives apart. An address typed freely into each system prevents it.
Adopting that logic does not require every citizen report to carry a perfect address. Many urban problems happen where there is no street number: a median, a bridge, a stretch of road, a vacant lot. It requires the system to distinguish which components were captured and which are missing, and for the point on the map not to depend on the address being complete.
Cities that connected their service lines to third-party applications reached the same conclusion years ago. The Open311 GeoReport v2 specification, an open standard that several cities use to receive urban service requests, establishes that every request must be submitted with a full location: a pair of coordinates (latitude and longitude, in the WGS84 system), a text address, or the identifier of an address in the city's own catalog.
The detail is telling. The specification requires coordinates to always be sent as a pair, because one alone is useless, and the text address to go from most specific to most general: number or cross streets, street, neighborhood, city and postal code. In other words, a standard designed so that different systems can talk to each other treated location as an entry requirement, not as an optional field filled in when there is time.
For a Mexican municipality, the lesson is not to adopt that standard as is. It is to understand that if a report can enter the system without a verifiable location, it will enter that way, and the crew will pay the cost.
When a report comes in by voice or in person, the location depends on what the operator understands and manages to write down. Without a map on screen to confirm the point with the person reporting, the verbal reference becomes text and stays that way.
In digital channels it is tempting to take the phone's position automatically. But someone reporting a leak from home may be two blocks away from the leak. If the system stores the device's position as if it were the problem's, the map fills up with points that are precise and wrong.
Hidalgo, Juárez, Morelos, 5 de Mayo. The same street name appears in several neighborhoods of the same municipality. If the neighborhood is typed by hand or left out, the report can be assigned to the wrong zone and travel between crews before anyone notices the mistake.
In new or informal settlements, many streets have no official name or number. There, a text address has nothing to hold on to, and the point on the map is the only way to get there.
The crew arrives, fixes the problem and closes the case. But if nobody records where the crew was when it closed, no one can verify that the work was done at the reported spot. And when a case is closed as "not located," that reason usually ends up in a comment rather than in a field that can be counted.
Fixing this does not require a cadastre project, just clear operating rules.
No report without a point. A report can come in with incomplete data, but not without a point on the map. If it arrives by phone or at the window, the operator places it and confirms it with the person reporting before generating the case number.
Confirm the point with the person reporting. In digital channels, the device's position is an initial suggestion, not the answer. The person must be able to move the marker to the exact location of the problem.
Addresses from a catalog. Neighborhoods and streets are chosen from a municipal list, aligned with official street naming and with the components of the INEGI standard. Free text is for additional references, not a substitute for the address.
Reference to the asset when there is an inventory. If the municipality has numbered its streetlights, water connections or containers, the report must be able to link to that object.
Record the arrival. The field work order must store the position and time at which the crew arrived and closed the case. Not as surveillance, but as evidence that the right spot was handled, for both in-house crews and contractors.
Measure "not located." Make it an explicit closure reason and review its frequency every month by channel, by zone and by operator. A high rate in one channel shows where intake is failing.
Deduplication becomes reliable. Ten reports of the same pothole are only recognized as one if they fall close together on the map.
Routing becomes automatic. If the point falls inside an operating zone, the case can be assigned to that zone's crew or contractor without a coordinator dispatching it by hand.
The heat map tells the truth. The territorial maps that public works departments use to decide where to invest are only as good as the points that feed them. Points taken from the reporter's phone, or dropped in the center of the neighborhood by default, draw a city that does not exist.
Contractor oversight has evidence. Knowing that the crew was at the reported spot when it closed the case is the basis for paying for work done rather than for status changes.
Agora, Intello's citizen services platform, is designed so that every report reaches the field with the information needed to handle it.
Omnichannel intake brings together in a single system everything that comes in through web, app, chat, phone and service window. Automated intelligence, with deduplication, classification and data extraction, organizes what comes in.
Geolocated work orders give the crew all the case information, and in-house crews and external providers work on the same platform. Full traceability records who did what, when and with what result.
On that foundation, real-time dashboards and territorial heat maps show where reports are concentrated, and the public dashboard lets the municipality show residents active cases, resolved cases and performance metrics.
If several answers are no, the municipality is paying for visits that solve nothing and building maps on data it cannot defend.
A citizen report is a promise that someone will go to a place to fix something. If the place is ambiguous, the promise is broken from the start, no matter how good the crew is. Treating location as mandatory, verifiable data linked to the asset is an operational design decision, not a form detail, and it is one of the cheapest a municipality can make so that its services reach the places that need them.
If your municipality wants every report to reach the field with a clear point and stay traceable until it is closed, see how Agora works, learn how Tribuna applies the same logic to public safety and civic justice, or request a demo.