• FORM FIELDS AND CONDITIONAL LOGIC • SETUP GUIDE

How to Use the Customer (contact) Block

By Rivio Support Team
2 min read

What you will achieve in this guide

Follow this step-by-step documentation to configure custom B2B registration forms, approval workflows, and customer tagging.

EXPECTED SETUP TIME 5-10 Minutes
COMPATIBILITY All Shopify Themes & Plans
TECHNICAL DIFFICULTY Zero Code Required

Use Customer (contact) for the applicant’s grouped primary-contact details. This guide explains setup, a practical example, and how to check the result on your Shopify storefront.

When to use it

Choose this type when you need the applicant’s grouped primary-contact details. Choose the type before configuring mappings, visibility conditions, or approval rules that depend on the answer.

Before you begin

Open the intended form in Rivio B2B Registration Forms and confirm its name and storefront slug. Inspect template fields and smart-block sub-fields so you do not ask for the same information twice. Use dummy details for your first test.

Set up Customer (contact)

  1. In the form builder, select Add field and choose Customer (contact).

  2. Expand its settings and enter a clear label or heading, such as Primary contact.

  3. Inspect the contact sub-fields, including email, before adding separate contact questions. Identify the primary applicant address and review available required and mapping controls.

  4. Drag the element into the intended position. If the form uses steps, review its assigned step.

  5. Select Save, preview the form, and confirm the actual storefront page loads this saved form’s slug.

Example

Question or content: Primary contact

Example: A dummy buyer name and an email you control

Adapt this example to the information your team needs. Use help text to explain the expected answer, and require it only when your review process needs it.

Test and expected result

Submit with a new test email and inspect the grouped answers. Approve a controlled application and compare the linked customer. Separately test an existing email when checking reuse behavior.

Expected result: the saved application contains the intended answer. Any configured visibility, rule, or mapping is checked separately; collecting an answer does not itself approve an applicant.

Limitations and important behavior

Only the first email is used for the customer as indicated in the builder. Approval reuses a customer by email and preserves existing name, phone, and tags while adding approval tags. Collection is separate from approval.

Troubleshooting

If a second customer is not created, reuse by email may be the expected result. If the wrong contact is used, inspect duplicate email inputs and the original submission before changing the form.

Screenshots to add

  • Screenshot placeholder: Builder with Customer (contact) expanded, showing Primary contact and the applicable saved settings.
  • Screenshot placeholder: Dummy submission showing the example answer; include the storefront input if it helps explain selection or validation.

Related guides