Selling Tickets

General

Sell tickets directly from your event pages with secure payment processing, automatic confirmation emails, and a QR code on every ticket. Selling is included on every plan, including Free, and Event Schedule takes no cut of a ticket sale.

When you edit an event, the Tickets section offers three mutually exclusive modes. Pick the one that fits the event:

The Free plan's paid-ticket allowance

A Free schedule can sell paid tickets, up to 25 paid tickets per calendar month. There is also a backstop of 50 paid tickets a month across every schedule one account owns, so the per-schedule allowance cannot be multiplied by spreading events over several schedules. Pro and Enterprise remove both limits, and a selfhosted install is unlimited.

The allowance counts individual paid tickets, not orders, and several things never count against it:

• Free registration and RSVP - unlimited on every plan
• Zero-price ticket types - a $0 tier sells without limit, even on an event that also has paid tiers
• Add-ons - extras, not admissions
• Appointment bookings - they have their own separate allowance
• Bulk attendee imports

Two rules keep the allowance from landing at the worst possible moment:

• Cash and other offline payments are counted but never blocked. Money taken at the door is always recordable, whatever the count says.
• An event starting within 48 hours is exempt. The allowance never stops sales for an event that is about to happen.

The count resets on the first of each month. If a paid plan lapsed part-way through a month, the window starts from the moment it lapsed, so tickets you sold while paying are not charged to the Free allowance. When the allowance is spent, online paid checkout pauses for that schedule until the reset: free registration, free ticket tiers and payment at the door all keep working, and the event page falls back to an Add to Calendar button instead of a dead buy button. The event editor shows the running count and the reset date in the Tickets section.

What ticketing includes

Everything below works on the Free plan except where a Pro badge says otherwise.

• Any number of ticket types per event, each with its own price, quantity and description
• Per-type sales start and end times, and an optional cap on how many one order may hold
• Volume discounts on a ticket type
• Promo codes and gift cards Pro - Requires the Pro plan
• Optional add-ons such as parking or merchandise Pro - Requires the Pro plan
• Passes and subscriptions that one buyer reuses across many events Pro - Requires the Pro plan
• Custom checkout fields, collected once per order or once per ticket Pro - Requires the Pro plan
• A QR code on every ticket and phone scanning at the door, on every plan, plus a live check-in dashboard Pro - Requires the Pro plan
• A waitlist that opens automatically when an event date sells out (free for registration, Pro - Requires the Pro plan for tickets)
• An interest list on public event pages, so visitors can ask to hear when tickets go on sale
• Refunds from the Sales page, sent back through Stripe or PayPal in full or in part
• Sale notification emails, a CSV export and a bulk attendee import Pro - Requires the Pro plan
• Post-event feedback requests with star ratings Pro - Requires the Pro plan

External

The default mode. Use it when tickets are sold somewhere else (Eventbrite, Ticketmaster, a box office of your own) or when the event needs no ticketing at all. Event Schedule handles no money in this mode.

Fields

• Registration URL: the external ticketing page. It becomes a View Event button on your event page, opening in a new tab.
• Price: a display-only price with a currency. Leave it blank if you do not know it; enter 0 and the event page reads "Free entry".
• Coupon Code: shown under the price so attendees can use it on the external platform. Event Schedule never validates it.
• Discount: what the coupon is worth, as a percentage or an amount in the event's currency. Shown beside the code, so the event page can read SAVE20 • 15% off rather than sending guests to the external site to find out. Leave it blank if the coupon has no fixed value.

Registration

A lightweight RSVP system for free events. Attendees sign up with their name and email - no payment setup required.

1. Edit your event and scroll to the Tickets section
2. Select the Registration mode
3. Optionally set a Registration Limit to cap how many people can sign up
4. Optionally add Custom Fields to collect extra details (Pro)
5. Save the event

Visitors then see a Register button on your event page. After registering they receive a confirmation email with a QR code for check-in, and the registration appears in your sales list. Add Registration notes (on the Options tab) to put directions, parking, a dress code or anything else into that email and onto their ticket.

Registrants can cancel themselves from the ticket page linked in their email, which frees the spot again.

