Skip to main content

Events

An event brings together a scheduled experience, its ticket offer and the people attending. Start with the date and venue, choose assigned seats or a general capacity, and prepare payment and admission before inviting guests.

This guide uses Garden Jazz at Harbourside, a fictional Sunday evening with CAD $35 General admission and a CAD $55 Front-row table ticket. The example was saved privately with sales switched off. Its populated settings and room plan demonstrate configuration; no ticket was issued, paid, emailed or scanned during this review.

Saved jazz event with poster, evening times, description and an illustrative public venue
Review the saved event information before sharing it. This rehearsal uses an illustrative venue and is not a real advertised event.
Saved jazz event with poster, evening times, description and an illustrative public venue

Review the saved event information before sharing it. This rehearsal uses an illustrative venue and is not a real advertised event.

Create and review an event​

  1. Open Events → Create Event. Check the active business first.
  2. Add the poster, name, description, tags and color. If poster autofill fails, enter and check the details manually; a loaded image does not guarantee successful extraction.
  3. Select the date, start and end times, and the intended location.
  4. Choose Layout-Based Tickets, Amount-Based Tickets or Information. The last option provides an event page without ticket inventory.
  5. Continue to settings. Review visibility, ticket types, currency, payment methods and any registration form.
  6. Review publication deliberately. Everyone, Linked and Private serve different audiences; publication and allowing sales are separate controls.
  7. Reopen the dashboard after saving. Confirm the actual visibility, sales switch, prices and event times rather than relying on the creation preview.

Private is useful for an authorized rehearsal. It does not by itself switch Allow Sales off. Our saved example uses both Private and sales off. Do not add it to a display or social post as part of a private test.

Ticket Sales​

Choose the sale mode around the promise you are making. Layout-based sales promise a particular seat; amount-based sales promise admission within a quantity limit. An information event should not suggest that a guest has bought admission.

In Settings, review each ticket type's name, description, price and capacity. A front-row type can be restricted to particular tables. Confirm the Tables For Sale selection as well as the total room capacity: a visible table does not necessarily belong to the sale offer.

Saved private ticket settings showing General and Front-row prices, capacities and sales disabled
The CAD $35/$55 types were saved and reloaded. This is a configuration example, not evidence of completed ticket sales.
Saved private ticket settings showing General and Front-row prices, capacities and sales disabled

The CAD $35/$55 types were saved and reloaded. This is a configuration example, not evidence of completed ticket sales.

Review Abstract Fees and the checkout estimate, then check the real payment setup. Card acceptance requires Stripe readiness. A displayed estimate is not proof of the amount a cash sale will settle for.

The dashboard's Sell Tickets action opens Terminal → Events with this event selected. The reviewed Terminal loaded the saved room and allowed a seat selection. Completing checkout, inventory locking, ticket issuance and payment were not verified. The dashboard's separate manual ticket-creation dialogs currently cannot save tickets; use the supported Terminal route rather than treating those dialogs as an alternative issuance path.

Seat Selection​

For assigned seating, prepare a saved layout before configuring the event. Check table labels, individual seats, fixtures and the tables available for sale.

In Terminal, open the event and tap an available seat. Review the selection chip before advancing. Clear removes the current selection. Selecting a seat is not a completed sale; proceeding to guest details can create a temporary reservation, and a reservation is not a paid ticket.

Event room plan with one selected seat and the Select Seats step before Guest Info
A real seat-selection draft, cleared before Next. The primary image is cropped to the event panel; guest details and payment were not submitted.
Event room plan with one selected seat and the Select Seats step before Guest Info

A real seat-selection draft, cleared before Next. The primary image is cropped to the event panel; guest details and payment were not submitted.

Two current inconsistencies need checking before live use: the reviewed Terminal event card showed midnight while Event Info held the correct 5 PM start, and its selection chip could show a different table number from the seat's accessible label. Verify the intended seat against the floor plan and saved event; do not rely on an inconsistent summary to issue tickets. These issues do not change the saved rehearsal prices or prove the consumer checkout has the same behavior.

Guest Coordination​

Use Guest List to work from issued tickets rather than a separate handwritten list. Its views separate tickets, orders, the room layout and per-table summaries. Filters can help distinguish payment and admission states; attendee information requires the appropriate event permission.

Before doors open, agree who handles unpaid arrivals and who admits paid guests. A layout seat marked booked without attendee information is not a substitute for a properly issued guest ticket. Keep any registration questions short and connected to the actual attendee form.

