Once your Onboarding Form and Ticketing Grid are complete, our Ticketing team builds your event page. Ticketing works only from what's submitted here — so the more complete and confirmed the details, the faster your page comes together and the fewer questions come back to you. If either is missing or incomplete, there's no way for the team to start building, and that delays your entire launch.
Your Ticketing Grid should include event dates and time slots, every ticket type with its price, and the allocation per ticket type. If this wasn't finalized before your contract was signed, just send us the approved final version as soon as you have it.
You'll receive a preview link before anything goes live.
Event pages run on photos — that's the core content we need from you. The more variety in ratios (square, vertical, horizontal), the better, since your images get used across different placements on the platform (collections grid, checkout, featured carousel), each with its own crop. High-resolution, well-lit images are what drive clicks and conversion.
What should you send us? Think about the full 360 of your experience: the venue itself, food and drinks if you serve any, and — most importantly — real people enjoying it. The more variety showing guests actually having a good time across different parts of the experience, the better your page performs.
Video isn't required for the page itself, but if you'd like to include one, share a YouTube link and we can embed it.
For full specs on image sizes, resolution, and content dos and don'ts, check the Marketing & Content page.
Your BD and PS reps send you the page URL via your Main Thread
Review everything: description, date/time, full address, ticket types, pricing, photos
Reply with your approval, or list any corrections needed
We apply changes and confirm — then it goes live
Double-check everything before you approve. Once the page is live and tickets are on sale, fixing pricing or ticket type mistakes gets complicated — and can affect guests who've already bought
For any updates post-launch, reply to your Main Thread with Reply All. Your BD and PS reps will coordinate the change.
If a guest has a ticket issue, direct them to bucketlisters.com/contact-us , where they can submit a request or email support@bucketlisters.com directly. You're welcome to submit this anytime, including weekends, but keep in mind our hours of operation are Monday-Friday 9 AM - 5 PM EST, so requests sent outside those hours will be answered as soon as we can.
During weekday business hours, you can also let us know through your Experience Main Thread (Reply All) and mention what you need, whether it's sending a broadcast, cancelling, or contacting one particular customer. Your BD and PS reps will make sure the Customer Service team gets involved.
Whenever we send a broadcast, whether it's a cancellation or another important update like a location or hours change, ticket holders are notified by both email and SMS. We also schedule a follow-up reminder after the first message, though the exact timing can vary depending on how much notice we have and how close we are to the event date. This gives your guests two chances to see the update and helps make sure it doesn't get missed.
The earlier you let us know about a cancellation, the more time we have to make sure ticket holders see the notice before the event. Less notice means less time for the message to land, which raises the risk of a guest missing it and showing up to a cancelled event.
To create a discount code, reply to your Main Thread. We'll need: the code name, discount percentage, usage limit (if any), and expiration date (if any).
All ticket sales go through Bucket Listers. Guests purchase on your event page, receive a confirmation email with a QR code, and present it at the door.
Requesting comp tickets
Send the following to your BD and PS reps via your Main Thread:
Name of event
Preferred event date/time
Ticket type
Number of tickets
Full name of ticket holder
Phone number ✱
Email address ✱
✱ We need both email and phone — tickets are sent to both. If the guest only has one, use yours as backup. If you have neither, send your own contact details and forward the tickets to them later.
Large guest lists? Create a spreadsheet with the fields above as columns — one row per guest — and attach it to your Main Thread message.