Skip to main content

Pre-registration for Advanced Approvals

Collect information directly from visitors before they arrive by adding visitor fields to your policy.


Overview

Pre-registration lets you collect information directly from your visitors before they arrive, as part of your Advanced Approvals policy. Instead of the host or an admin entering every detail, you can assign specific policy fields to the visitor.

Use pre-registration when accurate, first-hand information from the visitor is part of your entry requirements, such as Date of birth or travel history. The visitor completes these fields through a secure pre-registration link before their visit.

Configuring Pre-registration

If your policy includes any field set to Visitor only, pre-registration will be necessary for every sign-in flow associated with the policy.

Visitors may also provide these fields via walk-up visitors. Visitors may experience long wait times if multiple admins must approve their visit after signing in via the kiosk.

  1. In the Policy builder, add or edit a policy field.

  2. Under Assigned to, choose a visitor option:

    • Inviters and Visitors: The host can enter an initial answer on the invite form; the visitor can see it and update it during pre-registration.

    • Visitors only: Only the visitor provides the answer during pre-registration.

  3. Select Pre-registration from the sidebar.

    1. Optional: Set the step to Required so the approval process waits for the visitor to complete pre-registration.

  4. Add the pre-registration step to your policy by connecting it to other steps.

  5. Continue building out your policy. See main article: Building, Publishing, and Using your policy.

  6. Publish the policy and associate it with your sign-in flows.

💡Tip: Not sure when to use an Inviter + Visitor vs. Visitor only policy field? Use Inviter + Visitor when you want to pre-fill an answer the visitor can correct; use Visitor only when the information must come from the visitor alone.💡

The visitor experience

The visitor experience is just as straightforward as a standard Envoy invite.

  1. The visitor receives a pre-registration link with their invite.

  2. They complete the required fields.

  3. They submit.

Once submitted, the pre-registration form is locked. The visitor can't reopen the link to change their answers, and the submission time is recorded for your audit trail. If a detail needs to be changed afterward, an admin can update it in the invite record.

Did this answer your question?