Service request form
A service request exists to be routed, not just logged. Request type and urgency are the two fields that decide where it goes; everything else is context. This form works for internal requests and customer-facing ones — the fields stay the same, only the request types change. A support desk and an internal IT queue use the same shape.
The form beside this text is live. Fill it in and submit it — it validates exactly as it would for a real respondent, and saves nothing.
Request type as a dropdown, not a free text box
A select field for request type — support, billing, technical, other — means requests arrive pre-routed to the right queue before anyone reads them. Free text produces "help", "question", and dozens of micro-categories you have to group by hand.
Urgency as radio buttons that route the response
A radio group asking how fast an answer is needed — routine, soon, urgent — means a queue can be filtered by urgency before being read. A text field for urgency produces "ASAP", "whenever", and "ASAP!!" that do not sort.
This one uses file uploads, which is a paid feature — you can build and edit it on the free plan, but saving it needs an upgrade.
No card required.
Service Request Form
Live previewHow to build this form
5 steps in the editor.
- Add short text and email fields for the requester, plus a phone field left optional for urgent callbacks.
- Add a select field for request type — support, billing, technical, general — so you can filter requests by type in the CSV.
- Add a radio group for urgency (routine, soon, urgent) so a queue can be sorted by how fast someone needs an answer.
- Add an optional text field for location, and a required textarea for the request description.
- Add an optional select field for preferred contact method, then add a webhook destination so each request reaches your team the moment it arrives.
Fields in this form
9 fields, using 7 of the 19 field types available.
| Question | Field type | Required |
|---|---|---|
| Full name | Short text | Yes |
| Yes | ||
| Phone | Phone | Optional |
| Request type | Select | Yes |
| How soon do you need a response? | Radio buttons | Yes |
| Location (optional) | Short text | Optional |
| Describe your request | Long text | Yes |
| Preferred contact method | Select | Optional |
| Attachment (optional) | File upload | Optional |
What goes wrong with this form
Specific to a service request form, not general advice about forms.
Request type as free text
A text field for what the request is about produces "help", "question", "tech issue" and a hundred micro-categories you have to group by hand every time you want a count. A select field with fixed types — support, billing, technical — can be filtered by type in the export.
Urgency as a text field
Free text for "how urgent" produces "ASAP", "whenever", and variations that do not sort. A radio group with fixed options — routine, soon, urgent — lets a queue be reordered by urgency before anyone reads it.
No description field, so context has to be asked for
A required textarea for the request description means every submission arrives with enough context to route it. Without it a support team has to email every requester asking "what did you actually need", which is work the form exists to prevent.
Questions about this form
What should a service request form ask?
Contact details — name, email, phone — request type as a dropdown (support, billing, technical, other), urgency as radio buttons (routine, soon, urgent), and a textarea for the description. Location is optional and useful only in specific domains. Six fields is usually the right number.
Can requests reach a webhook or Slack channel?
Yes. Add a webhook, Slack or Discord destination in Settings and every request reaches your system or channel the moment it is submitted. The response is stored in Seagit either way and exports to CSV, so the dashboard is always the record.
Can I route by request type automatically?
Not automatically inside the form — request type is a select field so every request carries a value you can sort or filter by, but assigning it to a queue or person is still a step you take after it arrives. A webhook makes that automatic if your own system handles it.
This one uses file uploads, which is a paid feature — you can build and edit it on the free plan, but saving it needs an upgrade.