Skip to main content

Getting Started

Welcome to the Sessiq documentation! This guide will help you get started with the platform.

What is Sessiq?

Sessiq is a comprehensive, multi-tenant SaaS platform designed for managing bookings for leisure activities, tours, experiences, and workshops. Built for businesses that need flexible scheduling, resource management, and seamless customer booking experiences.

Key Features

  • Multi-tenant Architecture: Complete data isolation for each tenant organization
  • Flexible Scheduling: Recurring schedules, overrides, and blackout windows with timezone support
  • Resource Management: Track and allocate rooms, equipment, staff members, and inventory items
  • Payment Processing: Support for multiple payment providers (Stripe, Paytrail) with voucher/gift card integration
  • Admin Dashboard: Full-featured admin panel with real-time calendar updates and drag-and-drop rescheduling
  • Customer Booking Flow: Seamless booking experience with availability search, hold mechanism, and payment processing
  • Promotions & Pricing: Flexible pricing rules with party size tiers, temporal modifiers, and promotion stacking
  • Comprehensive Reporting: Revenue, capacity utilization, and booking analytics

Key Concepts

Before diving into the documentation, it's helpful to understand these core concepts:

Tenant

A tenant represents an independent organization using the platform. Each tenant has complete data isolation - they cannot see or access data from other tenants. A tenant typically represents your business or organization.

Site

A site is a physical venue or location with its own schedule and configuration. A tenant can have multiple sites. Each site has:

  • A timezone setting
  • Business hours and availability rules
  • Associated products and resources
  • Independent scheduling configuration

Product

A product is a bookable activity or service (e.g., "Laser Tag Session", "Escape Room Experience", "Cooking Workshop"). Products have:

  • Duration and capacity limits (minimum/maximum party sizes)
  • Required resources (rooms, equipment, staff)
  • Associated schedules for availability
  • Pricing configuration through variants

Variant

A variant represents different configurations of a product. For example, a "Laser Tag" product might have variants:

  • Standard Session (60 minutes)
  • Extended Session (90 minutes)
  • Premium Package (with add-ons)

Each variant can have different pricing, resources, or participant requirements.

Resource

A resource is an entity that must be allocated for a booking. Resources can be:

  • Rooms: Physical spaces (e.g., "Party Room A", "Conference Hall")
  • Equipment: Items that must be available (e.g., "Laser Tag Equipment Set 1")
  • Staff: Personnel required for the booking (e.g., "Instructor - Sarah")
  • Items: Consumable or inventory items (e.g., "Safety Waivers", "Equipment Cleaning Kit")

Resources can be shared across multiple bookings or reserved exclusively.

Slot

A slot is a specific time window available for booking. Slots are generated based on:

  • Schedule templates and overrides
  • Blackout windows
  • Resource availability
  • Capacity pools

Slots display start time, end time, available capacity, and any special labels (e.g., "Adults Only", "Toddler Friendly").

Booking

A booking is a reservation made by a customer for a specific product variant at a specific slot. Bookings go through several states:

  1. Hold: Temporary reservation that expires after a set time
  2. Confirmed: Payment processed and booking confirmed
  3. Completed: The activity has finished
  4. Cancelled: Booking was cancelled (may be refunded)

Quick Start Guide

For Administrators

  1. Access the Admin Panel: Log in to your admin portal using your credentials
  2. Set Up Your Site:
    • Configure your first site with business hours and timezone
    • Set up your organization's details and contact information
  3. Create Resources:
    • Add rooms, equipment, staff, and items that your bookings will use
    • Configure capacity and availability rules
  4. Create Products:
    • Add activities or services that customers can book
    • Create variants for different configurations
    • Configure pricing rules and participant requirements
  5. Configure Schedules:
    • Set up schedule templates for recurring availability
    • Add overrides for special dates
    • Configure blackout windows for maintenance or holidays
  6. Set Up Pricing:
    • Configure price rulesets for your variants
    • Set up party size tiers and temporal modifiers
  7. Start Accepting Bookings: Customers can now book your products through the customer-facing interface or API!

For Customers

  1. Search Availability:
    • Select a product and date range
    • Specify party size
    • View available time slots
  2. Select a Slot:
    • Choose your preferred time slot
    • Add any optional add-ons or resources
  3. Review Pricing:
    • See detailed pricing breakdown
    • Apply promotion codes or vouchers if available
  4. Create Hold:
    • A temporary hold is placed on the slot
    • You have a limited time to complete payment
  5. Complete Payment:
    • Choose payment method (card, voucher, or payment on arrival if available)
    • Complete payment to confirm booking
  6. Receive Confirmation:
    • Get booking confirmation with details
    • Receive notifications via email or SMS

Common Workflows

Booking a Session (Customer)

  1. Search for available slots → 2. Select time and add-ons → 3. Apply promotions → 4. Create hold → 5. Complete payment → 6. Receive confirmation

Managing a Booking (Admin)

  1. View booking in calendar → 2. Check details or make changes → 3. Reschedule or cancel if needed → 4. Process refunds if applicable → 5. Mark as completed or no-show

Setting Up a New Product (Admin)

  1. Create product → 2. Create variants → 3. Configure required resources → 4. Set up schedules → 5. Configure pricing → 6. Publish and make available

Next Steps

Now that you understand the basics, explore the detailed documentation:

Support and Resources

  • API Documentation: Complete endpoint reference in the API Overview
  • Developer Resources: See the Developer Guide for system architecture
  • Best Practices: Configuration guides and tips in admin documentation sections