Feature Request Submission
Roadmap intake capturing the problem, impact and willingness to beta test.
Bug reports, feature requests and technical intake.
21 free templates — preview any of them without an account, then customise every question, colour and layout.
Showing 1–21 of 21 templates · sorted by best match
Roadmap intake capturing the problem, impact and willingness to beta test.
Developer intake for sandbox credentials, scopes and expected call volume.
Internal troubleshooting request with asset details, impact and priority routing.
Agency intake covering site access, competitors, keywords and current channels.
A working example of branching: show, hide, require and page skip rules you can copy into your own form.
Reason-driven cancellation flow with a save-offer branch and confirmation of the effective cancellation date.
Structured beta program application covering platform, availability, NDA acknowledgement and feedback channel.
Procurement security review covering data handled, subprocessors, certifications, incident history and evidence upload.
Structured post-incident review covering severity, timeline, impact, root cause, action items and customer comms.
Qualify and onboard free trial sign-ups with company size, use case and a scheduled onboarding call option.
Structured in-app feedback with satisfaction, NPS and follow-up consent in eight questions.
Capture feature requests with the problem, workaround and impact — not just the idea.
Find out what users actually think of your app — usability, bugs, ratings and the one missing feature.
Request accounts for a new starter: who they are, start date, team and manager, what they need access to, equipment, and manager approval before setup.
Request a paid tool or seat: what the person needs to do, the tool and cost, who else would use it, data handled, and budget holder approval.
One-screen equipment request: what the person needs and why, where to deliver it, when it is needed, replacement or extra, and manager approval.
Three-page request to change a live system: what changes and why, who is affected, timing, testing and rollback, communications and approval.
Leaver access removal: who is leaving and when, what they had access to, equipment to recover, mailbox and file handover, and confirmation once done.
Request remote access to internal systems: who needs it and why, which systems, from where and for how long, the device in use, and who approves it.
One-screen request for a shared mailbox or group address: the address wanted, its purpose, who can send and read it, and who owns it long term.
Capture new project requests with the problem to solve, desired outcome, deadline, priority and budget status your team needs before it starts scoping.
Teams browsing this collection often start here too.