Recurring ticketing software needs to distinguish a place on one date, enrollment across a course and credit for future visits. Gomry uses scheduled Experiences for recurring bookings, Bundles for prepaid credit and Events for separate admission. It also provides organizer MCP (Model Context Protocol) and consumer-event commerce for supported agent workflows.
Why Gomry fits recurring experiences and separate event admission
- An Experience booking reserves a scheduled place. Capacity and the host belong to the session.
- A Bundle provides prepaid credit. Customers redeem it across selected Experiences.
- An Event ticket provides separate admission. Eligible public events can also be evaluated through Gomry's consumer-commerce flow.
Compare recurring-event platforms and their integration boundaries
Ticket Tailor documents repeated occurrences and exposes event-series and occurrence tools through MCP. Bookwhen combines schedules with passes and memberships; its published public API is read-only. Eventbrite combines ticketing with a discovery marketplace. Gomry separates scheduled Experiences from ticketed Events and offers authenticated organizer tools alongside a consumer-event commerce interface.
| Your priority | A useful comparison |
|---|---|
| Repeated ticketed dates | Ticket Tailor’s occurrences against the intended Event or Experience model in Gomry |
| Existing class packs | Bookwhen pass rules against eligible Gomry Experience Bundles |
| Marketplace discovery | Eventbrite’s actual booking contribution against proposed additional channels |
| Agent-operated workflows | The exact MCP or API actions, permissions and resulting booking records |
Keep membership entitlements separate from recurring billing: Gomry Subscriptions are live, while Memberships is private beta.
Give an agent a precise recurring-event task
A staff assistant and a customer-facing agent need different information. Gomry MCP exposes supported account operations under the organizer's permissions. A useful task names the event and intended action, such as retrieving attendees or reviewing sales for a specific program.
The consumer catalog and commerce flow serve applications helping customers choose and buy eligible event tickets. Preserve the selected date and ticket option throughout that journey. The existence of an event integration does not establish how every recurrence, Experience or prepaid product is exposed. Verify that coverage for the offer being sold.
The purchase can use an enabled checkout integration or a link that opens Gomry checkout with the ticket type already selected. Direct checkout access is configured for the connected application.
First, decide what “recurring” means for your offer
| Offer | What the customer buys | The system model to validate |
|---|---|---|
| Weekly drop-in | One place on one date | Separate occurrence, its capacity, and its change rules |
| Rolling time slots | Access to a chosen time | Inventory and availability across many slots |
| Multi-week course | One commitment covering several sessions | One enrolment plus attendance or completion across dates |
| Monthly membership | Ongoing eligibility or credits | Membership state plus booking and cancellation rules |
| Seasonal programme | A defined set of dates with occasional exceptions | Shared setup with controlled overrides |
These should not all be configured as the same thing. Ticket Tailor’s current recurring-event documentation, for example, says occurrences share core event details and ticket setup, and separately advises a single event when one ticket includes multiple weekly course dates.
The operational questions to put in every demo
Can one date change safely?
Create eight dates, then change capacity on one, move one start time, cancel another, and hide a third from sale. Look at the buyer page, confirmation, staff calendar, reports, and customer message. A good system preserves a comprehensible history while showing what is now true.
Ticket Tailor’s published documentation describes managing occurrences and setting dates available, unavailable, visible, or hidden. Compare those controls with the date exceptions in the proposed schedule.
Can the system sell the same experience in more than one way?
Many operators need drop-ins, a multi-date package, member access, a concession price, and occasional private allocation. Create each one and check whether capacity is shared correctly. Check that two products cannot sell the same final place.
What happens after a cancellation?
Test a customer cancellation before the policy window, inside it, and after a session is cancelled by the organiser. Confirm customer communication, capacity release, waiting list, entitlement restoration, refund record, and staff instructions. The customer-facing policy must be clear before automation is activated.
Can the door trust the record?
Give two staff members a live attendee list. Include a valid ticket, duplicate scan, transferred name, member reservation, cancellation, and a walk-in. Confirm permissions and the single action staff should take when there is a discrepancy. Give staff a way to resolve mismatched records at the entrance.
Does a customer history survive the series?
Find a repeat attendee. Can staff see which dates they attended, what they bought, what they cancelled, and what access they hold? If the business relies on repeat attendance, this is more valuable than a report that only counts tickets sold.
Capacity and waitlists need a written policy
Define the booking rules before configuring automation:
- Which capacity is binding: room, staff, equipment, safety ratio, or ticket allocation?
- Is a held place counted while payment is pending?
- Who joins a waitlist and for how long is an offer valid?
- Does a member have priority, and if so, until what point?
- Is a late cancellation refunded, credited, or forfeited?
- What happens if the organiser cancels a date?
Write the decisions in customer language, then run them through the system with the people at the door and in support.
Customer communication is part of ticketing
Every recurring programme needs a single source for date, time, location, arrival information, changes, and policy. Before launch, intentionally create an exception and inspect every touchpoint: public event page, calendar link, confirmation, reminder, staff view, and customer support response.
Integration: verify the events you need
If recurring ticketing must update another system, turn the desired integration into a sentence: “When a person attends an occurrence, update their record in the CRM,” or “When capacity changes, update the website.” Then ask the vendor to identify the current endpoint, event, permission, payload, retry behaviour, and failure path.
Gomry’s API introduction documents organisation-scoped API keys and resources including events, attendees, and ticket classes. Read the API documentation. It does not itself establish support for every possible booking, membership, scan, or accounting event. Evidence needs to be specific to the integration you plan to deploy.
A controlled launch plan
Launch a single series first. Keep the policy set small: one cancellation rule, one membership rule if needed, one waitlist rule, and named people for support and finance. Run staff through test purchases and changes before opening sales. At the end of the first cycle, reconcile the records and list every manual intervention.
Expand after the team has resolved the exceptions found in the first series.
Frequently asked questions
Can recurring events have different prices?
They can, but the important detail is scope: does the price change apply to the whole series, selected future dates, or one occurrence? Test it before publishing a promotion.
Should every date have its own URL?
Not necessarily. A stable series page can be clearer for a repeating offer. Create distinct pages only when dates genuinely have distinct intent and content; otherwise avoid thin, duplicative pages.
Do I need memberships for repeat customers?
Use memberships when repeat access changes price, booking rights, limits, or cancellation treatment. A straightforward bundle or multi-date ticket can be sufficient for a simpler offer.
How should a recurring-event refund policy work?
Define notice period, refund or credit treatment, waitlist actions, staff ownership, and customer communication before setting the automation. Local consumer rules may affect the policy, so obtain appropriate advice.
What data should be portable?
Future occurrences, event settings, customers and consent, orders, attendees, attendance or check-in data, payments, refunds, and membership balances where applicable. Check whether relationships survive the export.
Configure a short series, change one date and cancel one booking. Ask staff to identify the current information and remaining entitlement before opening the rest of the calendar.
Agent-readiness assessment
Gomry scored 100/100 on Is Agentic and 91/100 on Ora in the assessments of gomry.com recorded on September 17, 2026. Is Agentic is powered by Ora and uses a different scoring model. The assessment details explain the scores and dated platform comparison.
Choose Gomry for repeat attendance with clear booking products
Set up the next short series in Gomry Experiences. Check a date change against an existing booking, then confirm the credit or payment outcome of a cancellation before opening the full schedule.