Survey Question Types Growth+This feature requires the Growth+ plan or higher
The survey builder's left panel holds two groups: Survey elements — the rating scales EquipDash charts for you — and Form elements, the same field library used by waivers and forms, for everything else.
Survey Elements
These four are rating questions. EquipDash works out averages, distributions and trends for all of them automatically, and shows each one on the analytics page.
NPS Rating
A 0-to-10 scale asking how likely a customer is to recommend you. It powers your Happiness score (the average) and the NPS benchmark shown underneath it.
- Scale: 0 ("Not likely") to 10 ("Very likely")
- Categorization: answers are sorted into Happy (9–10), Okay (7–8), and Unhappy (0–6)
- Best for: overall loyalty, and the one number to track month over month
- Bonus: when a survey includes an NPS question, the survey email shows the 0–10 scale in the message itself. Customers tap a number, the survey opens with it preselected, and one more tap submits.
See Happiness Scores (NPS) Explained.
Likert Scale
A statement customers rate their agreement with, on a 1-to-5 scale.
- Scale: 1 (Strongly Disagree) to 5 (Strongly Agree)
- Best for: opinions on a specific statement, e.g. "Check-in was quick and easy"
Customer Satisfaction
An emoji-based 5-point satisfaction scale.
- Scale: Very Unsatisfied → Very Satisfied, shown as faces
- Best for: how one part of the visit felt, e.g. the handover or the briefing
Customer Effort Score
Measures how easy or hard something was, on a 1-to-7 scale.
- Scale: 1 (Very Difficult) to 7 (Very Easy)
- Best for: finding friction, e.g. "How easy was it to book online?"
Form Elements
The full field library. Everything below can be dragged into a survey exactly as it can into a waiver or form.
Questions people answer
| Element | Format | Best for |
|---|---|---|
| Short Text | One line of free text | Quick open answers — "What was the highlight?" |
| Long Text | A multi-line box | Detailed feedback — "Anything we could improve?" |
| Text Input | One line, structured | A short specific value, e.g. a booking reference |
| Number | Numeric entry | A count or measurement |
| Single Choice | Pick one | Mutually exclusive answers — "How did you hear about us?" |
| Multiple Choice | Pick one or more | "Which activities did you enjoy?" |
| Dropdown | Pick one from a list | The same job as Single Choice when the list is long |
| Star Rating | 1–5 stars | A quick rating on one specific thing |
| Date Picker | Calendar | "When did you visit?" |
| Time Picker | Time | A time of day |
| Agreement | Tick-to-agree | An acknowledgement inside the survey |
| File Upload | File or photo | Letting customers attach a photo of an issue |
Add, remove and reorder the answer options for Single Choice, Multiple Choice and Dropdown in the builder.
Who answered
| Element | Format | Best for |
|---|---|---|
| Full Name | Name input | Identifying who answered a shared link or QR code |
| Email input, format-checked | Matching a response to a customer — and the address the thank-you reward code is sent to | |
| Phone | Phone input | An alternative contact for follow-up |
| Address | Address input | Where customers came from |
| Signature | Drawn or typed signature | An acknowledgement alongside the answers |
| Initials | Initials capture | Initialing a specific statement |
When a survey is sent automatically we already know who the customer is. If you share a survey by link or QR code, add an Email element — without it there's nobody to send a thank-you reward to.
Layout and instructions
| Element | Shows | Best for |
|---|---|---|
| Heading / Heading 2 / Heading 3 | Display text, three sizes | Breaking a longer survey into clear parts |
| Text Block | A paragraph of display text | Context or instructions between questions |
| Section | A group container in the builder | Keeping related questions together while you build — customers see a flat list |
| Additional Logo | An extra logo | Co-branding partway down the survey |
| Image | A picture | A photo to illustrate a question |
Show a Question Only When It's Relevant
Any question can be set to appear only when an earlier answer matches, so people only see follow-ups that apply to them. The classic use is asking why only when someone is unhappy: put a Long Text "What went wrong?" after your NPS Rating, then show it only when the NPS score is at most 6.
Open the question you want to gate, tick "Show this question only if…", and build the rule (earlier question · comparison · answer). Numeric questions — NPS, Customer Satisfaction, Customer Effort Score, Star Rating, Number — support is at least / is at most, so you can target high or low scorers precisely.
This is the same conditional-logic engine used by waivers and forms — see Form Fields & Builder → Show a Field Only When Needed for operators and multi-condition (match all / any) rules.
Analytics stay honest: a gated question is only shown to some people, so EquipDash reports its response rate against the number who actually saw it — it never looks "skipped" by people who were never asked. Gated questions carry a small Conditional badge on the analytics page.
Tips for Choosing Elements
- Start with NPS. One number, tracked over time, comparable to anyone else's.
- Keep it to 3–5 questions. Response rates fall off sharply beyond that.
- Mix one rating with one open text. The rating tells you what is happening; the text tells you why.
- Be specific. "How would you rate the condition of the equipment?" is more actionable than "How was everything?"
- Add an Email element to anything you share by link or QR code, so rewards can reach the customer.