Most customer complaint forms collect enough to answer the complaint and not enough to stop it happening again. The submissions arrive as paragraphs of prose with no reference number, no date of the incident, and no indication of which of eleven things went wrong, so each one has to be read from scratch and none of them can be counted. Six months later the only honest answer to "what do people complain about most" is a guess.
The form is the cheapest place to fix that, because every field added at intake is a question nobody has to ask by email later. It is also the easiest place to overcorrect, since a complaint form long enough to satisfy an analyst is one an angry customer abandons.
Decide which of the three jobs the form is doing
A complaint form is asked to do three different things, and the field list follows from which ones apply.
Resolve this specific complaint. Needs whatever identifies the transaction and the person, plus enough detail to act. Short, and mostly the customer's own words.
Prove the complaint was handled. Needs a timestamp on arrival, an owner, a record of what was decided, and a closing date. Most of this is captured by the system rather than asked for.
Find the pattern across complaints. Needs a category, a date of incident distinct from the date of reporting, and a consistent way of recording the cause. This is the job that gets dropped, and it is the only one that reduces the number of future complaints.
The three jobs also have different owners. The first belongs to whoever answers the customer. The second belongs to whoever has to show, months later, that the case was handled properly. The third belongs to whoever is responsible for the thing that broke, who is usually nowhere near the complaint queue and will only ever see a summary. Naming those three people before designing the form settles most arguments about which fields are worth the friction.
Trying to do all three with one long form is how these end up unfinished. The better split is a short form for the customer, with the analytical fields filled in by whoever handles the case. A category assigned by a trained handler beats a category chosen from a dropdown by somebody who is upset, and it costs nothing at the point of submission.
The fields that earn their place
Nine fields, four of them required. This covers a complaint from an individual customer about a product or a service.
- Name. Required. Optional only if the form doubles as an anonymous channel, which is a different form with different handling.
- Email address. Required. One contact route, not three. A phone field added "in case" produces numbers nobody calls.
- Order, booking, or account reference. Required when one exists, with a note on the label saying where to find it. Asking for it at intake removes the single most common round trip.
- Date the problem happened. Required, and separate from the date of submission. A complaint reported in March about something that happened in January is a different case from one reported the same day, and the gap between the two dates is one of the more useful numbers a complaint log can produce.
- What happened. One open text box, the largest field on the form, with a label that asks for the sequence rather than the feeling. Something like "What happened, and in what order" collects more usable detail than "Details of your complaint".
- What outcome is being asked for. A short open field or a small set of options: a refund, a repair, a replacement, an apology, or a change so it stops happening. This one field prevents most of the mismatches where a case is closed with a voucher the customer never wanted.
- Attachments. Optional, multiple files, images accepted. A photograph settles disputes about condition faster than three emails.
- How they would prefer to be contacted. Optional, two or three choices. Cheap to ask and it removes a guess.
- Consent to be contacted about the complaint. Required where the jurisdiction or the privacy notice requires it, with plain wording and a link to the notice rather than the notice itself.
Nothing else is at the intake stage. Category, severity, owner, status, root cause, and resolution are filled in afterwards by the person handling it.
What to leave off, and why
A category dropdown with more than six options. Long category lists get answered with the first plausible item or the last one, which corrupts exactly the data the field was added to produce.
Severity or urgency chosen by the complainant. Everybody selects the top option, which means the field carries no information while creating an expectation about response time.
Postal address. Only needed if something is being physically returned or sent, in which case ask for it at that point, not at intake.
Job title, company size, how they heard about the business. Marketing fields on a complaint form read exactly as they are.
A required phone number. It cuts completions noticeably and, in most cases, nobody phones.
A confirm your email field. A typo in an address is better solved by showing the address back on the confirmation screen.
A rating scale. A complaint is not a satisfaction survey, and a one to five score next to a description of what went wrong adds nothing to the case while making the form feel like a research exercise.
Anything asking the customer to agree the complaint is accurate. It reads as a warning and changes nothing legally that the rest of the form does not already cover.
Who assigns the category matters more than the categories
The choice is not between having categories and not having them. It is about who fills them in.
| Customer picks the category | Handler assigns it after reading | |
|---|---|---|
| Accuracy | Low. Picked while upset, from labels written by someone else | High. Same person applies the same definitions each time |
| Cost at submission | One more field, measurably fewer completions | None |
| Speed of routing | Immediate, but routes on an unreliable answer | Minutes later, on a correct one |
| Usefulness for analysis | Poor. Categories drift and cannot be compared over time | Good, provided the list stays short and is reviewed |
The one exception is routing that has to be instant. If complaints about safety or about a regulated product must reach a specific person within hours, a single question near the top, phrased as a plain yes or no about the situation rather than as a category, does that job without asking the customer to classify anything.
Keep the internal list to six or eight categories and revisit it twice a year. Long lists are added to and never pruned, and by the second year no two handlers use them the same way.
What has to happen after submit
The form is the smaller half. A complaint form with no defined path behind it produces a queue nobody owns and customers who complain twice, once about the problem and once about the silence.
An acknowledgement on screen and by email, immediately. Both should state what happens next and by when. The email also gives the customer a written record, which reduces the number who chase.
A reference the customer can quote. Any stable identifier. Without one, every follow up starts with working out which complaint it refers to.
One named owner per complaint. Not a team and not a shared mailbox. A shared mailbox with four people watching it is where cases are read by everyone and answered by nobody.
A status with few states. Received, in progress, waiting on the customer, resolved. Four states get maintained. Nine do not.
A clock on the first substantive reply. The acknowledgement is automatic and does not count. The number worth watching is the time to the first reply written by a person, measured as a median, because the average is dominated by the one case that took six weeks.
A cause recorded in one line at closing. Not the category, which says what the complaint was about, but what actually went wrong. This is the field that turns a complaint log into something that prevents complaints, and it takes fifteen seconds per case.
Most of this is mechanical, which is the point. Where complaints arrive through a form, keeping the owner and the status on the response itself means none of it depends on somebody remembering to copy the case somewhere else.
Where a written procedure is expected
In some sectors a complaint form is part of a documented process rather than a convenience, and the requirements come from a regulator, a contract, or a certification scheme rather than from good practice. Check the specific rules that apply, because response deadlines and record keeping periods differ by sector and by country, and a number taken from a general article is the wrong number.
The recognised general guidance is ISO 10002:2018, titled "Quality management. Customer satisfaction. Guidelines for complaints handling in organizations", published in July 2018 and confirmed as current in 2023. It is guidance rather than a certifiable requirement, and it covers the planning, operation, and review of a complaints process rather than the layout of a form. Annex B of that document is written specifically for small businesses.
Two things from that framing are worth adopting whether or not the standard applies. Complaints should be visible to management as a set, not just handled individually, which means somebody senior looks at the categories and causes on a schedule. And the process itself gets reviewed, which in practice means asking once or twice a year whether the form still matches what people are actually complaining about.
Make it findable and finishable
A complaint form that takes three clicks from the footer to reach collects fewer complaints, which looks like fewer problems and is not. Link it from the contact page, the order confirmation email, and the help pages, using the same words the customer would use rather than an internal term like "feedback" or "case submission".
One screen per question is worth it for anything over five fields, because most of these are opened on a phone by someone standing somewhere annoyed. Keep the open text field unrestricted in length and never impose a character minimum. Allow file attachments without requiring an account. And put the privacy wording in one short sentence with a link, not four paragraphs above the submit button.
If the same form is also expected to handle suggestions, returns, or general questions, split it. One route per intent, each landing in the queue that deals with it, is less work than untangling a single inbox afterwards. The same set of intake routes usually already exists for other kinds of request, and complaints belong alongside them rather than in an address.
What to change first
Add the date the problem happened and the outcome the customer is asking for, then drop any category dropdown longer than six options and assign the category yourself when the case is read. Those three edits take an hour and change what the log can tell you in a quarter. Halict shows what one complaint looks like when the submission, the owner, and the reply sit on the same screen.
Q1. How many fields should a customer complaint form have?
Around nine, with four required: name, email, the order or booking reference, and what happened. Everything analytical, such as category, severity, owner, and cause, is better filled in by the person handling the case than asked of a customer who is already annoyed.
Q2. Should a complaint form allow anonymous submissions?
Only if it is a separate form with its own handling. An anonymous complaint cannot be resolved for the person who made it, so the two routes need different acknowledgements and different expectations. Mixing them in one form means promising a reply that sometimes cannot be sent.
Q3. What should the customer see immediately after submitting?
A confirmation on screen and an email, both stating what happens next and by when, plus a reference they can quote. The email matters more than it looks, because it is the written record that stops people submitting the same complaint twice or chasing it by phone.
Q4. Should the complaint form ask people to choose a category?
Usually not. Categories chosen while upset are unreliable, and unreliable categories are worse than none because they get counted anyway. The exception is a single plain yes or no question near the top when safety or a regulated issue has to be routed within hours.
Q5. What is the one number worth tracking from a complaint form?
Median time to the first reply written by a person, with the automatic acknowledgement excluded. It responds to changes in process within a week, unlike resolution time, which is dominated by a few long cases, and unlike volume, which mostly tracks how easy the form is to find.