Registration

Registration forms
that ask exactly what your event needs.

Drag fields from a palette, drop them onto the form, publish. Every field flows into the seat allocation, the QR pass, the check-in screen, and the Excel export. Nothing gets stuck in a Google Sheet somewhere.

admin/events/summit-2026/form
Field types
✏️ Text
📧 Email
📱 Phone
▾ Dropdown
◉ Radio
☑ Checkbox
📅 Date
🎟 Coupon
Live preview
Register for Product Summit 2026
Full name *
Priya Nair
Work email *
Dietary preference
Vegetarian ▾
🎟 VIP coupon (optional)
VIP-A3KX9Z ✓
Register & get pass →

Enough to describe any attendee, not so many you need a manual.

Text, email, phone, number, dropdown, radio, checkbox, date, and a coupon field wired into VIP allocation.

🎨
Drag-and-drop builder
Palette on the left, form on the right, live preview alongside. Reorder by dragging. Publish is one button.
🎟
Coupon field built in
Attendee enters a code, it validates against the coupons table in real time. Valid codes trigger VIP allocation on submit.
🔀
Conditional fields
Show T-shirt size only if Attending in-person is Yes. Hide dietary if the field says No meals. No JS to write.
👁
Hide built-ins
Do not need Company or Designation for a private wedding registration? Toggle them off. Name and email are the only mandatory pair.
Server-side validation
Required, min length, regex, phone format. Enforced in Laravel FormRequest, not just JS. Bots and copy-paste attacks blocked.
📊
Custom fields export
Every custom field becomes a column in the Excel export. Sponsor asks for a T-shirt size sheet? Filter and download.

Ten minutes from empty event to open registrations.

1
Pick fields
Drag from the palette. Name, email, phone are on by default. Add company, dietary, T-shirt, whatever the sponsor asked for.
2
Set required and rules
Toggle required per field. Add conditional show/hide. Set dropdown options. Live preview updates as you edit.
3
Publish
One button. The form goes live at your tenant domain. Share the URL, drop it into the invite email, done.
4
Data flows everywhere
Registrations land in the admin panel. Custom fields show on the check-in screen. Export drops them into Excel with their column headings.

The Google Form that ate our Sunday.

2023, medical conference in Chennai. Client used Google Forms because it was free. 620 doctors registered. Then the sponsor asked for a segmented list by speciality. Turned out the client had used a free-text field for "speciality", so we had 47 spellings of "cardiology" including one that just said "heart". Sunday afternoon lost to Excel find-and-replace.

The issue wasn't Google Forms as a form tool. It's that the form data lived nowhere useful. Nothing knew a registration existed. Seat allocation was manual. QR passes had to be designed and mail-merged. Check-in was a paper list. Six tools, six exports, six chances to break.

So the form builder here is drag-drop, but every field flows through the same data model as everything else. Add a "speciality" dropdown once, and it appears in the seat allocation logic if you want to weight it, on the QR pass if you tag it as visible, on the check-in screen so staff can spot the cardiologists, and as a column in the export. Add once, use everywhere.

Conditional fields matter too. We show "dietary preference" only if the attendee ticks "attending dinner". Cuts form abandonment by roughly 15% in our measurements.

A pharma symposium in Kolkata, form to Excel.

  1. 4 weeks out. Client opens the form builder. Drags in Name, Email, Mobile (built-in). Then adds three custom fields: Speciality (dropdown, 18 options), MCI Registration No (text), Attending Dinner (yes/no).
  2. Conditional rule. If "Attending Dinner" = yes, show "Dietary Preference" (dropdown: veg, non-veg, jain, halal). Click Publish. Total build time: 8 minutes.
  3. Form goes live. Registrations flow in. Each carries all 5 custom fields. Speciality auto-normalises because it's a dropdown, no spelling variants.
  4. 3 weeks in. Sponsor wants "all cardiologists attending dinner". We filter Speciality=Cardiology AND Attending Dinner=yes on the admin panel. 214 rows. Export. Sent.
  5. Day of event. Check-in screen shows Speciality next to each name so ushers can direct doctors to speciality-specific breakout rooms. Saves 3 seconds per guest at the door.
  6. Excel export. All custom fields as their own columns with the field labels as headings. Dietary Preference column is empty for non-dinner attendees, filled for the 340 who said yes. Catering count clean and correct.

Zero Sunday-afternoon find-and-replace sessions. Client billed a 20% higher fee this year because the workflow felt "professional".

Form builders that also do the rest.

For a 600-attendee ticketed event, one-off registration flow, India 2026.

ToolModel / CostNotesVerdict
Google FormsFreeForm + sheet. No seat allocation, no pass, no check-in.Fine for surveys, not events
Typeform + Zapier stack₹4k-8k / monthBeautiful forms. Ties into other tools via middleware.6 tools, 6 failure points
Cvent Registration₹1.5L+ / eventFull-featured but heavy configuration. Weeks to launch.Right for 5,000+ attendee shows
SignupDesk formsIncludedDrag-drop. Every field flows into seat, pass, check-in, export.One tool, no seams

Vendor prices vary by region and negotiated discount. Ours is included in the platform fee.

Where custom fields end up.

🎨
Any field you tag as "show on pass" prints on the branded PNG. Ideal for speciality, table number, meal preference.
🔗
Every custom field appears in the CRM mapping dropdown. Map to any HubSpot or Zoho property, including your custom ones.
📊
Filter the admin list by any custom field. Export lands each field as its own column in Excel with the field label as heading.

Questions we get

What field types?
Text, long text, email, phone, number, dropdown, radio, checkbox, date. Plus a coupon field for VIP flow.
Better than Google Forms?
Google Forms captures data into a sheet. Ours captures data, assigns a seat, generates a branded QR pass, emails it, and syncs into check-in.
Conditional fields?
Yes. Show a field only when another field has a specific value. No JavaScript to write.
Do custom fields export?
Yes. Every custom field becomes a column in the Excel export alongside built-in fields.
Stop patching Google Forms.
Free demo. Build a real registration form on your event data in 20 minutes.