A support request form that collects what the first reply needs
Most support threads start with a reply asking for something the customer could have given at the start: the steps to reproduce, the invoice number, which account. A triage form asks what kind of issue it is, then asks for exactly that detail, so the first reply can be the answer.
What should support teams ask first?
| Ask | Why it matters |
|---|---|
| What kind of issue is this: something broken, a billing question, a request, or something else? | Each kind goes to a different person and needs a different detail. |
| How urgent is it: blocking your work, annoying, or a suggestion? | It sorts the queue by what customers actually need first. |
| For something broken: what steps lead to it, and what did you expect instead? | Steps and expectation are what turns a report into something support can reproduce. |
| For billing: what is the account or invoice number? | Billing cannot do anything without it, and asking later costs a day. |
| Which account or workspace is this about? | Customers with more than one are often writing about the other one. |
| Has this happened before, or is it new? | A repeat problem needs a fix, not another workaround. |
If an answer would not change what you do next, leave the question out. Each extra question is one more reason for someone to stop before they finish.
Do not ask for passwords or full card numbers in a support form. If the issue needs them, the agent asks through your account or billing system instead.
Which answers come back too vague to use, and what do you ask next?
The answers that cause a phone call are rarely missing. They are present and too loose to act on. A narrower follow-up, asked straight away while the person is still there, usually settles them. Offering likely answers shows the person the level of detail you need.
| What comes back | The follow-up that settles it |
|---|---|
| “It doesn’t work.” | What happens when you try: an error message, nothing at all, or the wrong result? |
| “I was charged wrong.” | Was it the amount, a charge you did not expect, or a charge on the wrong date? |
| “It’s urgent.” | Is it stopping you from working right now, or is there a deadline coming? |
Follow up once per gap, then move on. If an answer is still unclear after one follow-up, flag it for whoever picks the request up rather than pressing.
When is a call or a visit still the right move?
An outage, a security worry, or a customer who is already upset needs a person quickly, and the urgency question exists to route those first. The form does not replace support. It removes the first round of back-and-forth so the agent’s first reply can be the fix.
How do you set this up from the Support ticket triage template?
Acquainto has a Support ticket triage template to start from. After you sign up, open Browse templates, pick Support ticket triage, and it lands in the editor as a draft you can change before anything is published.
This template is built for the job. It asks for a short description, the type of issue (a bug or error, a billing question, a feature request or something else) and how urgent it is, and branches on type: a bug leads to the steps and what the customer expected, a billing question to the account or invoice number. Add the account or workspace question if your customers can have more than one.
Acquainto runs it as a short written conversation instead of a form. It:
- asks a follow-up when an answer is incomplete, and asks for clarification when one is vague;
- uses a structured choice where precision matters and open conversation where detail matters;
- shows the person every answer before it is sent, so they correct their own mistakes;
- hands back one clean value per question, delivered to your own systems by webhook.
The person answering needs no account, and nothing has to be scheduled. Start free trial, see how it works, or compare plans.