Pick a flow type, preview a working example, then copy the config or open it in your dashboard. No maze of filters, just the useful starting points.
Showing 4 of 39 templates.
The default "report a problem" shape — bug / abuse / spam / privacy / other. Five categories is small enough that triage is fast but wide enough that almost nothing gets shoved into "other". Best as the universal entry point linked from a settings menu or help screen.
Designed for surfaces with user-generated content — comments, posts, profiles. Categories mirror App Store Connect's report taxonomy so what you collect lines up with what review boards expect. Email is OPTIONAL by default — reporters often want anonymity.
For technical apps where reporters can describe what they tried. Categories split by impact (crash / wrong-result / slow / visual-glitch) so engineering can route by severity. Email is REQUIRED — bug triage almost always needs a follow-up question.
For apps with transactions between users. Categories cover the marketplace failure modes — fraud, scam listings, no-show sellers, payment issues — plus a counterparty contact info ask in the prompt. Email required; we'll need it to investigate either side.