FixEcho
Open the app
Topics

How it works › Behind the scenes

How a report reaches the right service

Every case shows one line about where it is on this path. Tap “How this works” on a case to come here, with its step marked.

  1. Placed. The report is put on the municipality map; for roads, also which road it is (state, regional or local).
  2. Finding the service. FixEcho picks the responsible service from what it has learnt in this area. In an area that is new to us, it looks the service up on official websites and public registers.
  3. Checking a new service. A service found for the first time is accepted only when its address is on its own official site, that site is confirmed by an independent source (a public register or Wikidata), and a second AI model reviewing the evidence agrees. Where the sources disagree, a person on our team decides.
  4. Sent. One e-mail per service each working day, with the photo and the place — never your name.
  5. Reminded. After 3, 7, 14 and 30 days, then every month; where the law sets a deadline, FixEcho quotes it. A service that has not answered four messages hears from us once a month. Once it answers, the reminders slow down — 30 days after the answer (7 for a hazard), or 3 working days after the date it gave, then monthly (every three months after a refusal) — and only while someone on the spot says it is still there; they end when the fix is confirmed.
  6. Answered. “On it”, a date, “fixed” or “not ours” — with one click, or by e-mail, which FixEcho reads.
  7. Not theirs. The service names who it is, or FixEcho looks again — it never sends the case back to a service that said no.
  8. Fixed when people on the spot confirm it.

How FixEcho learns. Every answer teaches it: a service that acts or fixes counts for it, “not ours” strongly against it, months of silence a little. People can say a case went to the wrong service: that moves the case only when enough independent, trusted people agree, and it teaches FixEcho only once the service’s own answer proves them right — so a few accounts cannot steer where reports go.

When a person steps in. Only when the system is stuck: the sources disagree about a new service, two services both say “not ours”, people on a case disagree, an unclear reply has waited more than two working days, or a case has had no service for a week.