A drag-and-drop canvas where you lay out each registration step—Form, Ticketing, Add-ons, Order Summary, Thank-You—in any order. Visual arrows show every branch, so complex logic stays readable. This allows organizers to design sophisticated journeys without developer help. For example, employees jump straight to the thank-you page; external guests come to Ticketing, then an approval queue. 1 Pn

​
Map the journey

Flow Builder is a drag-and-drop canvas where steps—Form, Ticketing, Approvals, Add-Ons, Order Summary, Thank You—snap together like blocks. You can clone, rename, or delete any step except the final confirmation, and branches reconnect automatically to prevent dead ends.

​
Lean and conditional forms

Use Custom Fields (text, number, dropdown, multi-select, rich-text, country, session picker) and apply Conditional Logic to surface questions only when relevant—“dietary restrictions” after “Attending In-Person,” phone number if “Send SMS updates” is checked. Conditional logic keeps forms short for most users while still gathering the detail you need for logistics or personalization.

​
Branch for divergent audiences

A branch splits the flow based on form answers, ticket selections, or invite-list membership. For instance, employees can skip Ticketing and land on the success page, while prospects pass through payment and approval. Branching serves multiple personas inside one URL.

​
Gate with tickets, coupons, and invite lists

Inside any registration flow you can drop a Ticketing step to price tiers, set sales windows, and restrict purchase by coupon, email domain, or invite list CSV. Hidden or locked tickets support partner bundles or staff passes; visible tiers tease upgrades without exposing codes. By embedding checkout in the flow, payment and profile data converge into a single attendee record.

​
Speed with skip-ticketing and unassigned tickets

For targeted campaigns, append ?ticket_id=XYZ&coupon=ABC&skip_ticketing=true to the landing page and the flow jumps straight to Order Summary, shrinking click-count and preserving promo-code confidentiality. Enable Assign Later if corporate buyers want to secure tickets before naming attendees; finance books revenue immediately, and individual registrants receive links to finish their details when ready.

​
Protect capacity and data quality

Set a registration cap under Advanced Settings; once hit, the system either stops new sign-ups, pushes them to Approval, or holds a wait-list. Apply Domain Restrictions or Invite Lists to block select email addresses and ensure only qualified guests can register, eliminating manual vetting and last-minute cancellations.

​
Branding your flow

You can add custom CSS styles to each step in the registration process using the flow branding option and customize your registration page as per your company’s branding guidelines. You can customize a few additional pages, such as the error or the loading page.

​
Approvals

Turning on Attendee Registration Approval lets organizers screen every request before it converts to a confirmed seat. When you Approve; Zuddl flips the status to Approved, issues the confirmation email with calendar block, and, for paid events, unlocks the payment step. When you Reject to decline; the Registration Rejected email triggers and the seat returns to inventory. Bulk actions approve or reject all entries that match a filter—useful when you import an invite-list and trust its entries. Approval gates pair neatly with Registration Capacity. When you set a hard cap, you can choose New registrations need approval once the limit is reached; the system then holds overflow requests in Pending so you can cherry-pick high-value guests.