12 templates
Customer service form templates
A customer-service form is useful when it arrives already sorted: a reason chosen from a dropdown, an order reference in its own field, a rating that averages. These templates replace the free-text complaint with those structured answers, so a reply can be triaged before anyone reads the whole message.
Nothing here issues a refund, opens a ticket elsewhere or replies on your behalf. Each response lands in your dashboard and CSV export, and can be sent to your own webhook on any plan.
All 12 customer service templates
Each one is a working form. Open it, fill it in and submit it — nothing is saved — then build it in your own account with every field already configured.
Feedback
A score, a reason, and how likely they are to recommend you.
Try it liveSupport Request Form
Collect customer support requests by category and urgency so you can triage and respond faster.
Try it liveComplaint
A structured way for customers to report a problem and say what resolution they need.
Try it liveNPS Survey
One scored question on likelihood to recommend, one follow-up explaining why.
Try it liveBug Report
Gather software bug details, severity and reproduction steps from users.
Try it liveFeature Request
Collect user ideas for new product capabilities, the problem each solves, and priorities.
Try it liveAnonymous Feedback Form
Let people speak freely without identifying themselves.
Try it liveService Request Form
A request type, urgency level and description — the whole job in six fields.
Try it liveLost and Found Form
Collect item description, photo and contact details when someone reports a lost or found item.
Try it liveCustomer Satisfaction Survey
A score and open feedback on what went well and what could improve.
Try it liveLoyalty Program Signup
Customer email and contact info for a rewards program enrollment.
Try it liveShipping Address Change
Request to change delivery address on a pending order.
Try it liveWhich customer service template should you start from?
These differ less in their fields than in what has to be true after someone submits. That is the useful way to choose.
If you need a number you can chart
Start from the feedback form. The rating and recommendation score stay structured, so they average and chart directly out of the CSV export, with the open answer sitting in the same row as the score it explains.
If it's a problem, not just an opinion
Start from the complaint form. Category, description and desired resolution are separate fields, so a complaint sorts by type and tracks by what was actually asked for — the feedback form is the one for scores and sentiment instead.
If you need one number that sums up loyalty
Start from the NPS survey. It is deliberately two fields — a 0-10 slider and one open "why" — because the whole methodology is that minimalism, with promoters, passives and detractors read off the score after export.
If the audience is developers, not customers
Start from the bug report form. A severity dropdown and an "expected versus actual" pair of textareas replace an urgent message with no context, so reports can be triaged by impact rather than by arrival order.
If it's a capability you don't have yet, not a bug
Start from the feature request form. Priority and use-case fields are what the bug-report-form does not ask for — one is "something is broken," the other is "something doesn't exist yet."
If people will only be candid without a name attached
Start from the anonymous feedback form. It has no name or email field, only a topic, a 1 to 5 slider and a written account, plus an optional follow-up email. Anonymity is by design, not a guarantee, because timestamps and writing can still identify someone.
If requests come in for many different kinds of help
Start from the service request form. Request type is a dropdown and urgency is a required radio, so you can filter the CSV to what needs answering first. It is not a ticketing system: there are no statuses or deadlines.
If lost and found reports need to be matched later
Start from the lost and found form. A lost or found radio, category, colour and location are required and a photo can be attached, so staff can match items from the CSV. Nothing is matched for you.
If you want feedback from customers on what worked well and what could improve
Start from the customer satisfaction survey. A slider field (0-10) gives you a number to average, while required "what went well" and optional "improvements" textareas capture the reasoning. Satisfaction averages are only meaningful if collected consistently; one-off surveys trend but do not predict.
If you are signing customers up for a rewards or loyalty program
Start from the loyalty program signup. Name, email and optional phone fields collect contact details, while an optional "how did you hear about us" select tells you which marketing channel brought them in. The form records signup information but does not itself issue loyalty card numbers or track points.
If a customer needs to change their shipping address before their order ships
Start from the shipping address change. An order-number field and new-address textarea let fulfillment find the order and update it, while an optional reason select sorts requests by type. The form logs the request but does not change the order — someone in fulfillment still reads it and acts.
If a support team needs customers to report issues sorted by urgency and category before the team reads the description
Start from the support request form. It collects name, email, issue category (billing/technical/feature/other) via required dropdown, urgency (low/medium/high) via required dropdown, and issue description. Your team can sort and triage by category in the CSV or the dashboard. Not for emergency channels.
Other template categories
- Event templates 32RSVPs, registrations, bookings and sign-ups where the numbers have to add up.
- HR templates 39Hiring, time off, onboarding, reviews and exits — the same questions for every employee.
- Education templates 24Registrations, permissions, course feedback and parent sign-ups for schools and classes.
- Health templates 23Patient intake, appointment requests, consent and feedback for clinics and practices.
- Ecommerce templates 10Orders, returns, warranty claims and payments, where a wrong answer costs money.
- Business templates 78Contact, service requests, intake and bookings — the everyday forms a business runs on.
- Real estate templates 18Rental applications, maintenance requests, viewings and tenant notices.
- Research templates 15Participant sign-up, screening, consent and study surveys.
- Marketing templates 15Lead capture, newsletter sign-ups, demo requests, giveaways and testimonials.