Skip to main content
Solved

Ticketed Events and full set up

  • March 11, 2026
  • 1 reply
  • 16 views
Journey to Empower

I’m hoping to learn from those of you who are a little further along with HoneyBook than I am.

My business focuses on retreats and events, along with wellness coaching and breathwork facilitation. I originally started using HoneyBook just for client management, but I’m realizing it can do so much more. That’s exciting… but also a little overwhelming as I try to figure out the best structure.

What I’m trying to build is a smooth process for ticketed events and retreats directly inside HoneyBook. Ideally, I’d love to manage everything in one place rather than using something like Eventbrite.

For example, I’m currently launching a wellness day event with about 150 tickets, along with options for sponsorships and a VIP weekend experience. My goal is that once someone purchases, they automatically move through a workflow that includes confirmation emails, waivers, questionnaires, and event updates.

I feel very confident in the event design and guest experience, but the systems and setup side is where I’m getting stuck.

If you run a similar business model — retreats, workshops, or ticketed experiences — I would really appreciate hearing how you’ve structured this in HoneyBook.

Any advice or examples of how you’ve set up packages, ticket sales, and automated workflows for attendees would be incredibly helpful. Thank you in advance for sharing your insight!

Best answer by Alicia Bauer

​@Journey to Empower  - This is a really exciting use case for HoneyBook, and it’s great that you’re thinking about the client journey this intentionally. It can support parts of what you’re describing, but it’s helpful to know that HoneyBook isn’t really built as a traditional ticketing platform like Eventbrite, especially when you’re talking about 100+ attendees.

Most people running retreats or workshops in HB usually structure it one of two ways:

Option 1: Smart File + Package Selection
Create a Smart File with packages for the different ticket levels (General Admission, VIP, Sponsorship, etc.). Guests choose their option, complete payment, and sign any agreements in one place. From there, you can trigger automations for confirmations, questionnaires, waivers, and event updates.

Option 2: Hybrid Approach
Use a ticketing platform (Eventbrite, etc.) to manage the ticket sales and capacity limits, then move confirmed attendees into HoneyBook for the client experience side — things like onboarding emails, waivers, questionnaires, and event communication.

The biggest limitation inside HB for ticket-style events is:

  • No capacity tracking

  • No true ticket inventory

  • No attendee-style registration management

That said, the automation + Smart File workflow is really powerful for managing the post-purchase experience once someone is registered.

If you’re planning to run a lot of events like this, it might be worth starting with one event workflow and refining it as you go. Once the structure is built, it becomes much easier to reuse for future retreats.

You’re definitely asking the right questions, the systems piece just takes a little trial and iteration at first. 💛

1 reply

Alicia Bauer
Forum|alt.badge.img+4
  • Alicia Bauer
  • Newcomer
  • Answer
  • March 11, 2026

​@Journey to Empower  - This is a really exciting use case for HoneyBook, and it’s great that you’re thinking about the client journey this intentionally. It can support parts of what you’re describing, but it’s helpful to know that HoneyBook isn’t really built as a traditional ticketing platform like Eventbrite, especially when you’re talking about 100+ attendees.

Most people running retreats or workshops in HB usually structure it one of two ways:

Option 1: Smart File + Package Selection
Create a Smart File with packages for the different ticket levels (General Admission, VIP, Sponsorship, etc.). Guests choose their option, complete payment, and sign any agreements in one place. From there, you can trigger automations for confirmations, questionnaires, waivers, and event updates.

Option 2: Hybrid Approach
Use a ticketing platform (Eventbrite, etc.) to manage the ticket sales and capacity limits, then move confirmed attendees into HoneyBook for the client experience side — things like onboarding emails, waivers, questionnaires, and event communication.

The biggest limitation inside HB for ticket-style events is:

  • No capacity tracking

  • No true ticket inventory

  • No attendee-style registration management

That said, the automation + Smart File workflow is really powerful for managing the post-purchase experience once someone is registered.

If you’re planning to run a lot of events like this, it might be worth starting with one event workflow and refining it as you go. Once the structure is built, it becomes much easier to reuse for future retreats.

You’re definitely asking the right questions, the systems piece just takes a little trial and iteration at first. 💛

Alicia, Brand and Web Designer + Honeybook Pro
Terms & PrivacyCookie settingsAccessibility statement

© 2025 HoneyBook Inc.