Contact Preference

Published July 29, 2026

Contact Preference is a focused Question Block that asks how a participant wants the conversation to continue. It captures communication intent; it does not replace Lead Capture or imply consent.

How the decision works

Configure the block

1. Add Contact Preference from the Flow Block picker.
2. Customize the participant-facing question, labels, and descriptions.
3. Give each choice a stable channel value such as booking, email, phone, sms, information, or self_serve.
4. Specify whether the choice requires an email address, phone number, or no contact information.
5. Optionally choose the destination used immediately after selection.
6. Save the selected channel to a custom variable for personalization, reporting, and later rules.
7. Preview every path before publishing.

The block supports 2–7 choices. Channel values must be unique even when visible labels differ.

Lead Capture checks

When a choice needs an email address or phone number and routes to Lead Capture, the builder checks whether that field is enabled and required. Resolve any warning before publishing.

• Email me should lead to a step that requires email.
• Call me and Text me should lead to a step that requires phone.
• Book a meeting can route directly to Booking or Appointment Selection.
• Continue online normally needs no contact information.

Consent

A channel preference is not marketing consent. Selecting Text me or Email me communicates the participant's preferred follow-up method, but any required transactional or marketing consent must still be collected separately.

Plans and routing

Contact Preference is available on every plan. Collecting and saving the preference is included; immediate per-choice destinations follow the existing Pro Jump Logic entitlement.

Analytics

Block Performance records impressions and selections. Contact Preference also identifies the selected stable channel and whether the choice had a configured destination, allowing future reporting on downstream lead, booking, and CTA conversion by preferred channel.