The Registration Limit is per date. On a recurring event each occurrence keeps its own count, so a limit of 30 means 30 people per date, not 30 across the series.

If you have webhooks configured, registrations fire sale.created and cancellations fire sale.cancelled.

Tickets

Full ticketing for paid or multi-type events. Create ticket types, connect a payment method, and sell directly from your event page.

Setting up ticket sales

1. Connect a payment method first, under Admin Panel → Settings → Payment Methods. Without one, the only choice on the Payment tab is Cash. See Payment.
2. Edit your event and scroll to the Tickets section
3. Select the Tickets mode
4. Fill in the first ticket type (the four fields are described below), then use + Add Type for each further one
5. Open the Payment tab and choose a payment method and currency
6. Save the event

A Buy Tickets button then appears on your event page, or Get Tickets when every type is free. Both labels can be reworded under Customize → Custom Labels on the schedule's edit page.

The Tickets mode has five sub-tabs:

• General: the ticket types themselves, plus passes and per-type sales dates
• Payment: payment method (Cash, Stripe, PayPal, Invoice Ninja, Payfast or Payment Link) and the currency
• Options: checkout toggles, custom fields, ticket notes and a terms link
• Promo Codes: discount codes Pro - Requires the Pro plan
• Add-ons: optional extras buyers can attach to an order Pro - Requires the Pro plan

The Promo Codes and Add-ons tabs still open on the Free plan: they show what the feature does and an upgrade panel in place of the editor.

Ticket Types

A ticket type is a name, a price and a quantity. Add as many as the event needs:

Ticket Settings

Quantity, sales windows, max per order and volume discounts all work on the Free plan. Only the two rows marked Pro are gated.

Individual quantities or one combined pool

When an event has two or more ticket types and they all carry the same quantity, a choice appears under the list:

• Individual Quantities - each ticket type is counted separately, so the capacity is the sum. This is the default.
• Combined Total - all types draw on a single pool of that size. Use it when 100 means 100 people through the door however they split between General and VIP.

The choice is hidden when the quantities differ, when any quantity is blank, or when there is only one seat-selling type. Passes are ignored in that judgement, since a pass does not define seat capacity.

Volume discount

Choose + Add Discount on a ticket type to reward buying in bulk. Set the minimum quantity that unlocks it (two or more), then a percentage or fixed amount off. A group of four booking together gets the discount; a single buyer does not.

Max per order

Choose + Add Limit to cap how many of one ticket type a single buyer can take in one order. This is what keeps a two-for-one early bird from being bought out by the first person through the door, and it is separate from the ticket type's total Quantity: the quantity is how many exist, the limit is how many one order may hold. Add-ons take the same limit.

Passes & subscriptions Pro - Requires the Pro plan

Turn on This is a pass or subscription (multi-use) to make a ticket type one purchase a guest reuses across many events. Four types are offered: a visit pass with a fixed number of visits, an unlimited membership, a festival pass good once per event, and - on a recurring event only - a season pass.

Advance booking is off by default, which makes a pass scan-at-the-door only. Turn on Let holders book seats in advance first, and the per-date seat cap and the cancellation-deadline settings appear with it. Passes also keep one shared inventory bucket rather than a count per date. See Subscriptions & Passes for the full guide.

Buying Several Events at Once

A visitor browsing your schedule can collect tickets to more than one event and pay for the lot in a single checkout. On any event with tickets they choose their quantities and select Add to cart instead of Checkout, then carry on browsing. A cart button appears in the corner with a running count; opening it lists everything gathered so far, and one Checkout pays for all of it.

Afterwards the buyer lands on a page listing every event they bought, each linking to its own ticket. There is no combined ticket: every event is scanned with its own code, because each door only knows about its own event. The confirmation emails arrive one per event for the same reason, and where wallet passes are enabled each live event on that page gets its own Add to Google Wallet button.

The cart panel shows a running total as events are added, and a gift card can be applied to the whole order at checkout. Prices shown in the panel are for orientation: every ticket is re-read and re-priced from your event when the buyer checks out.

