Customer Complaint
Contact & support
Public Sector · Retail & Sales
Capture a complaint with order context, what went wrong, and the resolution the customer wants.
A complaint form that only says “tell us more” produces novels. This template asks for a topic, a date, and the make-good the customer already has in mind.
Who it is for
CX and store managers who need a paper trail that is not a one-star review.
When to use it
Publish it when something already went wrong. Refund Request is the money-only path. Support Request is for defects you can reproduce. Billing Question is a calmer cousin.
What this form collects
Customer identity, optional order reference, topic, optional incident date, the story, and a requested resolution.
- Retail or restaurant complaint QR
- Ecommerce post-delivery escalation
- Service-business make-good intake
Preview mode: This is a live read-only render of the template. Sign up to clone it into your account, or customize it with the guest AI builder first.
Customer Complaint
Frequently asked questions
Should this be anonymous?
Complaints you cannot reply to are reviews. Keep email required unless you truly want a vent box.
Can staff attach photos of the issue?
Add a file field if customers should upload evidence. The shipped file field accepts images and PDFs.
How is this different from Customer Feedback?
Feedback is a pulse. A complaint expects an owner and a reply. Do not mix them on one thank-you page.
Related templates
Nearby GRTforms templates for the same job or the next step after this one.
Refund Request
Take refund asks with order reference, reason, amount, and how the customer wants to be repaid.
Billing Question
Route invoice and charge questions with account email, invoice ID, and what looks wrong.
Support Request / Bug Report
Collect reproducible bug reports with severity, steps, and optional screenshots.
Customer Feedback Survey
Gather customer feedback with a star rating and open-ended comments.
Contact Us
Simple contact form for general inquiries with name, email, and message fields.