Skip to main content

Event Launch Workflow

Use this workflow when preparing a new event for organizers and attendees.

Steps​

  1. Create the event using the Event Create Wizard, including dates, the venue's IANA timezone, venue details, and mobile imagery.
  2. Add halls, venue information, venue map URL, and mobile event imagery.
  3. Add faculties and speakers, including categories and profile details.
  4. Create programs and sessions, then assign speakers, moderators, and committee members by role.
  5. Add event contacts, teams, sponsors, activities (or copy activities from a previous event), and documents.
  6. Enable Mobile Visibility when the event is ready for the mobile event list.
  7. Configure registration - choose the mode, build the form, set up ID format, and configure import if needed.
  8. If the event requires payment, configure category-based pricing and test the deployment's payment flow (see Payment Setup).
  9. If using WhatsApp, complete platform and per-event setup (see WhatsApp Setup).
  10. Configure certificates, including event enablement and category-specific designs when needed.
  11. Configure engagement tools such as feedback, quizzes, polls, and ask faculty.
  12. Review the mobile app event home, registration action, faculty profiles, and session screens.
  13. Share launch readiness with the organizer.

Validation Checklist​

  • Event appears in the expected environment.
  • Event timezone matches the venue, and the event remains ongoing through its complete local end date.
  • Event card and event home imagery match organizer branding.
  • Venue details, map URL, and optional event times look correct.
  • Sessions have correct timing, halls, and faculty roles.
  • Mobile Visibility is enabled when the event is ready for attendees.
  • Registration mode is tested: external link, in-app form, claim-only, or no registration action.
  • Public registration URL is tested when the event uses the public web form.
  • OTP reclaim transfer policy is clear to the support team if enabled.
  • Payment flow is tested end-to-end if the event requires paid registration.
  • WhatsApp registration and ticket delivery are tested if WhatsApp is enabled.
  • WhatsApp discovery and schedule answers use the event's local date and timezone if WhatsApp is enabled.
  • Template mappings are correct and templates are approved.
  • Certificate enablement, design, category overrides, and eligibility rules are reviewed.
  • Mobile navigation displays the expected event sections.
  • Support team knows the event name, organizer contact, WhatsApp number (if used), and payment help procedures.