Workshop booking software needs to carry the customer's purchase into the session staff will deliver. A single class reserves a place on one date. A course commits the customer to a series. A private group brings its own headcount, preparation needs and payment agreement. Those offers require different records even when one business sells all three.
The right system makes that promise clear to the customer and usable by the team: who is attending, what they paid for and what needs preparing. Gomry, Bookwhen and Ticket Tailor cover different combinations of scheduled visits, courses and public tickets. Their integration features matter after the booking workflow is understood.
One date, a course or reusable visits
A customer buying one public workshop expects a confirmed place at the stated time. A customer buying a four-week course expects access to its included dates. A customer buying prepaid visits expects credit they can use for later eligible bookings, not a place reserved automatically in every session.
That distinction changes the software choice. A studio teaching a fixed progression may need course enrollment most. An operator offering repeat drop-in pottery classes may need reusable visits and a timetable. A business adding a public festival or guest workshop may also need a separate Event ticket.
Gomry: recurring workshops and separately ticketed Events
Gomry offers configurable, ready-to-use software for small and midsize experience businesses. Experiences are its recurring bookable offerings, with schedules, capacity and hosts. A Bundle supplies prepaid visits across selected Experiences; customers use that balance when booking individual dates.
Experiences supports recurring sessions booked separately. A course promising every date needs an explicit course-wide enrollment arrangement; a recurrence or a Bundle alone does not establish that commitment.
Separate Events suit public admission outside the regular class offer. For eligible Event tickets, guests can transfer a ticket from their ticket page or app. The recipient signs in to accept before becoming the ticket holder. Transfers are on by default and can be disabled per ticket class. They do not transfer Bundle credit or move a customer to another class date.
Bookwhen: course enrollment and flexible passes
Bookwhen can sell one course ticket covering all the dates in a course entry. Paid course tickets require Lite or above. The customer purchases the course commitment rather than booking each date independently; a course ticket cannot cover only a selected subset of that entry's dates.
Its passes support a different purchase: a block of eligible classes, with at least one eligible ticket selected when buying the pass and later bookings redeemed under the same email. Passes require Standard or above and cannot redeem against course, group or free tickets. Their ticket and entry restrictions determine which classes customers can use.
Bookwhen memberships also require Standard and Stripe. Recurring payments place customers in a membership group that can receive exclusive free or discounted tickets. That access model should not automatically be treated as a limited monthly visit allowance.
For a business whose central offer is a fixed course alongside drop-in classes, these purchase and redemption differences are more important than the number of integrations listed on a feature page. The Bookwhen alternatives guide covers the wider operating and migration decision.
Ticket Tailor: public tickets and recurring occurrences
Ticket Tailor's recurring events share core details and ticket types across occurrences, with capacity set per occurrence and overrides where needed. A weekly course sold through one ticket can instead use a single event whose description and confirmation explain the session dates.
Ticket bundles combine tickets or products at one price. Its memberships can provide validity periods, redemption limits, member-only tickets and discounts. Those products need their own booking configuration; they are not automatically equivalent to Gomry Bundle credits across Experiences.
Ticket Tailor also documents API and MCP tools for event series, occurrences, orders, ticket issuance and membership operations. Organizer access through an assistant is therefore not exclusive to Gomry. The Ticket Tailor comparison develops the costs and workflow differences.
| Customer purchase | Gomry | Bookwhen | Ticket Tailor |
|---|---|---|---|
| One scheduled session | An Experience booking or Event ticket | A ticket for the selected class | A ticket for an event or occurrence |
| A fixed course | Experiences supports sessions booked separately; an Event ticket can represent the stated program | A course ticket covers the dates in its entry | A single event ticket can represent the course dates explained to the buyer |
| Reusable access | Bundle visits for selected Experiences | Eligible class passes or membership-group tickets | Configured membership redemptions and benefits |
Give staff the information needed to deliver the workshop
An order and an attendee are not always the same person. One buyer may purchase several places, each with its own materials choice, allergy information or accessibility requirement. Those details need to remain connected to the participant who will arrive, not only to the purchaser's email.
For public seats, an Event's ticket classes, capacity and registration questions define the offer. Gomry's Event participant export includes ticket types, registration status and custom-question answers. The instructor or preparation team can use those records to organize the session. Experience booking history has a separate dashboard export, as explained in the data-export guide.
Collect the participant information needed to prepare and deliver the activity.
Changes also need a clear handoff. A transfer changes who attends; a cancellation may release a place; a refund changes the financial record. The published policy should explain which action the customer can take and what the staff must do afterward.
Capacity is more than the room's seat count
A pottery workshop may be limited by wheels or firing space. A cooking class may have enough chairs but too few workstations. The smaller constraint determines the number of places the business can deliver safely and comfortably.
For example, a studio could have the following limits:
| Constraint | Maximum | What can change it |
|---|---|---|
| Physical places | 12 | Room layout or a private buyout |
| Staff ratio | 10 | Instructor absence or assistant availability |
| Equipment | 8 | Broken or reserved tools |
| Material kits | 12 | Supplier delivery or personalized choices |
| Safety and accessibility | Set by the activity | Participant needs and local requirements |
In this example, eight working equipment stations limit the workshop even though twelve people fit in the room. The operator uses that limit to set the number of sellable places.
Private groups need an agreed scope and payment record
A private birthday booking for fourteen people is not simply fourteen places on a public timetable. The team needs the agreed date, headcount, activity, special requirements and total price, plus any deposit, balance and due date. A changed headcount may alter materials and price before the final staff brief.
For a private buyout, agree the date, headcount, price and payment schedule before opening checkout. A quote and deposit agreement are separate from approval of a full-price Event ticket. The private-event guide explains the handoff from agreement to participant records.
This work has a cost even when no software subscription is involved. For example, twenty private inquiries a month at thirty-five minutes each for emailing, quoting, payment follow-up and updating records amount to roughly 11.7 hours of administration. The business's actual hourly cost determines what that time is worth; it is not a measured Gomry saving.
Publish the cancellation, transfer and refund terms alongside the offer. For fees and the timing of bank payouts, see the pricing page.
Where AI applications fit
For a separately ticketed public Event, an application can search Gomry's catalog, retrieve ticket choices and registration questions, and continue into a supported purchase or checkout link. An AI concierge helping someone plan a weekend can therefore connect a workshop recommendation to that Event's ticket checkout.
This consumer purchase route is not recurring Experience enrollment or the redemption of Bundle visits. A customer buying a public workshop ticket and a regular student booking with prepaid class credit still use different workflows.
Organizer MCP supports another task: compatible assistants can work with authorized event and attendee operations on the organizer's account. It does not bring an audience by itself. Product teams can use the consumer application guide, while the Agentcard article explains one purchase integration.
Choose around the offer that takes the most work
For a fixed teaching progression, prioritize how the customer enrolls across the dates. For flexible repeat visits, prioritize credit eligibility, expiry and individual session capacity. For public tickets, prioritize participant records and the path from purchase to admission. For private groups, retain the agreed scope and outstanding payment in the invoicing workflow as well as the delivery records.
A representative demonstration can use a twelve-seat public workshop, a four-week course and a fourteen-person private booking. Include one transfer, a missed course date and a changed private headcount. After the changes, staff should be able to prepare the session and explain what the customer has paid for from the saved records. That is a more useful test than a tour of unrelated features.
Gomry fits a business combining recurring workshops with separately ticketed public Events. For private groups, keep the agreed scope, headcount, total price and any staged payments connected to the booking so staff can prepare the session and explain the remaining balance. Bookwhen's course enrollment can matter more where one purchase must cover a fixed series. Ticket Tailor is relevant where event occurrences, ticket products and entry operations are the main requirement.