Two dates of the same recurring event count as two entries, so a visitor can take Friday and Saturday in one order. Nothing about the cart is trusted at checkout: every ticket is re-read and re-priced from your event, and if any part of the order can no longer be filled the whole thing is refused rather than charging for a partial order.

Free Tickets

If you need multiple ticket types (e.g. General and VIP) or promo codes for a free event, use the Tickets mode and set the price to zero:

1. Select the Tickets mode in the Tickets section
2. Create a ticket type
3. Set the price to $0 (or leave it blank)
4. Set a quantity limit if you have capacity constraints
5. Save the event

Visitors can "purchase" free tickets to RSVP. They'll receive a confirmation email with a QR code, and you'll have a list of who's coming. Add Ticket Notes (under Options) to include directions or other instructions in that email. A holder of a free ticket can cancel it themselves from their ticket page, which releases the spot; paid orders are cancelled by you from the Sales page.

Payment

Before you can take money online you need to connect a payment method. Payment methods belong to your account, not to a single event, so you connect one once and pick it per event. Event Schedule supports six options:

Connecting Stripe

1. Go to Admin Panel → Settings → Payment Methods
2. Click Connect Stripe
3. Complete the Stripe onboarding process
4. Once connected, Stripe appears as a payment option on the event's Payment tab

Stripe verifies a new account asynchronously, so there is a short window after onboarding where the account is linked but not yet ready to charge. The event editor shows a "verifying" notice during that time. If you finish onboarding in another tab, reload the event page to pick up the change.

Connecting PayPal

PayPal is worth connecting where Stripe is not available, or where your buyers would rather pay from a PayPal balance than type a card into a page they have not seen before. Like Stripe, it confirms the payment and issues the ticket with no manual step.

1. Sign in at developer.paypal.com and open Apps & Credentials
2. Stay on the Live tab (the Sandbox tab issues a different pair, for testing), and create an app if you have not already
3. Copy its Client ID and Secret
4. Go to Admin Panel → Settings → Payment Methods and open the PayPal tab
5. Paste both and save. We check them with PayPal before storing them, so a typo is caught here rather than by a buyer
6. PayPal now appears on the Payment tab of any event priced in a currency it settles

PayPal settles a fixed list of currencies, and an event priced in anything else simply will not offer it. Three currencies PayPal does support - the Hungarian forint, the Japanese yen and the New Taiwan dollar - are deliberately left out. PayPal will not accept an amount with decimals in any of them, and a percentage discount here can produce one, so an event priced that way would have money taken and the ticket withheld. Rather than let that happen, PayPal is not offered for those three at all.

Payments that PayPal holds for review are the one case where a ticket is not issued at once. The sale stays unpaid, its seats stay held rather than expiring, and the buyer is told the payment is being reviewed rather than being asked to pay again - on every event of the order, so nobody can accidentally pay twice for the same basket. We also ask PayPal not to accept funding that takes days to settle, such as an eCheck, so this should be a short wait rather than an open-ended one.

Finishing a reviewed payment - issuing the ticket if PayPal clears it, or letting the buyer try again if PayPal declines it - depends on PayPal notifying us, which needs a webhook. We register one for you when you connect your own PayPal account, so there is nothing to do. If your site provides one PayPal account for everyone, that registration does not happen and the administrator has to add a listener themselves; without it a reviewed payment on such a site stays unresolved. Selfhost administrators: see the Payments guide.

When a PayPal checkout is refused

Some orders never reach PayPal, because it would reject them on its own page after the seats were already held. An event priced in a currency PayPal does not settle - or in one of the three left out above - and an order PayPal declines to create. In both cases the buyer is returned to the ticket page with a message and the seats go straight back on sale, so nothing is lost.

If you see that on your own event, check the event's Currency on the Payment tab: an event can keep PayPal selected after its currency is changed, and it then shows in the dropdown marked no longer available until you pick something else. The same happens if you unlink PayPal while an event still names it - there the buyer is simply returned to the ticket page, so an event left that way is worth catching before a real buyer finds it.

Two more outcomes are worth recognising. A buyer who approves the payment, closes the tab and comes back much later may find the reservation has already expired - nothing is charged in that case. And if PayPal reports a total that does not match the order, the sale is held as an amount mismatch for you to look at rather than being completed: the money is with PayPal and the ticket is not issued, so it needs a person.

