Support ticket form template
A support form's job is triage before a human ever reads it: category and priority let you route tickets automatically instead of everyone landing in one inbox to be manually sorted. This template asks for those two fields explicitly, plus an optional order or account reference, since "which account is this about" is the question support agents ask most often on a ticket that doesn't already answer it.
Copy-paste HTML
<form action="https://send.webforms.to/wft_your_key" method="POST">
<label for="name">Name</label>
<input type="text" id="name" name="name" required>
<label for="email">Email</label>
<input type="email" id="email" name="email" required>
<label for="category">What's this about?</label>
<select id="category" name="category" required>
<option value="">Select...</option>
<option value="Billing">Billing</option>
<option value="Technical issue">Technical issue</option>
<option value="Account access">Account access</option>
<option value="Other">Other</option>
</select>
<fieldset>
<legend>Priority (optional)</legend>
<label><input type="radio" name="priority" value="Low"> Low</label>
<label><input type="radio" name="priority" value="Normal"> Normal</label>
<label><input type="radio" name="priority" value="Urgent"> Urgent</label>
</fieldset>
<label for="account_ref">Order or account reference (optional) (optional)</label>
<input type="text" id="account_ref" name="account_ref">
<label for="message">Describe the issue</label>
<textarea id="message" name="message" required></textarea>
<button type="submit">Submit</button>
</form>Replace https://send.webforms.to/wft_your_key with your own endpoint from the WebForms dashboard.
Why these fields
- Category is required, priority is not. Category is what enables routing (billing questions to one destination, technical ones to another); priority is genuinely subjective coming from the customer, and making it required just teaches everyone to always pick "urgent."
- Account reference is one plain text field, not a lookup or dropdown of the customer's actual orders - that level of integration is a real feature, but it belongs in your own app once someone's logged in, not in a public support form meant to work for someone who isn't.
Where to send it
Get your endpoint
Free for 300 submissions a month. No card required.
Start freeSupport ticket form FAQ
Yes - routing rules on paid plans read the category field and send the submission to different destinations accordingly, from the same form and the same endpoint.
Turn on the autoresponder in the form's settings to send an automatic confirmation to whatever email address they submitted, so they're not left wondering if it went through.