Number input

Number input asks the visitor for a numeric answer. Use this block when the answer should be a quantity — team size, budget, age, score, count, or any value that needs to be compared, summed, or used in calculations later.

Applies to: Builder Widget Results Contact fields

Best for

Quantities, scores, prices, ages, counts, and any value used in conditions, calculations, or reporting.

Stores

A single number in workflow answers. Optionally updates a custom contact field of type Number or Currency.

Routes

Continues along the step’s default path. Number input does not branch based on the answer.

Use Buttons for ranges of values

If you want the visitor to pick from named ranges (1-10, 11-50, 51-200), use the Buttons block. Number input collects an exact value the visitor types.

At a glance

Capability	Supported
Whole numbers and decimals	Yes
Minimum value	Yes, configurable per block
Maximum value	Yes, configurable per block
Step (increment)	Yes, configurable per block
Per-answer routing	No, all answers continue along the step’s default path
Contact field binding	Yes, custom Number or Currency fields
Mobile numeric keyboard	Yes, automatically on supported devices

Example

A pricing workflow asks:

How many seats do you need?

The visitor types 25 and presses Continue. The answer is stored as the number 25 in the workflow result and can drive a Condition block that routes large orders to a sales rep.

When to use Number input

Use Number input when the answer is a single quantity that may be compared or used in a calculation later.

Good use cases:

• Ask for an order quantity, seat count, or unit count.
• Capture a budget, price ceiling, or expected spend.
• Collect an age, anniversary count, or year.
• Score a value the visitor enters (1-10 satisfaction, project complexity).

Use a different block when:

• The answer is a range or named tier (small, medium, large): use Buttons.
• The answer is a date or time: use Date input.
• The answer is a 1-5 or 1-10 satisfaction rating with a visual scale: use Rating input.
• The answer is open-ended text that may include numbers: use Text input.

Add a Number input block

1. Open a workflow and go to the builder.
2. In the block sidebar, open Questions.
3. Add Number to a step.
4. Write the question text visitors should see.
5. Optionally set a placeholder shown inside the empty field.
6. Choose where to save the answer.
7. Optionally set Minimum, Maximum, and Step values to constrain the answer.
8. Connect the next path.

Configure the question

The question text appears immediately before the visitor sees the input. Keep it specific and answerable.

Good:

How many seats do you need?

Avoid:

Tell us about your team.

Number input expects a single value. Frame the question so the answer is unambiguous.

Configure the input

Placeholder

The placeholder is the helper text shown inside the empty input field. Use it to suggest the expected magnitude — 25, 1500, 0.5. The placeholder disappears as soon as the visitor starts typing.

Minimum and Maximum

Set Minimum and Maximum to define the range of accepted values. The widget rejects answers outside the range and shows a validation error.

Use bounds when the question has a known answer range — a satisfaction score (1 to 10), a seat count with a hard cap, or an age that must be at least 18.

Both fields are optional. Leave them blank to accept any finite number.

Step (optional)

Set Step to require the answer to be a multiple of a specific value. For example:

• Step: 1 accepts only whole numbers.
• Step: 0.5 accepts halves (1, 1.5, 2, 2.5, …).
• Step: 100 accepts only multiples of 100.

When Minimum is set, the step counts from the minimum. With Minimum: 5 and Step: 10, accepted values are 5, 15, 25, and so on.

Leave Step blank to accept any number.

Save the answer

Number input answers are always saved in workflow answers. You can also bind the answer to a custom contact field of type Number or Currency.

Question	Suggested contact field
How many seats do you need?	Seats (custom Number field)
What’s your monthly budget?	Budget (custom Currency field)
What’s your project size?	Project size (custom Number field)

Number input cannot bind to standard contact fields (First name, Last name, Email, Phone, Display name) — only custom fields with a Number or Currency value type are compatible.

Common patterns

Order or seat sizing

Capture a quantity early, then route based on the answer with a Condition block — small orders go to self-serve, large orders to a sales rep.

Budget qualification

Ask for a budget figure as part of lead qualification. Bind to a custom Currency field so the value is comparable across leads.

Satisfaction score

Use a 1-10 score with Minimum 1 and Maximum 10. For richer visual ratings, use the Rating input block instead.

Configurable workflow inputs

Capture an item count or unit count that drives the rest of the workflow — the saved number can be referenced by later messages and integrations.

Answer output

When a visitor submits a Number input answer, DialogMaker stores the value as a structured object with a numeric value.

{
  "type": "number",
  "value": 25
}

Field	Meaning
type	Always number for this block.
value	The numeric value the visitor submitted, normalized to a JavaScript number.

Routing behavior

Number input always continues along the step’s default path. The block does not branch on the answer’s content.

To route based on the value — for example, send orders over 100 seats to a sales rep — add a Condition block after the Number input and compare the saved value.

Validation and limits

DialogMaker rejects invalid Number input answers when:

• The answer is not a Number answer.
• The answer is empty.
• The answer is not a finite number (text, NaN, infinity).
• The answer is below the configured Minimum, when one is set.
• The answer is above the configured Maximum, when one is set.
• The answer is not aligned to the configured Step, when one is set.

Troubleshooting

Problem	What to check
The visitor enters a decimal but the system rejects it	Check whether Step is set to a whole number such as 1. Whole-number steps reject decimals. Lower the step or remove it to accept decimals.
The visitor’s mobile keyboard is not numeric	The number block requests a numeric keyboard via the browser. If a non-numeric keyboard appears, the visitor’s browser may not support the hint. The visitor can still type digits.
The answer cannot be bound to the contact’s name or email	Number input only binds to custom contact fields of type Number or Currency. Use a different input block for text fields.
Reasonable values are rejected as too large or too small	Check Minimum and Maximum. Either widen or remove the bounds.

Related articles

• Question blocks overview
• Answer storage
• Buttons
• Rating input