Route by request type
One dropdown at the top, one section per type. A print job and a landing page need different questions and neither requester should see the other set.
A work request form is the front door to a team that keeps getting asked for things in six different channels. Design, IT, marketing, facilities. The problem is always the same: requests arrive without the information needed to start them.
Opens the new-form flow, where the template picker is waiting. Free plan: unlimited forms, 100 responses a month.
A form fixes that by making the questions non-optional. Deadline, audience, format, budget, and what "done" looks like are asked once, at the point of asking, rather than reconstructed over two days of messages.
A starting point, not a rulebook: every question below is a real Questionful question type, and all of them are editable once the form is in your account.
| Question | Question type |
|---|---|
| What kind of request is this? The routing question, branch it to a section per request type if you need to | Dropdown |
| Who is asking? | Short answer |
| What do you need, in one sentence? | Short answer |
| Describe the request | Paragraph |
| When do you need it? | Date |
| How urgent is it? | Linear scale |
| Which deliverables do you need? | Checkboxes |
| Attach a brief or reference Paid plans | File upload |
| What does done look like? | Paragraph |
One dropdown at the top, one section per type. A print job and a landing page need different questions and neither requester should see the other set.
A date question instead of "ASAP". Half of triage is knowing which requests genuinely collide.
Give the urgency and impact questions point values and the request arrives with a number attached, so the queue sorts itself before anyone reads it.
Every submission POSTs as JSON to Zapier, Make, or your own endpoint: so a request can become a ticket, a card, or a row without being retyped.
Yes, via webhook. Each submission POSTs JSON with the form, the response, and every answer, so Zapier, Make, or your own service can create the ticket. Delivery happens inline with the submission and is logged on the form.
Yes on paid plans, up to 25 MB per file. The free plan does not accept respondent uploads.
Yes. That is the core of the template. A dropdown routes each type to its own section.
No. Questionful captures the request; tracking the work belongs in whatever the webhook feeds. Requesters can be given an emailed copy of what they submitted.
Route each answer choice to its own section, so people only see what applies.
FeatureEvery response POSTed as JSON to any endpoint, signed if you want it.
Feature19 types, including specialist ones most builders skip.
TemplateDates, type of leave, cover arrangements, and a record of the approval.
TemplateA clean contact-details form that routes the message to the right person.
TemplateAsk the budget, timeline, and fit questions before the first call.
TemplateCollect scope, budget and deadline once, instead of across nine emails.
Use caseTurn recurring internal requests (time off, IT tickets, purchase approvals) into structured forms with a real audit trail.
Use caseQualify enquiries while they are being filled in, and hand every submission straight to the tool your sales process already runs on.
Unlimited forms and 100 responses a month, free. Paid plans from €19.
No credit card required.
Choose which cookies you allow. Strictly necessary cookies are always on because the site cannot function without them.
Required for core features such as security, load balancing and remembering this cookie choice. These set no tracking cookies.
Google Analytics, used to understand traffic and improve the site. Loaded only if you allow it.