Refunds

PayPal is one of only two methods - Stripe is the other - where Refund Ticket on the Sales page sends the money back for you. You can return the whole amount or part of it, and the sale's PayPal reference is shown there as a link into your PayPal activity. Refund from the Sales page rather than from PayPal itself: a refund made in your PayPal account is not reported back, so the sale stays paid and its ticket keeps scanning. See Refunds for partial refunds and for what happens when a refund cannot be confirmed.

What PayPal does not do

PayPal cannot offer monthly installments, which need a card the gateway can charge again later, and gift cards cannot be sold through it. It is also not offered on events priced in Hungarian forints, Japanese yen or New Taiwan dollars, or on appointment bookings. Everything else works normally - promo codes, add-ons, volume discounts, per-attendee tickets - and unlike Payfast a PayPal event can be combined with others in the multi-event cart, because the whole basket is taken as one payment.

Connecting Payfast

Payfast is a South African gateway, useful where Stripe is not available. It settles in rand (ZAR) only, so Payfast appears as an option only on events priced in ZAR - and if an event is later switched to another currency, or its method is set through the API, checkout refuses rather than charging the wrong currency. See When a Payfast checkout is refused.

1. In Payfast, open Settings and note your Merchant ID and Merchant Key
2. Set a passphrase in the same Payfast screen if you have not already
3. Go to Admin Panel → Settings → Payment Methods and open the Payfast tab
4. Enter all three values and save
5. Payfast now appears on the Payment tab of any event priced in ZAR

The passphrase is required rather than optional. It is what lets us verify that a payment notification genuinely came from Payfast, so without one there is no way to tell a real payment from a forged one. Setting it on your Payfast account also makes Payfast reject unsigned checkout requests, which protects your merchant account beyond this integration.

By default Payfast shows buyers every method your account supports. To send them straight to one instead, tick exactly one entry under Payment methods. Ticking several, or none, leaves the choice to Payfast.

Invoice Ninja Modes

When using Invoice Ninja, choose between two checkout modes in your payment settings.

Options

Configure additional checkout settings for your event's tickets.

Custom Checkout Fields Pro - Requires the Pro plan

Collect additional information from attendees during checkout. You can add up to 10 custom fields per event. Each field has a name, a type (single line, paragraph, switch, date, dropdown or multi-select) and a required flag, and fields can be dragged into the order you want them asked.

1. Edit your event
2. Go to the Tickets → Options tab
3. Add field labels (e.g., "Dietary Requirements", "T-Shirt Size")
4. Mark fields as required or optional
5. Save the event

Responses are stored with each sale, shown when you expand the sale on the Sales page, and included in the CSV export as one column per field.

Additional Settings

Installment Payments Pro - Requires the Pro plan

Let buyers spread the cost of an expensive ticket over monthly payments. Useful for courses, retreats and multi-day events announced well in advance: a buyer pays the first installment at checkout and gets their ticket straight away, and the rest is charged automatically to the same card each month.

Setting it up

Open your event, go to Tickets then the Payment tab, and turn on Let buyers pay in monthly installments. The option appears only when the event is paid through Stripe, because Stripe is the only payment method that can charge a saved card automatically.

Every individual payment has to clear Stripe's minimum charge of roughly $0.50, so splitting a small order too many ways withdraws the option. A promo code or gift card applied at checkout can take an order under that line, or under your own minimum, and the buyer will simply not be offered monthly payments. Installments are also not offered for a basket spanning several events, or for one containing a pass.

What the buyer sees

At checkout the buyer chooses between paying in full and paying monthly. Paying in full is selected by default. If they choose monthly they see every payment date and amount before committing, confirm that they authorise the future charges, and are charged only the first payment. There is no interest and no fee: the total is the same either way.

Their ticket is valid from the first payment. Two days before each following payment we email them a reminder naming the card and the amount. Every one of those emails links to their own payment plan page, where they can pay early, clear the whole balance or change their card. That page is the only place their saved card is shown: the ticket page is what the QR code opens, and door staff scan it.

