Skip to main content

Give residents a reporting channel that actually routes

Reports arrive by phone to whoever answers, by email to a general inbox, and by social media to nobody. Categorisation happens never, and urgent things queue behind lost-cat posts.

The short way: One structured intake — category, location, photo — with the duty team told within minutes and everything counted by category and area.

Type this — that’s the whole job

“A community issue report form: issue category, location, description, photo upload, and how urgent it seems”

Build it now — free

No setup, no tutorial. The words above go with you — review what the AI builds, then share the link.

How it works — three steps

  1. 1

    List your categories; the AI adds location, photo and urgency fields.

  2. 2

    Turn on the link's response alerts every minute, with the duty inbox copied in.

  3. 3

    The category-by-area counts become the monthly operations report.

What’s doing the work

Photo uploads

The pothole arrives with its portrait — dispatch stops guessing severity.

Response alerts

The duty inbox hears within minutes that reports are in; filter by category to put 'Safety hazard' first.

Anonymous option

Reports about neighbours come in only when reporting is consequence-free.

Questions people ask

How do we stop duplicate reports of one pothole?

You don't want to — duplicate volume IS the priority signal. The category+location counts turn duplicates into ranking.

Can reporters get a follow-up?

An optional contact field gives you an address to reply to; anonymous reporters simply skip the field.

Minutes, not weeks. That’s the deal.

Start free