Configure Services

Services represent bookable offerings in Tiquo.

A service defines what a customer can reserve, such as an appointment, experience, or activity. Any time-based offering in Tiquo is managed as a booking. Services define what can be booked, while bookings manage the operational scheduling of that service.

Examples include:

• Massage appointment
• Spa treatment
• Fitness class
• Private session
• Workshop

Services are configured within a sublocation and determine how bookings are scheduled, priced, and managed.

Navigating to Services

Services are configured per sublocation. To open the services workspace:

1. From the main sidebar, select Locations.
2. Choose a location, then click the sublocation card whose services you want to manage.
3. Open the Configure Services section within that sublocation.

Simple Mode

The Configure Services page has a Simple Mode designed to cover everyday service configuration without requiring the full advanced flow graph. Select a Business Type to apply the terminology, booking order, scheduling method, party-size rules, and workspace structure for that operation.

Simple Mode uses four workspace patterns:

• Appointment uses a direct appointment-type-to-calendar workspace for staff, rooms, or equipment.
• Restaurants and bars manage table and seat instances directly.
• Spa & Treatments uses a connected treatment-to-room workspace.
• Hotel Rooms, Meeting Rooms, Gym, Sport and Leisure Facilities, Venue Hire, and Classes & Tutoring use service folders containing connected inventory.
• Exhibitions, entertainment venues, and Events use category folders containing ticket types and a paired schedule.
• Health Club combines the Spa and Gym workspace patterns as separate sections within one customer flow.

Choose the guide for the selected Business Type:

For service-folder modes, an inventory item can be created for one service or linked as existing inventory. Linking the same facility to multiple services shares its capacity across those booking options. For example, one padel court can fulfil member, guest, and public activities; a booking through any of them consumes the court's availability.

The Business Type selector is locked once services or inventory have been created. Delete those items before changing to a different preset.

The Simple Mode sidebar provides the industry workspace plus Booking Flow, Appearance, Localization, and Notifications. Booking Flow expands to General, Services, Steps & navigation, Scheduling, Customer details, Payment, Policies, Layout, and Deployment.

Use Download TXT config from the Simple Mode actions to export the visible workspace, booking-flow, service, inventory, connection, category, instance, service-setting, and offer configuration as a readable text file. The export is for review and support; it does not create a second configuration or expose credentials.

Simple Mode handles common day-to-day setup. For multiple customer flows, detailed inventory logic, or custom graph structures, use Advanced Mode. Advanced Mode can return to Simple Mode only when the sublocation has no services or inventory; remove those items first or the Simple Mode option remains locked.

Advanced Mode and Flow Builder

Advanced Mode is a three-column visual flow builder showing how customer and staff journeys connect to services and inventory. The + button at each column header adds a new card for the respective columns. These can also be added from the bottom action bar.

Guided Setup and Templates

Some sublocation templates use a guided setup flow to create the right services and inventory structure for the type of business being configured.

Guided setup is useful when the inventory is the main thing customers book. For example:

• Restaurants and bars can be set up around tables
• Hotels can be set up around rooms
• Meeting spaces can be set up around rooms or bookable spaces
• Spas can be set up around treatment rooms or therapists
• Events can be set up around ticket types and scheduled slots

These guided flows still create normal Tiquo services, customer flows, staff flows, and inventory behind the scenes. They simply reduce the number of manual steps needed to get a common venue type operational.

Advanced mode remains available for teams that need to customise flow connections, service categories, inventory rules, pricing, or availability in more detail.

Customer / Staff Flows

Defines how bookings are initiated. Two flow types exist:

• Customer Flow: the booking journey customers follow when they book themselves (website, portal, branded flow)
• Staff Flow: the booking journey staff follow when booking on behalf of a customer in Tiquo through bookings and orders

