Skip to main content

Registration

Registration tools help event teams collect attendee details, import participants, issue QR badges, verify attendance, and manage check-in — through the mobile app, the web, or WhatsApp.

Features​

FeaturePurpose
Registration SetupThe single event-scoped page for registration settings, the attendee form, WhatsApp Flow registration, and approval/payment policy.
Registrations listView, search, edit, and manage participant records.
Registration detailsReview status, QR badge data, claim state, payment status, and participant actions.
Registration reviewsApprove or reject registrations that require manual review (e.g., WhatsApp Flow submissions).
Delegate profilesView individual attendee profiles with complete registration and communication history.
ImportAdd participant records in bulk.
Check-inMark participants as present at the event (see Operations).
AnalyticsReview registration and attendance performance.
  1. Open Registration Setup for the event and configure registration settings (mode, visibility, ID format).
  2. Build and publish the registration form on the same page.
  3. If using paid registration, configure payment terms in the Approval & Payment section (see Payments for the payment provider itself).
  4. If using WhatsApp registration, enable it in the WhatsApp Registration section and assign a Flow — pick an existing one or generate one from the published form. See WhatsApp.
  5. Test the form with a sample registration on mobile and WhatsApp.
  6. If using manual approval, review incoming registrations from Registration Reviews.
  7. Import existing participants if needed.
  8. Use check-in during the event.
  9. Review registration analytics after the event.

Registration Modes​

Registration can support different attendee entry paths:

  • External registration sends attendees from the mobile app to an organizer-provided registration link.
  • In-app form registration lets attendees complete a published registration form inside the mobile app.
  • Claim-only registration lets imported attendees claim an existing registration with their registration number and email.
  • No registration action is used when the event does not accept registration through the mobile app.

Choose the mode that matches the organizer's event process. If an external URL is used, test it from a mobile device before launch.

Registration Setup (Unified)​

Registration Setup is the single event-scoped page for the whole registration journey: settings, the form, WhatsApp Flow registration, and approval/payment policy. Reach it from the event sidebar under Event Settings → Registration Setup.

The page includes:

  • Registration — Registration methods, ID format, confirmation, cancellation, and check-in settings (the same settings previously on a separate Registration Settings page).
  • Attendee form — Drag, add, and configure registration fields; manage draft and published versions.
  • Public Registration URL — Copy and share the attendee-facing registration link.
  • WhatsApp Registration — Enable WhatsApp registration and discovery, and assign the Meta Flow the event uses: pick an existing published Flow, or generate one directly from the form's own fields with Generate Flow from this form. Generating creates and publishes the Flow in Meta and assigns it in one step. If the form changes after a Flow was generated, the card shows Rebind required; Regenerate Flow from this form publishes a replacement and retires the old one, since a published Flow's JSON can never be edited in place.
  • Approval & Payment — Automatic or manual approval policy, and payment amount, currency, and collection mode for paid events.

Category-Based Pricing​

An event can charge different amounts for different attendee types (delegate, student, member, and so on) by putting prices on the options of a single choice field.

To set it up, in Registration Setup → Attendee form:

  1. Add a dropdown, radio, or checkbox field — Category is the usual one.
  2. Give each option a Price (₹, incl. tax). Leave the price empty on options that should not affect what the attendee pays.
  3. Publish the form version.

How it is charged:

  • The attendee is charged the exact price of the option they selected.
  • Only one field may carry prices. The server charges the single priced option that was selected and rejects a submission matching two, so the form editor refuses to publish a form that prices two different fields.
  • Prices are gross — the figure entered is exactly what is collected. There is no separate tax component, so include any GST in the amount and say so in the option label (for example, AFPI Delegate - ₹708 including GST).
  • The Payment amount in Approval & Payment becomes a fallback, used only when a registration selects no priced option. When tiered pricing is in use the field is relabelled and the detected tiers are listed above it.

The form editor shows a Sets price chip and the full tier list on any field that carries prices, so the pricing is visible without opening each option.