The reviewed rehearsal has no issued tickets. Guest filtering controls and their implementation were inspected, but populated guest records and attendee edits were not exercised or photographed. No invitations or guest messages were sent.

Guest Insights​

Interpret event reports alongside the underlying tickets. Ticket counts, paid state, checked-in state and per-table occupancy answer different questions. Use the dashboard's table summary for seating, and Analytics for the event reporting console.

Age information, where available, depends on supplied attendee details; missing ages should not be treated as a complete audience profile. A quiet event with zero tickets cannot demonstrate conversion, revenue or attendance performance. The rehearsal review did not create guests to populate analytics, so no audience statistics are presented as measured results.

Ticket Scanning​

Open the event and choose Check In Guest to use its scanner. The scanner belongs to the selected event: a valid ticket for another event should not be admitted here. Camera access and a compatible device are prerequisites.

The admission implementation checks that the ticket exists, belongs to this event, is paid and has not already been used. A successful admission records check-in and its time. Treat invalid, wrong-event, unpaid and already-used outcomes separately; repeatedly scanning should not create another admission.

Camera scanning, printed-code readability and a successful real-ticket admission were not tested in this review. Test the actual entrance device with an authorized test ticket before relying on it at the door. Never publish a guest's ticket QR in a help request or documentation image.

Event Check-in​

Payment and attendance are separate states. Check In Guest is for admission; Accept Payments is a different route even though it can also use a camera. Collecting money does not by itself prove that a person entered the venue.

Use the dashboard's checked-in count to reconcile arrivals against issued tickets, and give door staff the required access before the event. If admission fails, check the selected event, payment state and prior check-in before changing a record. Any manual correction should reflect the actual guest's arrival, not an attempt to make the counter match an expectation.

The admission rules are source-confirmed; neither scanner admission nor manual guest check-in was completed in the rehearsal.

Event Flows​

The flow library includes Ticketed Event and Free RSVP starting points. They help describe an event page, attendee information and the intended checkout or completion path. Use the Flow Builder to inspect and adapt a draft, replacing sample ticket tiers and questions with the actual offer.

A flow diagram does not automatically activate event checkout. The current event dashboard's Connections panel says that event connections are coming soon, and a generic event-to-flow association is not sufficient to establish the consumer checkout configuration. Do not publish a flow and assume the event is now selling through it.

For current event operations, configure the event's own ticket, registration and payment settings. A flow-based event checkout needs an explicitly supported setup and an end-to-end test of seat or quantity selection, answers, payment and ticket issuance. That complete integration was not verified here.

QR Sharing​

An event-page QR helps someone open the event. A ticket QR identifies a particular admission. Use the former for promotion and keep the latter private.

The event publication workflow can offer adding a poster and event link to selected displays, with a QR for that page. Review the destination and audience before selecting a display. Linking to an event does not override its visibility or sales settings.

No display publication, public QR distribution or guest-code capture was performed in this private rehearsal. A standalone downloadable event-QR control was not verified; do not expect a ticket QR to serve that purpose. See Displays for the display workflow.

In-App Tickets​

The consumer ticket page provides the admission code and ticket details. Available actions include editing attendee details and transferring a ticket, subject to ownership and ticket state. Have the guest open the intended event's ticket before approaching the scanner.

A ticket on screen is different from a basket, a reservation or an unpaid order. Verify its event and payment state if there is an admission problem. Transfer and claim actions should be performed only for the intended recipient.

The customer ticket implementation was inspected, but no consumer ticket was issued or claimed in this rehearsal. Screenshots deliberately omit admission codes and transfer material.

Email Tickets​

The ticket delivery implementation can send purchase emails with ticket attachments, and the consumer transfer workflow has its own email path. Use a correct recipient address and distinguish an original purchase message from a transfer invitation.

If a guest cannot find a message, check the intended address and ticket record before attempting another delivery. Do not infer successful email delivery merely because a ticket exists or a send action was requested. No purchase email, transfer message or inbox delivery was tested here.

PDF Tickets​

Purchase-ticket delivery includes generated PDF attachments containing event and attendee details and an admission QR. A PDF is a delivery format for an issued ticket, not an editable artwork template or proof that payment completed.

Keep the original file readable and protect its admission code. If printing, test the code using the actual entrance device and paper size. PDF generation and email attachment handling are source-confirmed; no ticket PDF was generated, printed or scanned in this rehearsal.

Ticket Designer​

A customizable ticket designer was not found in the reviewed implementation. The existing generated PDF format should not be presented as a drag-and-drop ticket editor.