Tracking payments

The Installments tab on your Sales page lists everyone paying monthly, how far through they are, what has been collected, what is outstanding, and what to expect month by month. Overdue plans sort to the top.

You get one daily summary of the payments due in the next couple of days, rather than an email per buyer, and an immediate email whenever a payment fails.

When a payment fails

If a card is declined we retry it three more times over the following nine days, emailing the buyer each time and telling them plainly that their ticket is still valid. If their bank asks them to confirm the payment (common in Europe) we send a different email asking them to approve it, and do not count it as a decline.

If the balance is still unpaid after that, the ticket goes on hold: it stops scanning at the door until they pay, and paying makes it valid again immediately. A week before the event everyone with an outstanding balance gets a final notice, and you get a list of them, so nobody is surprised at the door.

Running out of retries is the common route to a hold, but not the only one. A plan also goes on hold if a bank authentication request goes unanswered for a week, or if your own Stripe connection is disconnected so nothing can be collected at all. That second one is worth knowing: the buyer has done nothing wrong and cannot fix it, so you are the one we email, and reconnecting Stripe is what restarts collection. For the ordinary routes, the buyer replacing or re-confirming their card lifts the hold and puts the remaining payments back on schedule.

One state deliberately waits for a person: if a charge is interrupted and we cannot tell whether the money moved, we stop rather than retry, because retrying a payment that may already have succeeded is how a buyer gets charged twice. The same applies to a payment that arrives but does not match anything we can apply it to. Both show on the Installments tab as needing your attention, with the Stripe reference to check against your dashboard, and neither is resolved by the buyer changing their card.

Scanning a ticket that is on hold shows your door staff an amber Overdue balance screen with the attendee's name, the amount outstanding and how much of the total has been paid, rather than a red rejection. The scan does not check them in, so taking payment or letting the guest in is your call.

Cancelling or refunding an order, cancelling the event, or deleting the schedule all stop the remaining payments immediately. A payment plan can only be refunded in full: Refund Ticket returns each payment that was already collected, one at a time, and the Installments tab still lists every payment reference so you can check them against your own Stripe dashboard.

Promo Codes Pro - Requires the Pro plan

Offer discounts to attendees with promo codes. Buyers enter a code during checkout to receive a discount on their purchase.

Adding a Promo Code

1. Edit your event
2. Go to the Tickets → Promo Codes tab
3. Click + Add Promo Code
4. Enter the code (e.g., "EARLYBIRD", "VIP50")
5. Choose the discount type and value
6. Save the event

Discount Types

• Percentage: A percentage off the ticket price (e.g., 20% off)
• Fixed amount: A flat amount off the ticket price (e.g., $10 off)

Promo Code Settings

• Max Uses: Limit how many times the code can be used (leave blank for unlimited). The number of times it has been used is shown beside the code.
• Expires At: A date and time when the code stops working
• Active: A toggle that switches the code off without deleting it
• Applies To: All Tickets, or Specific Tickets to tick the types it covers

Each promo code has a copy-link button that produces a shareable URL pre-filling the code at checkout, making it easy to distribute to your audience.

A promo code never discounts add-ons, and it is worked out after any volume discount on the same line, so the two never double-count the same money. A percentage code is capped at 100% and a fixed code can never discount more than the eligible subtotal.

Add-ons Pro - Requires the Pro plan

Add-ons are optional purchasable items that customers can include with their ticket order, such as parking passes, merchandise, or meal packages.

Creating an Add-on

1. Edit your event
2. Go to the Tickets → Add-ons tab
3. Click + Add add-on
4. Fill in the add-on details and save the event

Add-on Fields

• Name (required): The name displayed to customers (e.g., "Parking Pass", "Event T-Shirt")
• Price: The price per unit (leave blank or set to 0 for free add-ons)
• Quantity: The total number available (leave blank for unlimited)
• Description: An optional description with additional details
• URL: An optional link, for a size chart or a product page
• Image: An optional picture of the item
• + Add Limit: Caps how many of this add-on one order may hold, the same as Max Per Order on a ticket type

How Add-ons Work

