Phone input

Phone input asks the visitor for a phone number. Use this block when the workflow needs a callback number, an SMS-reachable contact, or a phone field on the contact record.

Applies to: Builder Widget Results Contact fields

Best for

Lead callbacks, sales follow-up, account verification, and any workflow where the visitor’s phone number is required.

Stores

The phone number as a trimmed string in workflow answers. Always available to bind to the contact’s phone field.

Routes

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

Use Text input for free-form contact details

If the answer is not a phone number, use Text input. Phone input enforces a basic length range and shows a phone-friendly keyboard on mobile devices.

At a glance

Capability	Supported
Mobile phone keyboard	Yes, automatically on supported devices
Length validation	Yes, between 4 and 32 characters
Per-answer routing	No, all answers continue along the step’s default path
Contact field binding	Yes, the standard Phone contact field
Skip if the contact already has the value	Yes

Example

A demo-request workflow asks:

What’s the best number to call you back on?

The visitor types their phone number and presses Continue. The answer is stored on the workflow result and bound to the contact’s phone field, so a sales rep can call back later.

When to use Phone input

Use Phone input whenever the workflow needs to collect a phone number for follow-up.

Good use cases:

• Capture a callback number for sales or support.
• Collect an SMS-reachable contact for appointment confirmations.
• Verify a phone number on file for an existing contact.

Use a different block when:

• The answer is open-ended text: use Text input.
• The answer is an email, URL, number, or date: use the matching specialized block.

Add a Phone input block

1. Open a workflow and go to the builder.
2. In the block sidebar, open Questions.
3. Add Phone to a step.
4. Write the question text visitors should see.
5. Optionally set a placeholder shown inside the empty field.
6. Confirm the answer is bound to the Phone contact field.
7. Connect the next path.

Configure the question

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

Good:

What’s the best number to call you back on?

Avoid:

Can we follow up?

State plainly that you are asking for a phone number and explain how it will be used.

Configure the input

Placeholder

The placeholder is the helper text shown inside the empty input field. Use it to suggest the expected format — +1 555 0123 or (555) 555-0123 — so visitors know whether to include a country code.

The placeholder disappears as soon as the visitor starts typing.

Save the answer

Phone input answers are always saved in workflow answers. They should also be bound to the contact’s standard Phone field — this is what enables follow-up and identity matching.

Question	Suggested contact field
What’s the best number to call you back on?	Phone
What phone number should we send the confirmation to?	Phone
Confirm your mobile number	Phone

The publish review warns when a Phone input is not bound to the Phone contact field, and offers a one-click fix to bind it.

Skip if we already have this value

When the answer is bound to the Phone contact field, the editor shows a Skip if we already have this value toggle. Turn it on to skip the question entirely if the contact already has a phone number. This avoids re-asking returning visitors for information they have already provided.

Use Skip if known for returning visitors

When the same workflow may be entered by both new and returning contacts, binding to the Phone contact field plus turning on Skip if we already have this value keeps the conversation short for repeat visitors without losing the question for first-time visitors.

Common patterns

Sales callback request

Ask for a callback number after a demo-request workflow. Bind to the Phone field so the rep can dial directly from the contact.

SMS confirmation

Collect a mobile number to send SMS confirmations through a follow-up integration. Use Skip if known so existing contacts are not re-asked.

Account verification

Capture the phone number on file for an existing contact at the start of an authenticated workflow.

Lead enrichment

Pair a Phone input with a Webhook block to trigger an enrichment service or a CRM update as soon as the number is captured.

Answer output

When a visitor submits a Phone input answer, DialogMaker stores the value as a structured object.

{
  "type": "phone",
  "value": "+1 555 0123"
}

Field	Meaning
type	Always phone for this block.
value	The trimmed phone number string the visitor submitted, stored as the visitor typed it.

Routing behavior

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

To route based on the number — for example, by area code — add a Condition block after the Phone input and check the saved value.

Validation and limits

DialogMaker rejects invalid Phone input answers when:

• The answer is not a Phone answer.
• The answer is empty after trimming whitespace.
• The answer is shorter than 4 characters or longer than 32 characters.

Troubleshooting

Problem	What to check
The visitor’s number is rejected as too short	Phone numbers must be at least 4 characters. International formats with country codes always meet this minimum.
The visitor’s number is rejected as too long	Numbers can be up to 32 characters. Trim extension digits or extra punctuation.
The same person’s number appears twice with different formatting	DialogMaker does not normalize phone numbers. Encourage a single format with the placeholder, or normalize downstream in your CRM or integration.
The number is missing from contact information	Make sure the answer is bound to the Phone contact field. The publish review flags Phone inputs that are not bound.
The publish review warns “Phone is answer-only”	Bind the Phone input to the standard Phone contact field. The review offers a one-click fix.

Related articles

• Question blocks overview
• Answer storage
• Email input
• Text input