Events implementation guide

How to create and manage Events in Lead Connector

Plan the event type, publish the attendee experience, configure tickets and notifications, test registration and payment, then manage attendance and follow-up from one connected workspace.

Explore the Events feature

Decide the event model before you build

Start with the attendee journey and operating rules. Ticketed and RSVP events cannot currently be converted into one another after creation, so define the commercial and registration model first.

Choose Ticketed for paid, VIP or inventory-controlled experiences; choose RSVP for free confirmation without checkout.
Decide whether the experience is in-person or online and how attendees receive access.
Define capacity, ticket inventory, sale windows, registration deadline and refund policy.
Map confirmation, reminder, check-in and post-event follow-up before publishing.
Test as a real attendee on mobile and desktop before switching to live mode.

Event setup, step by step

1. Create the event

Open Events, choose Ticketed or RSVP, then enter the event name, cover image, short summary and detailed description. Save the first version as a draft.

2. Set date, time and time zone

Choose start and end dates and the display format. Ticket sales, sessions and coupon periods use the event time zone, so confirm it before launch.

3. Configure the location

For an in-person event, add the complete address. For an online event, add the session title, meeting URL, joining instructions and the schedule that controls link visibility.

4. Add the organizer

Add the organizer image, name and required email, plus an optional website and phone number. These details appear publicly in the Hosted by section.

5. Build tickets and coupons

For Ticketed events, create free or fixed-price ticket types, quantity and sale period. Add optional percentage coupons, active dates, usage limits and ticket restrictions.

6. Add schedule and speakers

Create sessions within the event window, define the stage or room, add descriptions and assign speakers with their profile, tagline and social links.

7. Design pages and checkout

Choose which event sections appear, customize the event and checkout design, add only useful registration fields, require terms where appropriate and review mobile and desktop previews.

8. Configure registration and notifications

Set the deadline and total capacity, configure allowed check-in payment statuses, organizer alerts, attendee confirmations and reminders, sender identity, slug, favicon, tracking and embed code.

9. Test before publishing

Keep live mode off while testing. Complete RSVP or checkout, verify ticket inventory, coupons, required fields, email delivery, online access timing, duplicate behavior and QR eligibility.

10. Publish and share

Turn on live mode when eligible payments are ready, publish the event, then share its public URL or approved embed code. Unpublishing preserves registrations but does not refund them.

11. Manage registrations

Search and filter registrations, review tickets, revenue and refunds, manually add attendees where appropriate and process eligible cancellations or refunds from the registration record.

12. Check in and follow up

Use QR scanning for eligible in-person attendees. Trigger event workflows for welcome, resources, surveys, offers, tasks and separate treatment of attendees and no-shows.

Launch checklist

Public experience

Event name, summary, description, schedule, speakers, location, organizer and FAQs are accurate on mobile and desktop.

Commercial rules

Tickets, quantities, sale periods, coupons, capacity, deadline, payment status and refund policy are documented and tested.

Automation

Confirmation, reminders, internal alerts, date-relative waits, check-in actions and post-event follow-up have stop rules and owners.

On-site operations

Staff can search attendees, add approved registrations, scan QR codes, handle exceptions and escalate payment or access issues.

Common event-launch mistakes

Choosing the wrong type

Ticketed and RSVP cannot currently be switched after creation.

Going live before testing

Test checkout or RSVP, inventory, coupons, delivery, access and check-in before real promotion.

Treating registration as the finish

Design reminders, on-site actions and post-event follow-up before publishing.

Assuming unpublish means refund

Cancellation or unpublishing does not automatically return eligible payments.

Ignoring CRM ownership

Define who owns new event contacts and which actions the sales or service team must take.

Scope and operating responsibility

Available event, payment, workflow and communication options can vary by account, plan, region and connected provider. The organizer remains responsible for event terms, privacy, consent, recording, taxes, refunds, accessibility, venue safety and applicable local requirements.

Events setup questions

Can I change an RSVP event to Ticketed later?

No. Choose the event type carefully; it cannot currently be switched after creation.

Can one ticketed event offer both free and paid tickets?

Yes. Create multiple free or fixed-price ticket types with individual quantities and sale periods.

When should I enable live mode?

After testing the full registration journey and confirming the connected payment provider and all commercial rules. Test mode does not process real payments.

Can staff add walk-ins or phone registrations?

Yes. Eligible attendees can be added manually from registrations, keeping tickets, confirmation and inventory connected.

Does cancelling an event automatically refund tickets?

No. Refunds must be processed from eligible registrations; unpublishing or cancelling alone does not return payment.

Launch with a tested attendee journey

Build one event in test mode, complete the full registration and check-in flow, then publish when every owner and exception is clear.

See plans and pricing