• Add-ons appear in the checkout form only after the customer selects at least one ticket
• Customers choose a quantity for each add-on (or leave it at 0 to skip)
• Add-on totals are added to the ticket total at checkout
• Promo codes and volume discounts do not apply to add-ons
• Add-ons are tracked separately in sales records, the CSV export and confirmation emails
• Add-ons never count toward the Free plan's paid-ticket allowance

Allocated Seating Enterprise - Requires the Enterprise plan

Everything above sells by the number. If your venue has rows, you can sell the seats themselves instead: draw the room once as a seating plan, attach it to an event, and buyers pick where they sit. Your box office gets the same map to hold seats back, take a booking over the phone, move somebody or release a single seat.

It has a guide of its own: Allocated Seating.

Managing Sales

Track and manage your ticket sales from Admin Panel → Sales. The page spans every schedule you own or administer, and carries tabs for Sales, Waitlist, Feedback, Subscriptions, Installments and Gift Cards.

What You Can See

• Every purchase with the buyer's name, email and phone
• The event and the occurrence date the sale is for
• Payment status: paid, unpaid, cancelled or refunded, plus Refunded so far once any money has gone back
• The amount, any discount or gift card applied, and the transaction reference
• Check-in status, and the star rating if the buyer left feedback

Expand a row to see the individual tickets in the order, the add-ons, and any custom field answers. Columns can be sorted by clicking their headers.

Filtering Sales

Use the filter input at the top of the sales list to search by buyer name, email, phone, event name, status or transaction reference. The filter updates results in real time. When exporting sales data, only the currently filtered results are included in the export.

Past events are hidden by default. Turn on Include past events to bring older sales back into the list, and into the export.

Actions

Open the Actions menu on a sale row:

• View Ticket: Open the attendee's ticket page, with its QR code
• Send Email: Send the confirmation email again
• Mark Paid: For cash or other payments taken outside the app
• Refund Ticket: Send money back on a Stripe or PayPal sale, all of it or part. See Refunds
• Mark as Refunded: Shown instead of Refund Ticket on every other payment method. It records a refund you make yourself, and moves no money
• Cancel Ticket: Cancel a paid or unpaid sale without recording a refund
• Delete: Remove a sale from the list. A live sale is cancelled first, so its tickets go back on sale

A full refund, a cancellation or a deletion returns the sale's tickets and any allocated seats to stock, gives back any promo code use, credits any gift card balance the buyer spent, stops any remaining installment payments, and notifies the next person on the waitlist. A partial refund does none of that: the sale stays paid and every ticket on it stays valid.

Refunds

Refunds work on every plan, and what the action does depends on how the sale was paid:

• Stripe and PayPal: Refund Ticket sends the money back through the provider, and the status here changes only once it has gone. A dialog shows Available to refund and asks for a Refund Amount, so you can return all of it or part.
• Every other method - Invoice Ninja, Payfast, a payment link, cash, or any sale you marked paid by hand - shows Mark as Refunded instead. It records the refund and adjusts your revenue figures, and you return the money in your provider's own dashboard.

A partial refund leaves the sale paid and its tickets valid, and the row shows Refunded so far. Refund the rest later and the sale becomes refunded, with its tickets and seats back on sale. Until then your Analytics revenue still counts the sale in full.

A payment plan on installments can only be refunded in full: Refund Ticket returns each payment already collected, one at a time, and stops the rest.

Sale Notification Emails Pro - Requires the Pro plan

Opt in to receive an email notification every time a ticket sells. Each notification includes:

• Buyer name and email
• Ticket type and quantity
• Total amount
• Payment status
• Discount or promo code applied

How to Enable

Open the schedule's edit page in the admin panel, go to Settings → Notifications and turn on New ticket sale. Every editor of the schedule can opt in separately. If push notifications are enabled, the same alert is mirrored to the browser.

Exporting Sales Data Pro - Requires the Pro plan

Export your sales data for accounting, tax purposes, or to import into other systems. The export covers every schedule you own or administer.

1. Go to Admin Panel → Sales
2. Narrow the list with the filter box, and turn on Include past events if you need older sales. The export contains exactly what the list is showing.
3. Click Export
4. Download your sales data as a CSV file