You can prepare the event's poster and description, then check how issued ticket details appear through the available delivery channel. If your event needs a custom ticket layout, confirm that capability separately before promising editable fields, typography or export templates.

Wallet Tickets​

An Apple Wallet or Google Wallet pass export was not found in the reviewed event or ticket implementation. An in-app ticket and an emailed PDF do not establish wallet-pass support.

Plan admission around the verified ticket channels and test them with your entrance device. Confirm a working wallet integration before telling attendees to add a pass to their wallet.

Announcements​

The event settings offer Promotion Text, which supplies text for the event presentation. It is not a verified guest-notification broadcast tool.

Use the event description for arrival information that guests need to read, and verify that it saved. A separate announcement composer, recipient selector and delivery confirmation were not found in the reviewed event workspace. Do not assume changing promotion text sends email, push notifications or messages to ticket holders.

Event Photos​

The verified event image workflow is the poster: select or upload an image, then review the saved event information. This is useful for identifying the event and presenting its offer.

A guest photo album, attendee upload flow or event-specific photo-sharing permission screen was not found in the reviewed event workspace. General business assets are a separate tool. Do not advertise a poster upload as a populated guest gallery.

Song Requests​

The consumer ticket page currently displays a song-request card, but it does not provide a working request form or submission action in the reviewed implementation. No DJ queue or moderation workflow was found.

Do not ask guests to rely on that card for requests. Confirm a working request and reception path before advertising it as part of the event experience.

Event Tokens​

A ticket data field alone does not establish an event-credit system. A working operator workflow for issuing, pricing or replenishing event tokens was not found in the reviewed implementation.

If drinks or activities need prepaid credits, establish a supported payment and redemption process before selling them. Do not represent a ticket's displayed or stored token value as proof of a redeemable balance.

Token Terminal​

A token issuance or redemption terminal was not found in the reviewed app. Ordinary Terminal item sales are a different workflow; they should not be described as deducting an event-token balance.

Before planning cashless token redemption, confirm the balance rules, refund handling and actual operator screen with the intended payment setup. None was verified in this rehearsal.

Token Analytics​

No event-token ledger or token-specific analytics screen was found in the reviewed implementation. Ticket sales, check-in counts and normal payment analytics cannot establish token issuance, spending or outstanding balances.

Use reports that correspond to real recorded transactions. Do not promise token reconciliation or unused-credit reporting until a complete token workflow and its data are available.

Troubleshooting before opening sales​

SymptomWhat to review
Poster loads but autofill failsEnter the event details manually and verify the saved result. Autofill failed in this rehearsal.
Seats are missingCheck sale mode, chosen layout, floors, tables for sale and existing reservations.
Price differs from the expected offerReview ticket-type price, capacity, table restrictions, currency and fees.
Card payments are unavailableComplete the provider setup; a settings switch alone is not readiness.
Guest information is inaccessibleCheck event permissions, not only the general workspace role.
Event connection is unavailableThe dashboard panel is currently a placeholder; do not assume a flow is active.
Saved time or table summary differsVerify Event Info and the room plan; resolve the inconsistency before issuing tickets.

Continue with Prepare a private event rehearsal and Layouts.

Video tutorial​

How to Create Events and Sell Tickets in SRVZrYouTube ↗

Seat and table actions on the layout map​

In the event dashboard, open Guest List → Layout and click a seat or a table. A dialog opens with a zoomed-in view of what you clicked and everything you can do with it:

ClickedActions
Open seatCreate ticket (opens the guest details form), Mark as sold (no guest details, with Undo), Sell all open seats at this table, plus the Table on sale and Seat on sale switches
Sold seat with a ticketOpens the ticket directly
Seat marked sold without detailsOpen the seat again
TableSell open seats and the Table on sale switch

Right-click (or long-press) shows the same actions as a smaller popover next to the pointer. Shift-click still selects several seats at once for a batch.

Take individual seats off sale​

For an assigned-seat event, use the Seat on sale switch in the seat dialog to exclude a specific seat without removing its entire table. If the table itself is off sale, turning a seat on puts the table on sale with its other open seats held back, so buyers can book only that seat. Review the saved map and the consumer-facing legend before sales begin.

A blocked seat is unavailable for purchase even if nearby seats remain available. Taking a seat off sale is different from issuing, reserving or refunding a ticket. If the intended seat already has a booking, inspect that booking separately before changing the layout. The per-seat behaviour is source-confirmed; no seat inventory or live ticket sale was changed in this refresh.