By unifying public space management on District360 and connecting public reports through a See Say integration, Downtown Dallas Inc. cut response times by 75%, eliminated dispatcher phone relays, and gave the board an evidence-based view of every shift.
Schedule a Demo
Downtown Dallas Inc. partnered with District360 to bring four field teams onto one platform, replace paper logs and disconnected tools, and give leadership an evidence-based view of every shift across the district.
A unified system for field operations used by everyone on the team, from ambassadors and assistant managers to directors and the VP of Homeless Services. Custom workflows for all four field teams sit alongside an automated public reporting pipeline that routes See Say reports straight to the crews who can respond.
Ambassadors are resolving nearly three times as many cases per shift, response times to public reports dropped by 75%, and the dispatcher’s manual relay workflow was significantly reduced.
Downtown Dallas Inc. is the principal advocate, champion, and steward for downtown Dallas. Every morning, four field teams fan out across the district. Clean crews begin their routes. Safety officers coordinate with Dallas Police. Homeless Outreach workers check on people they have been building trust with for months. Ambassadors activate parks, greet visitors, and check in with local businesses.
For years, most of that work disappeared into paper logs and disconnected tools the moment a shift ended. Each team used its own system. None of the systems talked to each other. Supervisors could not easily confirm where crews worked, how long they spent in each location, or which areas asked for attention again and again.
Public reporting was the hardest part. When a resident submitted a request through the See Say app, the report appeared in a separate Elerts dashboard. To act on it, a dispatcher had to:
Travel was inefficient, updates lived in radio chatter, and every month, leadership compiled board reports by hand from systems that did not match. The work itself was excellent. What was missing was a way to see all of it at once, so teams could learn from it, supervisors could support it, and the board could understand it.
Today, the four teams work as one, with every activity connected and visible in a single system.
District360 worked alongside the Downtown Dallas team, learning each function before designing for it. Clean has its own rhythm. Safety operates with its own incident vocabulary. Homeless Outreach is built on relationship-based work. Ambassadors live in the public, activating parks and supporting merchants. Forcing all four into one generic form would have failed.
Instead, the platform was set up around the way each team already worked. The District360 platform became the system of record for properties, contacts, service requests, and reporting. District360 Streets, our mobile platform for public space teams, became the daily companion for field ops across ambassadors, safety, clean, and homeless outreach, with structured forms, photo capture, location data, site timers, and a real-time dashboard for supervisors and leadership. Together, they form a single source of truth that respects four distinct workflows.
The most visible change came from integrating Elerts with District360. The moment a resident submits a See Say report, a case is now created instantly inside the platform and surfaces in Streets in real time. Supervisors see where every ambassador is across the district and assign each case to the closest available person with one click. Status updates flow back to Elerts automatically, keeping public-facing reporting and internal operations in sync.
The dispatcher’s manual relay workflow was significantly reduced. Radio coordination is still used for moments when a push notification might be missed in the field, but the default path is now app-driven, with an 8:10 on-site arrival flowing into an 8:20 case completion and status landing back in Elerts automatically. The story leadership tells the board changed at the same time. With every report, every case, and every interaction syncing into one platform, monthly reporting moved from anecdotal compilation to evidence-based dashboards built on real coverage data, response patterns, outreach outcomes, and hotspot trends that help the Safety and Clean teams decide where to focus next.
Most districts stitch together a patchwork of tools. District360 puts every function your organization runs onto one connected platform.
Start a conversationAfter integrating with District360, Downtown Dallas measured the difference at every step of the public-report workflow.
The downstream effect on day-to-day productivity was even more striking. Before District360, an average ambassador completed about nine cases in an eight-hour shift, with most of the time spent on coordination, travel, and waiting for assignments. After District360, with smart dispatching and auto-logging, that number rose to roughly twenty-six. Almost three times the output, with the same team and the same shift length.
Six years in, the partnership keeps evolving alongside the team. The work keeping downtown clean, safe, welcoming, and activated has not changed. What has changed is that all of it now lives in one place.
Most districts already have a way for residents to flag issues, whether that is a city-run 311 line, a resident-facing app, a community email inbox, or social media. The friction is rarely getting the report in. It is getting the report to the person who can act on it before the issue grows cold. District360 is built to integrate with those inbound channels, so a public submission lands as a real case inside the platform rather than a ticket stranded in a separate dashboard.
At Downtown Dallas, that meant wiring Elerts into District360. The moment a resident submits a See Say report, a case is created in the platform, routed to the closest available ambassador, and synced back to Elerts with a status update when it closes.
Most place management organizations run more than one kind of field work, and trying to squeeze every team into a single form is usually where deployments fail. Clean crews track different things than Safety officers. Outreach teams do relationship-based work that does not fit an incident log. District360 treats each function as its own workflow, with its own categories, capture fields, and reporting, while keeping every team on the same platform so supervisors see one picture of the district.
Downtown Dallas runs four field teams on District360, Clean, Safety, Homeless Outreach, and Ambassadors, each with its own structure, and none of them squeezed into someone else’s form.
If the numbers in a case study depend on someone remembering how the month went, they are not worth much. Every case inside District360 is timestamped from the moment it is created, through acknowledgment, on-site arrival, and close-out. Location data, photo evidence, and team assignments are captured as part of the same record. Productivity metrics fall directly out of that operational data instead of being reconstructed at month-end, which is how response times, case counts, and hotspot trends become defensible numbers rather than rough estimates.
The role does not disappear, it shifts. Before automated dispatch, the coordinator acted as a human switchboard, reviewing reports, calling ambassadors, relaying details by radio, and phoning back to confirm completion. Most of that work is now handled by the platform. Cases route to the closest available responder, status updates are visible in real time, and close-outs are captured automatically. The human role moves up the stack, toward operational oversight, watching coverage patterns, reallocating resources when something spikes, and coordinating with city partners. The day looks less like relay and more like command, seeing where every team is across the district and deciding where attention needs to go next.