Importing Attendees Pro - Requires the Pro plan

Bulk-add attendees who paid out-of-band (cash, sponsored, or through a third-party system) instead of checking them out through the public ticket page. Up to 5,000 attendees per import.

1. Go to Admin Panel → Sales and click Import
2. Pick a schedule (if you own more than one), an event, and the Event Date the attendees are coming on
3. Either type rows on the Form Entry tab or switch to Upload CSV
4. When uploading, map each CSV column to a field (name, email, phone, ticket type, etc.), then click Next to review
5. Optionally toggle Send Email to send a confirmation email to each attendee
6. Click Save Attendees

Check-in at the Door

Use your phone to scan tickets at the door. No special hardware needed.

1. Go to Admin Panel → Sales on your phone
2. Click Scan Ticket
3. Point your camera at the QR code on the ticket
4. The app shows the ticket details and marks it as checked in

Ticket Security

Each ticket has a unique QR code that can only be scanned once. If someone tries to use a ticket that's already been checked in, you'll see a warning. An unpaid or cancelled order shows its QR code struck through, marked Unpaid or Void.

Check-in Dashboard Pro - Requires the Pro plan

Monitor attendance in real time from Admin Panel → Sales → Check-in. The dashboard provides a live overview of check-in progress for your event.

• Overall progress bar with percentage of attendees checked in
• Per-ticket-type breakdown showing check-in counts for each ticket type
• Guest headcount - when a pass admits guests, a headcount including guests is shown next to the check-in count
• Reserved pass seats for the occurrence, so door staff know how many pass holders are still expected
• Recent activity feed showing the last 10 check-ins with attendee names and times, and their seat on an allocated event
• Filter by event and event date to view specific event dates

Counts are keyed to the venue's own calendar date, so an evening event west of UTC reports correctly rather than rolling over at the wrong midnight. Only redemptions count as checked in: a pass holder who booked a seat in advance appears in the reserved count until they actually arrive.

Wallet Passes

Ticket buyers can save their ticket into Google Wallet from the ticket page, from the order page of a multi-event purchase, or from the confirmation email. The pass carries the same QR code the ticket page shows, so it scans at the door exactly like any other ticket, and it works offline once saved.

• Event details on the pass - name, venue, date and time, attendee name, ticket type and seat
• Arrival reminder - when the venue has map coordinates, Google can notify the attendee as they arrive nearby
• One pass per event - a multi-event order gets a separate pass for each event, since each is scanned with its own code. A single order for several people is one pass showing the number it admits, unless the event issues individual tickets
• Passes and registrations too - a pass or subscription of any type saves as one undated pass rather than one per date, and shows how many people it admits at each event when that is more than one. If the pass has an expiry, Google Wallet archives it once that date passes. Free registrations get a wallet pass on the same terms as a paid ticket
• Not for every order - there is no wallet button for an appointment booking, on an event you have cancelled, or while an installment plan is behind on its payments

At the door a wallet pass is scanned exactly like any other ticket: the attendee opens it and you scan it from Scan Ticket as usual. On an allocated event the seat is printed on the pass.

The pass is a snapshot taken when the attendee saves it. Cancelling or fully refunding an order does not remove a pass already on someone's phone, but the code stops working: the door scanner checks the order's live status, and a cancelled or refunded ticket is refused there just as it is on the ticket page. A partial refund leaves the order paid, so its pass keeps working.

Waitlist

When an event date fills up, fans can join a waitlist to be notified when spots become available.

How It Works

1. When all tickets sell out for an event date, a Join Waitlist button appears on the event page
2. Guests enter their name and email
3. When a spot opens up - a sale is cancelled, fully refunded or expires unpaid, a pass holder cancels a booked date, or your box office releases a seat - the next person in line is notified by email. A partial refund frees no spot
4. They receive a link that is valid for 24 hours
5. If they don't purchase in time, the next person in line is notified

Managing the Waitlist

View and manage the waitlist on the Waitlist tab of Admin Panel → Sales. The tab appears once there is at least one entry, and the table shows each entry's name, email, event, date, and status.

