Forms that connect to your stack

Use cases

Pick the form you need and the tool it should feed. Every submission flows straight where your team already works — no Zapier tax, unlimited submissions, free.

Browse by tool

Browse by use case

Bug report

Collect reproducible bug reports — steps, expected vs actual, severity, and a screenshot — so engineering can triage without the back-and-forth.

Feature request

Capture the problem behind every ask, tagged by priority, so your roadmap is driven by real demand instead of the loudest voice.

Customer support

Turn a shared inbox into structured tickets — subject, category, priority, and details — that route to the right person every time.

Internal request

One intake for IT, ops, and access requests — typed and dated — so nothing falls through the cracks between teams.

Contact form

The classic name / email / message form — the fastest way to let people reach you without exposing an inbox to spam.

Lead capture

Qualify leads as they come in — budget, timeline, and intent — so sales spends time on the ones that are ready to buy.

Newsletter signup

A fast, clean email capture with optional name and GDPR consent — built to grow a list without scaring people off.

Waitlist

Build pre-launch demand and learn who your early users are — role, use case, and where they heard about you.

Job application

Collect applications with resume upload, links, and experience — a tidy pipeline you can review without a heavyweight ATS.

Event RSVP

Track who's coming, plus-ones, and dietary notes — with attending-only logic so you only ask what matters.

Customer feedback

Gather structured feedback you can actually act on — ratings, reasons, and open comments in one place.

Order form

Take orders with live price and total calculation — a lightweight checkout for products, services, or pre-orders.

NPS survey

Measure loyalty with the classic 0–10 question plus a reason — track your score over time without a survey tool subscription.

Quiz

Run a scored quiz with pass/fail routing — great for training checks, lead scoring, or interactive marketing.

Demo request

Qualify before the call — company size, use case, and timing — so sales shows up to every demo prepared.

Quote request

Scope the work up front — service, budget, and timeline — so every quote request starts qualified.

Appointment request

Let people request a time without the email tag — service, date, and notes captured in one step.

Incident report

Capture incidents the moment they're spotted — severity, affected services, and impact — so on-call can declare, track, and resolve without scrambling for detail.

Change request

A lightweight change-management intake — what's changing, the risk, and the rollback plan — so deploys and config changes are reviewed, not surprises.

Access request

Collect access requests with a justification and approver up front — the system, the level, and why — so IT and security can grant or deny with a paper trail.

IT helpdesk ticket

Turn 'my laptop's broken' into a routable ticket — category, urgency, and detail — so internal IT triages by priority instead of by who shouted loudest.

Vulnerability report

A responsible-disclosure intake for security findings — severity, affected component, and repro — so reports reach the security team instead of a public thread.

Design request

One front door for design work — deliverable, brief, and deadline — so the design team triages a real queue instead of fielding DMs.

Content request

Brief content work properly the first time — type, audience, and due date — so writers start with what they need and the queue stays visible.

QA test report

Log test results as structured records — case, pass/fail, environment, and notes — so failed runs become tracked work instead of a buried spreadsheet row.

Product idea

An always-open idea box for the team — the problem, the idea, and who it helps — so good thinking lands in the backlog instead of evaporating in chat.

Beta feedback

Channel beta-tester feedback into one structured intake — area, what broke, and severity — so signal from your early users becomes triaged work.

Work request

A single intake for cross-team work — what, why, and how urgent — so requests arrive as triable tasks instead of as-soon-as-possible favors.

Data request

Scope analytics and report asks before they hit the queue — the data, the purpose, and the deadline — so the data team triages instead of guessing.

Maintenance request

A clear intake for facilities and equipment issues — asset, location, and priority — so maintenance work is tracked to done, not lost on a sticky note.