Customer-facing booking surface: each Customer Flow deploys to its own Hosted Page URL and Embed Code (see the Customer Flow editor's Deployment tab). Customers reach a flow via that hosted page, an embed on the operator's website, or a branded shareable link. Whatever services are connected to that flow are the services the customer sees; the inventory connections drive resource allocation when the booking is created.

Customer Flow Editor

The editor is organised into tabs. Each tab controls one part of the customer-facing booking journey.

Setup > Services

Choose which services are available on the flow and how they are presented on the booking page.

Use Show Capacity to display the exact remaining capacity once both the service and date/time are known. Capacity appears on the choice that completes that context:

• Category → Date/Time → Service: on the service
• Category → Service → Date/Time: on the date/time
• Date/Time → Category → Service: on the service
• Agenda List View: directly on the agenda item

Services with unlimited capacity do not display a remaining-capacity value. Turning this setting off changes presentation only; capacity limits are still enforced.

Setup > Steps & Navigation

Set the order of the booking steps and how customers move through them.

Setup > Scheduling

Configure the calendar, time slots, and party size.

Setup > Customer Details

Configure the fields customers fill out when making a booking.

Custom fields can be linked to active Customer Parameters so submitted details are saved as structured customer data. Field and parameter types must be compatible; compound parameters require a nested field, select-based inputs support option mapping, and the field type remains locked while the link is active.

Setup > Payment

Control the payment step, accepted payment methods, and wallet domains.

Setup > Policies

Choose what customers review before completing their booking.

Appearance & Layout

Customise the look, page structure, and alignment of the booking form.

Use Show Duration in the service display settings to control whether customers see service duration in service choices, booking summaries, payment details, confirmations, and supported booking tickets. Turning it off changes presentation only; duration still controls availability and booking end times.

Notifications

Configure which emails your customers receive.

Deployment

Deployment contains the Hosted Page URL, an Embed Code snippet for the website, and Apple Pay and Google Pay domain registration.

Why multiple Customer Flows? Customer Flows multiplex the booking experience: which services appear, which steps the user walks through, which theme renders, which payment and invitation rules apply, and which surface deploys the flow. A sublocation can run several in parallel, for example a public website embed, a VIP shareable link with a different service set and theme, and an in-room iPad self-booking page. Staff Flows by contrast are limited to one per service and cover all staff surfaces uniformly.

Staff-facing booking surface: the Staff Flow drives every staff booking surface across the dashboard, iPhone, iPad, Android, and PDQ (the UK term for a card-payment terminal). A service can have at most one Staff Flow attached, so unlike Customer Flows there is no multiplication of staff experiences.

Editing Staff Flow:

• Configure: confirms the Staff Flow is for staff booking on behalf of a customer across the dashboard, iPhone, iPad, Android, and PDQ.
• Connected Services: which services this flow exposes, drag-and-drop to reorder, grouped by Category.
• Steps: Booking Flow Type (Date/Time → Service, Service → Date/Time, Agenda List View), Party Size (min, max, default, label), Invitations toggle, Payment toggle.
• Display: Quantity Selector toggle.
• Notifications: Booking Confirmation, Appointment Reminder, Cancellation Email, Follow-up Email, Tickets & QR Codes, Wallet Cards, Calendar Attachment toggles.

Services / Categories

Each service appears as a card showing its name, price, duration, and a short description. Services can be grouped into Service Categories for organisation (e.g., a Spa Treatments category containing Deep Tissue Massage, Aromatherapy Massage, and Facial Treatment).

General Settings: service name, description, image, visibility status, and a featured service toggle. The Active toggle controls whether the service appears in booking flows.

Pricing:

• Price: base cost of booking the service (e.g., £60 for a 60-minute massage).
• Named fixed prices: for a fixed-price service, add choices such as Standard and Member rather than duplicating the service. Choose the default option and optionally restrict another option to active memberships, selected plans, or membership permissions. Eligible customers choose from the visible prices in the booking flow.
• VAT: rate applied; the tax portion is calculated automatically (e.g., 20% on a £60 service). New services start with an editable default based on the parent location's country, or the configured US state. Review the rate because local, reduced, service-specific, exempt, and threshold rules are not inferred.
• Payment Requirement: Require full payment (full amount at booking) or Require deposit (deposit at booking, balance later).
• Pricing Levels: multiple price tiers per service (e.g., Economy, Standard, Premium, Rack Rate). Connected to Pricing Seasons.
• Pricing Seasons: apply different pricing levels during specific date ranges (name, start, end, assigned level, optional yearly repeat). Default level applies when no season matches.
• Packages: group services into predefined offerings such as bundled services, promotional offers, or special pricing structures. Each package has a name, package code suffix, description, package type, and an optional wholesale flag.

Restricted named prices remain hidden when the booking flow cannot identify the customer. Require or allow customer login, or identify the customer through a supported website integration, before relying on member-specific price choices.

When an access rule uses Show as locked, an identified customer who is not eligible can still see the service or ticket, but cannot select it. Without this option, the ineligible choice is hidden. Login must be available on the flow, or the customer must be identified by a supported website integration, for locked access to be evaluated reliably.

Time-Based Pricing: services can carry variable prices depending on the time of day or day of the week. Each rule defines the days, time window, and price that applies inside that window. When a customer books, the matching rule sets the price; bookings outside every rule use the base price.

Booking offers: a promotion can be shown as a booking offer with its own name, description, fixed offer price, optional image, eligible services, days, date range, and time window. The customer sees the offer only for matching availability and can open its details before choosing a slot. At least one service and one day are required.

Access: the Access tab controls who can book the service and how many times each identified customer can book it. Access can be restricted to active memberships, specific membership plans, or membership permissions. A per-customer booking limit can also be set, for example one member ticket per event date or two guest tickets per member per event.

This allows a single event to offer multiple ticket types with different audiences, prices, and booking limits.

Duration and Capacity:

• Service Type: Calendar based (duration and capacity defined on the service, used for appointments, classes, treatments) or Slot based (availability controlled by connected inventory slots).
• Duration Type: minutes, hours, nights, or days.
• Duration: how long the service lasts (e.g., 60 minutes for a massage appointment).
• Capacity: maximum customers who can book the same slot.
• Buffers: Buffer Before adds prep time; Buffer After adds reset time. Prevents overlapping bookings.
• Booking intervals: for calendar-based services, choose Derive from service duration, Custom booking intervals, or Optimise availability. Custom intervals offer starts every 5, 10, 15, 20, 30, or 45 minutes. Optimise availability packs valid starts around availability, existing bookings, capacity, and buffers to reduce unusable gaps.

Whether the duration is shown to customers is controlled separately by the Customer Flow's Show Duration display setting.

Limits:

• Minimum Advance: how far ahead a customer can create a booking (e.g., 2 hours).
• Maximum Advance: how far into the future bookings can be made (e.g., 90 days).
• Cancellation Deadline: how long before start a customer can cancel (e.g., 24 hours).
• Auto Confirm Bookings: when on, bookings confirm automatically; when off, manual approval may be required.
• Booking Buffer: minimum time between consecutive bookings (e.g., 15 minutes).
• Auto Checkout: automatically checks customers out after the booking duration. Only fires when no other order items are attached.
• Allow Same Day Booking: allows same-day bookings.
• Require Approval: requires staff to approve bookings before confirmation.

Availability:

• Start Time / End Time: earliest and latest times the service can begin (e.g., 09:00 to 17:00).
• Available Days: which weekdays the service runs (e.g., Monday to Friday).
• Time Slot Interval: choose the service duration, a custom interval, or Optimise availability for calendar-based services. An Advanced staff flow can override the connected service's interval for that staff booking journey.
• Buffer Between Bookings: additional time inserted between consecutive bookings.

Inventory / Slots / Calendar

The physical or scheduling resources that services draw on. Each card shows the resource name, capacity, and its scheduling mode (Flexible, Fixed Slots, etc.).

Editing Inventory:

• General: name, description, Enable Waitlist toggle (allows customers to join a waitlist when the resource is fully booked).
• Capacity: Simple Capacity (a single total) or Use Instances (individually-named rooms, tables, or seats with bulk-add).
• Availability: Availability Windows with start/end times, recurrence (Specific Days), day picker, optional break windows.

Use Instances when each unit is named and bookings need to be allocated to a specific instance (Treatment Room 1 vs. Treatment Room 2). Simple Capacity treats the resource as a single bucket of N concurrent slots.

For tables, rooms, ticket types, and similar named resources, instances make each unit visible to staff and allow bookings to be allocated to a specific resource. This is the structure used by guided setup flows for restaurants, bars, hotels, meeting rooms, spas, and events.

Slot-based event inventory can use individual slot durations and recurrence rules so each event date or ticket slot can carry the right timing and capacity.

Connected Inventory: when a service is connected to inventory, bookings can only be created if the required resource is available. Inventory resources can also be prioritized to determine which is allocated first when multiple options are available.

Product add-ons

A customer flow can offer products after the customer chooses their booking. Open Product add-ons, turn it on, and choose active fixed-price products from the same sublocation. Custom-priced products are not available as add-ons.

Set the heading shown to customers and the maximum quantity for each product. The allowed maximum is between 1 and 100. Selected products are added to the same order as the booking and are paid for during checkout. A sold-out product remains unavailable.

No-show card guarantee

Simple Mode services can save a customer's card at checkout without taking a payment. Staff can charge the agreed fee only when they mark that booking as a no-show.

Turn on No-show card guarantee in the Payment settings, enter a fee greater than zero, and choose whether it applies once per booking or once per person. The policy is recorded with the booking at checkout. Marking a booking as a no-show still works when there is no guarantee, but no fee is charged.

Waitlists

Turn on Enable Waitlist for inventory that customers may request when a slot is full. Joining the waitlist does not take payment. If capacity becomes available, Tiquo sends the customer a temporary offer with an expiry time.

The customer accepts either a free offer or an offer that requires payment. If the offer expires, the request returns to the waitlist instead of becoming a confirmed booking.

Guest invitations

Customer and staff flows can collect guest details when invitations are enabled. A signed-in customer can also create and share secure guest invitations from a portal where Guest registration is available. Invitation emails use the configured booking notification branding and templates. Delivery failures are shown to staff so the invitation can be corrected or sent again.

When the flow covers sublocations in more than one parent location, include the selected location in the invitation. The guest preregistration page then opens with the intended venue context. Where an invitation includes a Guest Pass, its issued balance and available, redeemed, or expired state remain visible in the portal.

Localised time display

Under a flow's Localization settings, choose 12-hour or 24-hour time and turn on Hide Leading Zeros when customer-facing times should display as 2:30 PM instead of 02:30 PM, or 8:30 instead of 08:30. The setting applies to supported slot lists, summaries, offers, and confirmation views.

Services in Orders

When a service is booked, it appears in an order as an order item.

Example:

Order:

• Massage Appointment (booking)
• Herbal Tea (product)
• Face Cream (product)

The booking manages the operational scheduling, while the order manages the commercial transaction.

Summary

Services define the appointments and experiences that customers can book.

They control:

• Pricing
• Duration
• Capacity
• Booking rules
• Availability

Services connect the operational booking system with the commercial order system, allowing businesses to manage both scheduling and transactions within a single platform.