Requiring proof before the complaint is accepted
Asking for a receipt or a photo as a condition of recording the complaint shuts out people who have no proof. Ask whether proof exists and how it can be shared through your own process.
Customer complaint form: a dated record the review can use
A customer complaint form records the complaint in the customer's own words, when and where it happened, who or what was involved, and the outcome the customer is asking for. Its key judgment is keeping the facts a reviewer can check apart from the customer's account of them, so the review can start without guessing. Ask only for what a review needs, and leave out details that will not change the decision.
A filled example
A completed example to compare against
Example only, not a real submission
- Date of the problem
- 6 October, about 10 a.m.
- Type of complaint
- Billing or charge
- What happened
- I booked a two-hour visit. The technician arrived 50 minutes late without calling ahead, and the invoice included a call-out fee that was not in the quote I was given.
- Outcome I am asking for
- A written explanation of the fee, and a corrected invoice if the quote was right.
- Reviewer note (internal)
- Check the written quote and the booking log before replying. Confirm whether the fee applies under the agreed price list.
Field blueprint
Ask for the facts a review needs, in one pass
| Field | Type | Required | Why you ask it |
|---|---|---|---|
Your name | Short text | Required | Lets the reply go to the person who made the complaint, and helps the reviewer find any earlier contact. |
Email addressGive an email address or a phone number so we can reply. One is enough. | Optional | The reply route. The form cannot make email or phone an either-or choice, so the helper text says one is enough. | |
Phone numberOptional if you gave an email address. | Phone | Optional | A second reply route, useful when an email address was mistyped or is rarely checked. |
Date the problem happenedIf you are unsure, enter the closest date you can recall. | Date | Required | Places the complaint in time, so the reviewer can find the booking, shift or order it refers to. |
Where or how it happenedA branch, a web page, a phone call or a visit. Use the words you would use with a friend. | Short text | Optional | Tells the reviewer where to look: the location, the channel or the service point. |
Person or team involved, if you know | Short text | Optional | Shows where to check the record. The customer does not need to name anyone, and a name is a lead to check, not a finding. |
Type of complaintService qualityBilling or chargeDelivery or timingProduct qualityStaff conductOther | Dropdown | Required | Lets the reviewer see the category first, and lets you count patterns by month. |
What happened?Describe the events in order. Say what you saw or were told, not what you think caused it. | Long text | Required | The customer's account, recorded as they gave it. This is the core record, so it should hold facts rather than conclusions. |
What would put this right for you?An explanationA correction to a charge or invoiceA repair or replacementA refundSomething else | Single choice | Optional | Sets the outcome the team must answer. Your own policy decides which outcomes are available. |
Have you raised this with us before?NoYes, by phoneYes, by emailYes, in person | Single choice | Optional | Shows the reviewer whether to look for an earlier contact, so they do not start from nothing. |
Anything else we should know?Leave out health details unless they are needed to understand the complaint. | Long text | Optional | Catches context that does not fit the questions above, without asking for more personal information than the review needs. |
Try it
Preview the form before you send the link
Mistakes to avoid
Wording and gates that discourage honest complaints
Offering answer choices that judge the other party
Options such as 'rude staff' push the customer toward a conclusion. Use neutral categories such as 'Staff conduct', and let the description carry the detail.
Leaving the date optional
Without a date the reviewer cannot match the complaint to a booking, shift or order. Keep the date required and let people enter the closest date they can recall.
Asking for a compensation amount up front
Requesting a sum on the first form turns a complaint into a negotiation. Ask what outcome the person wants, then decide what your policy allows.
After a response arrives
How a complaint moves after submission
Set the reply window in words your team can keep
The hourly production job processes saved submissions, and only the form's creator receives the notice. Write the confirmation message around a reply window your team can meet, not around the moment the notice arrives.
Open a case for complaints that need follow-up
If the form creates a Customer Care case, the case takes the priority, tags and assignees set in form settings. Choose a default that suits most complaints, and have a person review the priority once the facts are in.
Count the pattern each month
The submissions grid lists every complaint, and CSV export lets you count types by month. A repeated billing complaint points to a process to investigate, even when each individual case is closed.
Working checklist
Working a complaint from start to finish
On arrival
- Confirm the date falls within the period you can check
- Find the booking, order or visit the complaint describes
- Mark which facts you have verified and which come from the customer
Before you reply
- Compare the outcome the customer asked for with your written policy
- Avoid admitting fault until the facts are checked
- Name who will follow up and by when, but only if you can keep that promise
When you close it
- Record the outcome and the reason in the case or in your own system
- Note whether the same cause has appeared before
- Tell the customer what changed, if something did
Frequently asked questions
What should a customer complaint form ask for?
Ask for the date, the place or channel, the customer's own account of what happened, the type of complaint and the outcome they want. Include a name and at least one reply route, and ask whether they have raised the matter before, so the reviewer does not start from nothing.
Is there a customer complaint form template I can copy?
The fields in this guide can serve as a starting point. Keep the category labels neutral, and remove any question your team will not read in review. Every extra question can make a complaint form harder to finish, so cut anything that does not change how a complaint is handled.
Should a complaint form let people stay anonymous?
You can make the name optional, but a complaint you cannot follow up on is hard to resolve, and the customer cannot learn what changed. If you accept anonymous reports, say so on the form and explain that the team may be unable to reply.
When should someone use a complaint form instead of a general contact form?
Use the complaint form when the message describes a specific event that needs a record and a review. A general question or a request for information fits a contact form better. If someone starts with a question and then describes a problem, the complaint fields keep the details you need.
Browse by category
More reports in Customer Service & Support
Reports
Warranty Claim
Intake forms
General Contact Us
Surveys
Customer Feedback Survey
Surveys
Encuesta de satisfacción del cliente
Requests
Feature Request
Surveys
Net Promoter Score (NPS)
How to build it
Choose a category and a form type in the wizard. Answer three Atty Suggestions questions, then give the form a title. Atty builds the fields in the background. Edit the fields and ask Atty to refine them, then publish and share the /f/ link.
