Selstack is a platform for creators and businesses to build a public selling page, share individual offers, accept supported payments and bookings, and manage the resulting orders and customer details. A “Stack” is a selling page. This guide explains the relevant workflow and the seller’s responsibilities; payment methods, account requirements and some features depend on the business configuration and plan.
Package and deliver topic, date, time zone, capacity, joining instructions, replay policy and reminders in a way that gives customers a paid event customers can join without searching through old messages.
Creators can package knowledge, access and digital delivery into focused Selstack offers without turning every launch into a custom technical project.
Package a result, not a vague promise
Describe the audience, the progress they can reasonably expect and exactly what they receive. For this offer, define topic, date, time zone, capacity, joining instructions, replay policy and reminders. Separate teaching, access, files, feedback and live time so buyers can judge fit before paying.
Choose a delivery model you can sustain
Set dates, capacity, access duration, file formats, meeting details and support boundaries before launch. If delivery depends on a cohort, approval or live session, make that timing visible. Do not promise unlimited access or attention without the resources to provide it.
Build the Selstack offer and hand-off together
Use Course for hosted modules and learner progress, Ticketed event for paid attendance and check-in, or Digital product, Service, Appointment, Lead form or Payment link for the other delivery models. Keep the public page focused, then make the portal, pass, confirmation, download, booking or follow-up explain what happens next.
Price for delivery and support
Include preparation, platform fees, revisions, moderation, customer support and refund exposure when setting the price. A lower price is not helpful if it creates a cohort, membership or service the creator cannot reliably deliver.
Launch to a specific audience
Use proof and examples you own, explain who the offer is not for and send traffic to one canonical link. Test purchase and delivery on mobile before launch. Monitor capacity as closely as sales so new orders do not weaken the experience of existing customers.
Improve the product after real use
The desired result is a paid event customers can join without searching through old messages. Review completion, attendance, access problems, support questions, refunds and repeat purchases. Avoid publishing a meeting link publicly or forgetting to explain time zones and replay access. Update the offer when evidence shows a recurring misunderstanding or delivery bottleneck.
A practical example
Use an Appointment or appropriate paid offer with date, time zone, capacity, meeting method and replay policy.
When the result is unexpected
Appointment reminders are Pro where available; otherwise send a planned campaign or direct confirmation without claiming automatic reminders.
Connect ticket sales to attendance
Selstack’s event workflow links the public event offer, ticket purchase, attendee information and check-in. The organiser should be able to explain how someone moves from hearing about the event to presenting a valid pass at the door. That requires more than a poster and a payment button. Customers need an accurate time, location, ticket description and support route. The event team needs a consistent attendance record so that a paid ticket, a cancelled booking and a duplicate scan are not treated as the same thing.
Publish the practical details
Choose a specific event name and explain what attendees will experience. Add the start and end times, event time zone, venue or joining arrangements, ticket price and relevant capacity. State restrictions that materially affect the customer’s decision, such as who the event is intended for or what a ticket includes. If sales need to close before the event starts, configure the appropriate closing time. A customer should not need to infer an important deadline from a social caption that may be separated from the public selling page.
Confirm the result
Use the venue search and select the intended Google Maps place when configuring an in-person event. Check the place name, formatted address and map position rather than accepting the first similarly named result. A typed venue name can be ambiguous across cities and countries. Review the map shown on the public page and the information passed to attendees. If the event is online, explain where joining information will be supplied and when it will be available. Keep private access information out of a publicly shared poster when that would defeat the ticketing arrangement.
Make ticket choices understandable
Describe the difference between available ticket options in terms of access or included benefits. Avoid creating several labels that all appear to promise the same thing. Check capacity and pricing against the actual event plan, and explain any material conditions before payment. If several people can be included in one purchase, review how attendee details and passes are handled in that configured journey. Do not assume a receipt for one transaction is automatically the entry document for every person arriving with the buyer.
Test the confirmation and pass
Run an authorised test from the public event page and inspect the resulting confirmation and attendee pass. Verify the event title, date, time zone, venue and ticket details on a phone. Check that the QR pass belongs to the intended attendee record and that a customer can retrieve the relevant information after purchase. An organiser’s dashboard preview is useful, but it does not replace testing the customer hand-off. If the confirmation is missing, investigate the order and attendee records before asking the customer to pay again.
Prepare the people doing check-in
Give authorised event staff the access and instructions needed for their role. Explain how to scan a pass, find an attendee manually and recognise an existing check-in. A duplicate scan should show that the pass has already been used rather than silently adding another attendee. Keep a practical alternative for a customer whose phone battery is flat or whose screen cannot display the code. Staff should resolve an exception against the recorded attendee information, not accept an unrelated bank alert as proof of entry.
Plan for changes and questions
Decide how the team will communicate a venue change, delay or cancellation before an urgent situation occurs. Use the legitimate event contact information and refer customers to the current event details. Explain the available options without promising a refund status that has not been recorded. If an attendee reports a problem, collect the event name and a safe order or ticket reference. Do not request card security details or a password to look up a booking. Keep internal notes factual and limited to what the team needs to resolve the issue.
Review the event after it ends
Compare tickets sold, attendance, check-in exceptions and any recorded refunds. These figures answer different questions: selling a ticket does not prove attendance, and a check-in count does not explain every payment outcome. Look for bottlenecks at entry and questions that could have been answered on the public page. If staff repeatedly had to clarify the venue or ticket type, improve those details before promoting another event. A short operational review is more useful than simply reporting that the event was busy.
Respect the purpose of attendee information
Use attendee details for the event and necessary customer service. Invite future marketing separately where appropriate and respect each person’s choice. Do not export a guest list into unrelated campaigns simply because the organiser has access to it. Limit staff access to the records their role requires and retain information according to the business’s legitimate needs. Selstack connects ticketing and check-in, while the organiser remains responsible for the event itself, attendee communication and the commitments made when tickets were sold.
Review Selstack pricing for current plans and online payment fees. For related tasks, visit the Help Centre. If the recorded result remains unclear, contact support with the relevant safe reference.
