Ticketing wins the first transaction. It does very little for the second one.
Most Nigerian organisers rebuild their audience from scratch after every night: same flyer effort, same promoter chase, same cold start. Communities and experiences on Tickethub.ng exist to stop that reset. This article covers what each one is, how hosts schedule bookable sessions, how guests pick a date and time, and when to use which.
The short version
- A community is the public home for an ongoing brand.
- An experience is a listing guests book by session, not by ticket tier.
- Hosts add dates and time-of-day slots, with bulk add for busy seasons.
- Guests pick a date first, then a time. That order works better on a phone.
- Free experiences carry no platform fee, same as free events.
Communities: the home base
A community is a public page for a group rather than a date: creators, faith communities, run clubs, industry circles, alumni networks. Members follow it, and they see what you publish next without you having to find them again.
Events and experiences can be associated with a community, so discovery compounds instead of restarting. Use one when you have a repeating identity that is bigger than any single night.
Making a community page worth following
- Answer three questions in the about section: who belongs here, what happens next, and how to join.
- Use real photos from past sessions. Stock imagery reads as a page that has never actually met.
- Cross-link your events and experiences so a first-time guest always has a next step.
- Do not publish an empty shell. A community with no activity costs you trust rather than building it.
Experiences: bookable sessions
Experiences are listings guests book by session rather than as one concert-style event. Workshops, tours, tasting nights, studio sessions, fitness classes, hosted activities.
Each session is a specific time of day on a specific date, with its own capacity. That matches how people book activities everywhere else in the world, adapted for Nigerian hosts and Nigerian payment rails.
Single-seat bookings are the current default path. If you need party size controls, wait for them rather than faking multi-guest inventory in a spreadsheet outside the system, which reliably ends in a double-booked Saturday.
Scheduling as a host
From the experience dashboard:
- Add a date and a time of day for each slot you want to offer.
- Use bulk add to select a date range and tick morning, afternoon, evening, or custom times. This is the tool for a full season.
- Set a typical duration so end times fill in automatically and sessions do not silently overrun into the next group.
- Block dates you cannot host, including travel and public holidays, before anyone books them.
- Set meeting points per session where locations rotate.
Lead with the simple view of days that already have slots, then move to the full timeline when you need to edit capacity or fix a specific session.
Buffer your own time, not the guest's. Set the session duration to what guests actually get, and schedule cleaning and reset time in your personal calendar. A session that runs over is a session that starts late for the next group.
How guests book
On the public experience page, guests see a calendar of dates that still have availability. They pick a day, then a time slot with seats remaining, then book.
That date-then-time order matters more than it sounds. A flat list of every datetime is unreadable on a phone, and unreadable means abandoned. Waitlist options can appear when a slot is full, so demand you cannot serve today is still captured.
Meeting points and cancellation policies should be visible before payment. Expectations set after payment are complaints waiting to happen.
Fees and policies
Paid experiences use the same fee model as events: absorb or pass, decided by you. Free experiences carry no platform fee, exactly like free events.
Price for the depth of the session rather than by comparison to nightlife tickets. A three-hour workshop with materials is a different product from a club entry, and pricing it like one undersells it to the people most likely to book.
Publish a cancellation policy guests can read before they pay, and confirm live rates on the pricing page. The fee mechanics are in Tickethub.ng pricing explained.
Events, experiences, or both
The test is one question: do buyers choose among many times, or among ticket tiers for one night?
Use an event
One-night shows, conferences, parties, tour stops. Classic ticket tiers, one door time, everyone arrives in the same window.
Use an experience
Repeating activities across multiple dates and times. Workshops, tours, classes, studio sessions, small-capacity formats.
Use a community to brand the ongoing relationship across both. What you should not do is build a parallel tool outside Tickethub.ng that duplicates guest lists, because that is how check-in breaks and how two people end up holding the same seat.
Running a weekly format
Weekly experiences work when the promise is specific: the same host energy, a clear skill level, and a meeting point guests can actually find. Vary the theme, keep the ritual constant. Guests should be able to learn your calendar pattern without being told.
- Block holidays and travel early. Nothing erodes trust faster than a wave of last-minute cancellations.
- Decide underbooked sessions early. Merge or run small, but choose before the morning of.
- Use waitlists when popular times fill, and notify fairly when seats free up rather than quietly adding friends first.
- Message guests the day before with arrival tips. Treat upcoming bookings as a production schedule, not a list.
Doors still matter for experiences
Review upcoming bookings grouped by session date so you know who is coming in the next week or two. Guests should be able to see their session status and meeting point in their bookings list without messaging you.
Then check guests in with the same QR discipline you would use for a thousand-person event. Capacity is capacity, and a twelve-seat workshop with fourteen people in it is a worse experience than a queue.
Getting started
- Create or open your community if you have an ongoing brand.
- Create an experience with a cover, city, price, and duration.
- Add dates and time-of-day slots, using bulk add for a full season.
- Publish a cancellation policy and set meeting points.
- Share the public link and watch which sessions fill first.
- Iterate weekly on blocked dates, capacity, and creative.
Questions hosts ask
Can I run both a concert event and a workshop experience?
Yes. Use the format that matches how guests choose, and link both to the same community.
Can I change the meeting point for one session?
Yes. Set it on the session itself when locations rotate.
Can guests pick a date without a specific time?
No. Sessions carry concrete time slots so inventory stays honest and capacity means something.
Can I block a date after seats have sold?
Cancel with policy honesty and direct guest communication. Never silently hide a sold session.
Give guests somewhere to go next
Recurring formats create memory, and memory is what sells the next ticket without shouting. Build the ongoing version of what you already run.