Registration ID Format​

You can configure how registration IDs are generated using a prefix, start number, padding, and an optional year segment. The format is useful when events need structured IDs for badges, check-in, and reporting.

Registration ID format options:

  • Prefix — Optional. Letters, numbers, hyphens, and underscores. Example: REG, KASICON.
  • Start number — The first sequence number. Defaults to 1.
  • Padding — How many leading zeros to add. 0 means no padding. 3 produces 001, 002, 003.
  • Include year — Appends the current year before the sequence number.
  • ID separator — The character placed between segments. Default is a hyphen (-). Can be configured to use a different separator or none.

The resulting ID follows the pattern {prefix}{separator}{year}{separator}{padded-sequence}. Empty parts are omitted, so a plain start number with no prefix or year produces simple IDs like 1, 2, 3.

The admin settings show a live preview so you can confirm the format before saving.

Registration Reviews​

When manual approval is enabled (for example, for WhatsApp Flow registrations), incoming submissions appear in the Registration Reviews page under the Audience section.

Each review entry shows:

  • Full name, email, and phone
  • Organization, designation, and category
  • Submission timestamp
  • Source (WhatsApp Flow, web form, etc.)

Reviewers can approve or reject each entry. Approved registrations are persisted as full records and trigger confirmation notifications. Rejected entries are recorded for audit.

Delegate Profiles​

The delegate profile view provides a single page showing everything about one attendee:

  • Registration details (number, category, status)
  • Payment status and history
  • QR badge
  • Communication audit (whatsapp messages, emails sent)
  • Session attendance records
  • Certificate status

OTP Reclaim Transfer​

OTP reclaim transfer helps support cases where a registration has already been claimed but the organizer allows it to be moved after OTP verification. When enabled, a signed-in attendee can verify ownership and transfer the registration to their current account.

Use this carefully for attendee support. Confirm the attendee's identity, event, registration number, and organizer policy before advising a transfer.

Alternate Email​

Registrations and user profiles can include an alternate email. This helps support attendees who registered with one email but sign in or receive communications through another.

When searching or troubleshooting, check both the primary email and alternate email before concluding that a registration is missing.

Legacy QR Settings​

Older events or deployments may use the legacy QR settings to configure the attendee QR lookup URL and banner image. Use these only when the event still relies on that earlier flow.

Registration List and Details​

Use the registration list to search and manage participants. The detail page is the organizer's source of truth for attendee registration status, QR badge data, claim state, payment status, and confirmation actions.

Common actions:

  • Create a registration manually.
  • Edit attendee information.
  • Review primary and alternate email details.
  • Review registration status and payment status.
  • Resend confirmation when needed.
  • Help an attendee claim or unclaim their registration.
  • View the delegate profile for full history.
  • Export participant data for event operations.

Import​

Import is used when the organizer already has a participant list. After import, attendees can claim their registration in the mobile app using their registration number and email, then verify by OTP. If alternate email data is available, keep it accurate so support teams can identify attendees more reliably.

Check-In​

Check-in is handled through Ops Attendance for event-day operations. Confirm scanner devices and staff accounts have access before event day. See Operations for details.

Attendee Support Notes​

  • Mobile users can open My Registrations, claim imported registrations, verify by OTP, view registration details, and show QR badges.
  • Attendees can register through WhatsApp if WhatsApp is enabled for the event (see WhatsApp).
  • If a registration requires payment, the attendee must complete payment before the registration is confirmed (see Payments).
  • If a user cannot claim a registration, confirm the registration number and email match the imported record. Also check alternate email when available.
  • If a user cannot see a QR badge, confirm they are signed in and the event uses registration-enabled QR badges.
  • If a registration is already claimed, confirm whether OTP reclaim transfer is enabled before advising the attendee to retry.
  • If a user changed devices, ask them to sign in again and open My Registrations.
  • For WhatsApp registrations awaiting manual review, advise the attendee that their registration is under review and they will be notified when approved.