Interest List

Most people who look at an event page are not ready to buy that minute. The interest list lets them leave an email address and hear from you when it matters, with no account and no sign-up.

How It Works

1. On a public event page, a visitor opens the Add to Calendar menu and chooses Tell me when tickets go on sale, or Tell me if anything changes once tickets are on sale. An event that is already selling tickets or taking registrations also shows a Not buying today? Tell me if anything changes link beside the buy button
2. They type an email address and press Notify me. No name, no account and no confirmation email to click
3. Three emails go out automatically: one when that date's tickets go on sale, a reminder about 48 hours before it starts, and a cancellation notice if you cancel the event. Someone who asks once tickets are already on sale skips the first one
4. A change reaches them only if you send it. When you save a new date or time on a one-off event, or a new venue or online link on any event, the editor asks Notify attendees of this change?, and the list is emailed only if you choose Notify attendees
5. Every message carries a one-click unsubscribe, and unsubscribing deletes the address rather than keeping it on a suppression list

Each date of a recurring event keeps its own list, so someone who asks about one Friday hears about that Friday's tickets and that Friday's reminder. Nothing else is sent: the list never receives your newsletters or news of your other events.

Seeing Who Is Waiting

The Tickets panel in the event editor says how many people asked, for example "12 people asked to be told when tickets go on sale", counting each address once across every date. While a schedule has upcoming events and no ticket type, the dashboard suggestion reads "12 people are waiting to buy - add a ticket type". You see how many, not who, and neither number is shown publicly.

Post-Event Feedback Pro - Requires the Pro plan

Automatically collect ratings and comments from attendees after your events end. Feedback emails are sent to ticket buyers and RSVP attendees, linking to a simple form where they can rate their experience.

Enabling Feedback

1. Go to your schedule's edit page in the admin panel
2. Open Engagement → Feedback
3. Turn on Post-event feedback
4. Choose a delay (how long after the event ends before emails are sent). The default is 24 hours.
5. Save your changes

How It Works

1. After an event ends and the configured delay passes, feedback request emails are automatically sent to attendees
2. Each email contains a link to a feedback form branded with your schedule's logo and colors
3. Attendees rate their experience from 1 to 5 stars and can leave an optional comment
4. Each attendee can only submit feedback once

Viewing Feedback

View all feedback from Admin Panel → Sales → Feedback tab. The page shows:

• Summary card with average rating, total responses, and response rate
• Feedback table listing each response with attendee name, event, date, star rating, comment, and submission time

The tab also shows a Sent - Awaiting Response list of attendees who were emailed but have not replied yet. If a request was missed or landed in spam, click Resend next to an attendee to send the feedback request again.

Exporting Feedback

Click Export Feedback on the Feedback tab to download a CSV file with all feedback data.

Feedback Notifications

To receive an email when new feedback is submitted, enable New feedback in Settings → Notifications. Each notification includes the event name, attendee name, star rating, and comment.

Financial Information

Important information about payments, refunds, and taxes.

Embed Widget

Embed a ticket purchase or RSVP form directly on your own website using an iframe. Visitors can buy tickets or register without leaving your site.

Getting the Embed Code

1. Open your event in the admin panel and go to the Tickets section
2. Enable Tickets or Registration mode and save the event
3. Click the Embed Tickets (or Embed Registration) link next to the section heading
4. Copy the iframe code and paste it into your website's HTML

The link that opens the snippet only appears for Pro schedules. On the Free plan you can still embed the RSVP form by building the URL yourself from the parameters below.

URL Parameters

You can customize the embed URL with these parameters:

See Also

• Creating Events - Add events to sell tickets for
• Gift Cards - Sell prepaid gift cards redeemable at checkout
• Subscriptions & Passes - Sell one pass reused across many events
• Appointments - Take bookings for a time slot, with their own allowance
• Sharing Your Schedule - Promote your events
• Event Graphics - Create promotional images
• Analytics - Track conversion rates and revenue per view
• Account Settings - Set up your payment method
• Newsletters - Send newsletters to promote ticket sales
• Embed Tickets - Embed a ticket form on your website