Best for
NPS, satisfaction surveys, post-conversation ratings, qualification scores, and any single integer the visitor picks from a fixed scale.
Rating input asks the visitor to pick a number on a configured scale. Use this block when the answer is a satisfaction score, an NPS rating, a 1-5 review, or any single integer the visitor selects from a fixed range.
Applies to: Builder Widget Results Contact fields
Best for
NPS, satisfaction surveys, post-conversation ratings, qualification scores, and any single integer the visitor picks from a fixed scale.
Stores
A single integer in workflow answers. Optionally updates a custom contact field of type Rating or Number.
Routes
Continues along the step’s default path. Rating input does not branch based on the score.
| Capability | Supported |
|---|---|
| Discrete integer scale | Yes, configurable minimum and maximum |
| Auto-submit on selection | Yes, the visitor picks a score and the workflow continues |
| Per-answer routing | No, all scores continue along the step’s default path |
| Contact field binding | Yes, custom Rating or Number fields |
A post-conversation feedback workflow asks:
How would you rate this conversation, on a scale of 0 to 10?
The visitor sees the numbers 0 through 10 as a row of buttons. They tap 8 and the workflow continues to the next step. The score is stored as the integer 8 in the workflow result and can be sent to a custom Rating field on the contact.
Use Rating input when the answer is a single integer on a known scale.
Good use cases:
Use a different block when:
The question text appears immediately before the visitor sees the rating buttons. Keep it specific and answerable.
Good:
How would you rate this conversation, on a scale of 0 to 10?
Avoid:
Was this helpful?
Always state the scale in the question so the visitor knows what 8 means before they pick.
Set Minimum score and Maximum score to define the scale. The widget renders one button for every integer between the minimum and maximum, inclusive.
Common choices:
0 to 10 for NPS-style scoring.1 to 5 for satisfaction or quality ratings.1 to 10 for finer-grained satisfaction or readiness scoring.Maximum must be greater than minimum; the publish review rejects rating blocks where the maximum is equal to or below the minimum.
Rating input answers are always saved in workflow answers. You can also bind the answer to a custom contact field of type Rating or Number.
| Question | Suggested contact field |
|---|---|
| How likely are you to recommend us? | NPS score (custom Rating field) |
| How would you rate this conversation? | CSAT (custom Rating field) |
| How ready are you to buy? | Buying intent (custom Number field) |
Rating input cannot bind to standard contact fields (First name, Last name, Email, Phone, Display name) — only custom fields with a Rating or Number value type are compatible.
Net Promoter Score
Use a 0 to 10 scale at the end of a workflow. Bind to a custom Rating field so reporting can roll up promoter, passive, and detractor segments.
Satisfaction survey
Use a 1 to 5 scale right after a service interaction. Pair with a Text input for free-form feedback when the score is low.
Lead qualification scoring
Ask the visitor to rate their readiness to buy or their project urgency. Use a Condition block after the rating to route hot leads to a sales rep.
Post-resolution feedback
At the end of a support workflow, ask the visitor to rate the resolution. Bind to a custom Rating field used in agent reporting.
When a visitor submits a Rating input answer, DialogMaker stores the value as a structured object with an integer score.
{ "type": "rating", "value": 8}| Field | Meaning |
|---|---|
type | Always rating for this block. |
value | The integer the visitor selected. Always within the configured Minimum score and Maximum score range. |
Rating input always continues along the step’s default path. The block does not branch on the score.
To route based on the score — for example, send detractors (0 to 6) to a recovery workflow — add a Condition block after the Rating input and compare the saved value.
DialogMaker rejects invalid Rating input answers when:
| Problem | What to check |
|---|---|
| The visitor cannot pick the same score twice in a row | The widget submits as soon as the visitor taps a score. To change the answer, the visitor must restart the workflow. |
| The publish review rejects the block | The Maximum score must be greater than the Minimum score. Adjust the scale and republish. |
| The score cannot be bound to a standard contact field | Rating input only binds to custom contact fields of type Rating or Number. |