Express Guide
Express: Understanding the Registration Flow
Flow draws your whole registration journey as one map, and every card on it opens straight into the screen where you edit that stage. Learn to read the map once, and the rest of your form gets a lot easier to configure from here.
What this article covers: A tour of the Flow map in Express, the single diagram that shows your whole registration journey and lets you click into any stage to edit it. You'll see how your form, the optional Verify step, and Confirmation connect, plus where your closed-registration message lives.
The Flow map
Every registration follows the same path, and Flow draws that path for you as a single diagram. Once you know how to read it, the rest of this guide is a lot easier to follow.
Open the event you want to work on, then head to the Form tab. Everything in this guide lives there, so nothing you do here touches the event details you see on Overview. Inside Form, click Flow.
The map lays out the whole registration journey top to bottom. Identity is your form, and the card lists every field on it. Verify sits underneath as an optional review step, where an attendee checks their answers before submitting, greyed out here because it's switched off, with its own toggle right on the card. Confirmation covers everything that happens after someone submits, and the map ends at Registration Complete.
Here's the part most people miss: click any card and it becomes a door into that stage's editor. Click Identity and you land straight in the form editor, with your fields on the left and the form itself on the right. It's the same screen you'd reach through Form, you just got there by clicking the stage you wanted to work on.
The Verification page
Verify is the only optional stage in the flow. It gives attendees a chance to read their answers back before they commit, and it's off by default.
Toggle Verification on from its card, and you can open it to see the page your attendees would see: settings on the left, a live preview on the right filled in with sample answers. By default, answers are grouped under headings with an Edit button beside each group, one of three layouts along with Rows and Columns.
Preview Mode decides whether that page lists every question you asked or only the ones somebody answered. On a long form with a lot of optional questions, Answered Only gives people a much shorter page to read.
Above the layout options sit two more settings: the shield badge on the blue banner, and the event banner image behind it. Both are on by default. Three button captions are yours to change too: Review Answers, Edit Answers, and Confirm and Submit.
The heading and paragraph in the blue banner are editable as well, just not from the side panel. Click the message card on the canvas, and a small toolbar appears above it, bold, italic, text style, color, and alignment, plus a Reset button if you want the original wording back.
Insert Field opens a list of dynamic fields in three groups: Event fields (name, dates, location, organizer), System fields (the registrant's own contact details), and your form's own custom fields. Drop one into the message and it shows up as a green chip while you're editing, then fills in with the real value once someone reaches the page. Write the message once with a token like event_name, and it works for every event you run.
Confirmation email and page
Confirmation covers three tiles, and each one opens a different editor.
Page is the screen an attendee lands on after they submit. You'll find toggles for the success icon and the event banner, plus the same dynamic fields you used on the verification page, so the page can greet someone by name and quote their own registration code back to them.
Email is the confirmation message that goes out automatically. Preview buttons let you check how it renders in Gmail, Outlook, Apple Mail, and mobile, and a Send Test button lets you send yourself a copy before you rely on it.
Actions is the third tile, and it's empty on a new event. It's built for anything that should fire automatically after someone registers: webhooks, emails, Slack messages, calendar invites, tags, and delays. You don't need any of it to run an event, but when someone asks whether Express can tell another system that a person just registered, this is where the answer lives.
Every editor you open from the map has a Return to Flow button at the bottom of the panel, so you're never more than one click from the journey view, and nothing changes or saves just by looking.
Check your Form Setup
One more setting lives outside the Flow map. Head back to Form Setup, where you'll find the closed message alongside your registration window and capacity. That grouping makes sense: the closed message is what takes your form's place once those settings shut it.
Scroll to the bottom of Setup and you'll find When Closed. The message box holds a heading and a paragraph, with the same Field button and dynamic fields you used on the verification page, so a closed message can still name the event and the dates it ran. Underneath sits a live preview and an optional icon, four to choose from, each one setting the tone before anybody reads a word.
Before you go: click Save, top right. It's easy to forget, and closing the tab without it throws away everything you just set.
That's the whole map, and that's your form built. Flow is where you come back to change any part of it, preview the journey end to end, and call your registration finished.
Before you move on
- Verify is optional and off by default, turn it on only if you want attendees to review their answers before submitting.
- Dynamic field tokens work the same way on the verification page, the confirmation page, and the closed message, write once and reuse everywhere.
- Any editor you open from Flow has a Return to Flow button, so exploring a stage never puts your settings at risk.
- Save lives on Form Setup, not on the Flow map itself, don't close the tab before you click it.
Comments
0 comments
Please sign in to leave a comment.