Guest Passes

A Guest Pass belongs to a customer and covers a guest's registration. The owner and guest each have a customer profile within the issuing organisation. It is not an Access Pass for the owner to use themselves, and it cannot be spent in another organisation.

There are two ways to use one. A customer can invite a guest before a visit through a Guest Pre-Registration flow, or staff can add a guest when registering the customer at the front desk.

Guest Passes apply to customer registration, not booking check-in. Booking guest invitations are a separate feature and do not spend Guest Passes.

Set the guest allowance

Open Settings > Registration > Guest Registration. This section is labelled Beta.

Under Default guest allowance, choose:

• No guest limits: customers do not need an owned Guest Pass balance to invite or register guests. Invitations and guest registrations are still recorded, but no owned-pass balance is deducted.
• Set guest limits with Guest Passes: each guest needs an available Guest Pass use from the inviting customer. A pass reserved for an invitation is not available to invite somebody else.

Then choose which sublocations allow guest registrations. A sublocation that does not allow guests remains unavailable in either allowance mode. "No guest limits" does not override that setting.

Why the allowance setting can be locked

Once you have created a Guest Pre-Registration flow, you must delete all Guest Pre-Registration flows before changing the default allowance mode.

To switch from Set guest limits with Guest Passes back to No guest limits, you must also archive all active Guest Pass types in Settings > Passes. Clearing a customer's balance is not the same as archiving the type.

Save the allowance change before creating new flows. If you archive a Guest Pass type that a flow uses, delete that flow or reconfigure it to use another eligible type.

Create and issue Guest Passes

When guest limits are enabled:

1. Open Settings > Passes and choose Create Pass.
2. Select Guest Pass, enter a name, and add an optional description.
3. Set Expiry after issue in days, or leave it blank for no expiry, then save.
4. Open the customer's profile and choose Issue Passes in the Passes section.
5. Select the Guest Pass type, set the number of uses and the start date, then confirm. The form shows any expiry calculated from that start date.

Membership plans can also include Guest Pass benefits. The pass type defines the benefit; the issued balance belongs to the customer.

Guest Pass types do not have a sublocation picker. For an invitation, the customer chooses a location from the Guest Flow. Staff later register the guest at a guest-allowing sublocation within that location.

Create a Guest Pre-Registration flow

In Settings > Registration, find Guest Pre-Registration and choose Add Guest Flow.

Give the flow a name, choose its theme, and write the invitation text. In limited mode, select the Guest Pass type the flow should use. In unlimited mode, set Maximum guests per submission to control the size of each submission without requiring a pass balance.

Under Associated locations, select the locations customers can invite guests to. You select whole locations here, not individual sublocations. A location cannot be selected if none of its sublocations allows guests.

Save the flow. It can be used as a standalone form, embedded on a website, or made available in the Customer Portal's Guest registration area. Standalone forms are for inviting guests; the portal also shows the customer's live sent and received passes.

Locations and invitation variables

If the flow has more than one eligible location, the customer chooses a Location when inviting a guest. If only one is available, Tiquo uses it automatically and does not show a dropdown.

Use Add Variable in the invitation editor to insert a variable at the cursor. Variables appear as pills in the editor:

• {{venue}} becomes the selected location's name, not a list of sublocations.
• {{guestFirstName}} becomes the guest's first name.
• {{inviteLink}} becomes the guest's secure invitation link.

Keep the invitation link in the message so the guest has somewhere to accept the invitation. For example:

Hi {{guestFirstName}}, I'd like to invite you to join me at {{venue}}.
Please use this link to register before you arrive:
{{inviteLink}}

Invite a guest before their visit

The customer opens the Guest Flow, selects the visit date and location, enters the guest's details, and shares the invitation link.

In limited mode, sending the invitation reserves one use from the required Guest Pass type. It does not consume the use yet. The owner cannot spend that reserved use on a second guest.

The guest opens the link and completes acceptance. The pass then appears as Accepted on the guest's profile and remains Assigned on the sender's profile. Acceptance still does not deduct a use.

A customer cannot invite themselves or accept their own guest invitation. An accepted link cannot be claimed by someone else or reused for another invitation. Once it has been claimed, the sender's share button becomes a disabled Invitation claimed button.

Accepting the invitation also links the inviter and guest in the social graph. Invitation and registration events appear in both customers' activity histories.

Consume the pass when the guest arrives

Staff register the guest at a sublocation that allows guests within the invitation's selected location. Registration consumes the reserved Guest Pass use. It does not also spend an Access Pass belonging to the guest.

The pass is then shown as Consumed in both the sender's and recipient's profile history. A consumed use is no longer available to the owner.

Staff can register accepted guests from the host's registration modal or through See Upcoming Guests. See Customer Registration for both workflows.

What happens if the guest never arrives?

The invitation's visit date determines how long the reservation is held. Tiquo uses the selected location's timezone.

For a visit on 1 September, an unaccepted invitation expires at the end of 1 September. If the guest accepted it but did not register, it expires at the end of 2 September.

When the reservation ends, the use returns to the owner without being marked consumed. The expired invitation cannot be reused. The owner can create a new invitation using the returned allowance, provided the underlying pass is still valid. Returning a reservation does not extend the pass's own expiry or restore an expired membership benefit.

What staff and customers see

The owner's profile shows available, assigned, and consumed uses. Received Guest Passes are labelled separately so staff can see who sent them, the visit date, and the location.

In the Customer Portal, the Guest registration tab shows live sent passes as Assigned and live received passes as Accepted, above the invitation forms. This list can appear even when the customer has no flow available to send a new invitation. Consumed, expired, and revoked invitations are not included in that live list; staff can review their history on the customer profiles.

In No guest limits mode, guests still have an invitation and registration record. Registering the guest marks that invitation consumed without taking a use from the inviter's owned passes.