Support request form template
Take a support ticket with the version, the environment, and a screenshot already attached.
10 fields. Free to start. No card.
Who uses it
Software support teams, managed service providers, and hardware vendors. It fits any product where the first reply is usually a request for information the customer could have sent at the start.
The problem it solves
A ticket arrives saying it is broken, and the first three replies go on establishing which version, which browser, and what the customer did. The clock on the response target runs the whole time.
How this handles it
The questions an engineer always asks are on the form, so the first reply is an answer rather than an interrogation, and the screenshot field takes the console, the error, and the screen before it. Each ticket arrives by email and by webhook at once, so a helpdesk system and a human see it in the same second.
The problem
Your environment
Evidence
The error itself, and the screen just before it. Attach a log if you have one.
Contact
API
Submit this form over the API
The template is published as JSON at
/templates/support-request.json.
Read it for every field id, then post values keyed by those ids.
A field id is stable. A label is not.
{
"values": {
"sr_subject": "A short factual answer.",
"sr_impact": "cannot_work_at_all",
"sr_steps": "A short factual answer.",
"sr_product": "Found under Help, then About",
"sr_platform": "windows"
},
"idempotency_key": "support-request-2026-09-09-001",
"agent": {
"name": "your-agent"
}
}Authorization: Bearer ifk_submit_…, or connect over MCP at /mcp.Questions about support request forms
Can log files be attached?
Yes, if the accepted types list them, as this template does. Each file is capped at three megabytes, so ask for the relevant excerpt rather than an entire day of logging.
How does this fit an existing helpdesk?
Point a webhook at the helpdesk and every submission becomes a ticket there, with the fields already separated. The form is the intake surface and your helpdesk stays the system of record.
Should the impact question be free text?
No, because a fixed list is what makes a queue sortable. Four honest options cover nearly every ticket, and the detail that does not fit belongs in the reproduction steps.
Does the customer see a ticket number?
They see the submission reference on the confirmation page. If your helpdesk mints its own number, send that from the webhook handler so the customer holds the identifier your team will search on.
Create this form in your own workspace.
It loads as a draft. Change every field, or send it as it stands.
Create this form