Report flows

Give users a clean way to flag problems.

A hosted report form with a category picker — bug, abuse, spam, privacy, or your own list — plus a message and an optional email. Reports land triaged in your dashboard so nothing gets lost.

Report an issue
🐞 Bug
🚫 Abuse
🧹 Spam
🔒 Privacy
Submit report
🏷️

Category routing

Define 1–10 categories; each report is tagged so you can sort bug reports from abuse at a glance.

🛡️

Safety-ready

A standard 'report content' surface — useful for App Store UGC compliance and trust & safety.

📊

Triage in one place

Filter by category, read details, export CSV, and follow up via the optional reply email.

How it works

Triaged reports in three steps.

No backend, no build. Define categories, publish, share the URL.

  1. 1Define
  2. 2Receive
  3. 3Triage
  1. 1

    Define categories

    Set your report types (bug, abuse, spam, billing…) and the success message. Publish.

  2. 2

    Users file reports

    Link it from your app or App Store listing. Each submission is validated against your live config.

  3. 3

    Triage & resolve

    Sort by category in the dashboard, export, or pull reports via the API / MCP.

Built for AI agents

Or let your coding agent build it.

Install the MCP server once. Then your agent (Claude, Cursor, Codex, …) creates the app, builds this flow, and publishes it — typed tools, no clicking around.

Prompt: “let users report problems
Add a 'report a problem' flow.
Categories: bug, abuse, spam, billing.
Require a message; email optional.
Publish.
You get

Reports triaged by category.

update_report_draftpublish_report_flow
Read the agent guide →

Ship it in minutes — or let your agent do it.

Hosted, App Store–safe, and buildable from the dashboard, the REST API, or the MCP server.