This guide takes a new operator from an empty workspace to a fully working booking, step by step. Every step states the goal, the action, and the result you should see. Follow it in order the first time; afterward, use the individual operation pages for daily work.
Step 1 — Sign in and find your workspace
- Goal
- Access your team workspace with an account that holds staff or owner rights.
- Action
- Open /auth and sign in with Google, Microsoft, or email. The dashboard shell you land in is filtered to the capabilities your app_role (owner or staff) allows.
- Result
- You see the team dashboard with navigation for services, staff, bookings, and settings — items your role cannot use are not shown.
Step 2 — Create your first service
- Goal
- Define one real service with a real duration and constraints.
- Action
- Open the services list and create a service. Name it, set its duration, assign the staff who can deliver it, and select the resource it requires (room, device, or other constraint).
- Result
- The service appears in the list and immediately begins shaping availability: no slot can be offered that cannot serve this duration with the assigned staff and resource.
Step 3 — Verify availability behaves correctly
- Goal
- Confirm the availability engine intersects staff, service, and resource constraints.
- Action
- Open your public booking URL (https://que.qubickle.com/u/your-slug) and pick the service. Look at the offered slots, then create a booking in the busiest window.
- Result
- Only slots where the staff is scheduled, the service fits, and the resource is free are offered. After the booking, the slot disappears from the list.
Availability is an intersection
QUE does not color a calendar green and hope. A slot is offered only when every constraint the service declares — duration, staff schedule, resource, existing bookings, and overrides — agrees. If a slot you expect is missing, one of those dimensions is rejecting it; see Troubleshooting → Slot not offered.
Step 4 — Create your first booking
- Goal
- Complete the public booking flow end to end as a customer would.
- Action
- From the public booking page, select the service, a slot, and fill the intake form. Submit.
- Result
- The booking is created in the pending state, the customer receives the confirmation view with their management link, and a booking_created reminder wave is planned for the new booking.
Step 5 — Test the four required states
A booking surface is only trustworthy when its exceptions behave as well as its happy path. Test these four states before you rely on the system for daily work.
- Goal
- Normal state — a customer sees and takes an allowed slot.
- Action
- Book an open slot as a new customer.
- Result
- Booking created, staff view shows ownership, reminder waves are scheduled.
- Goal
- Changed state — a moved booking keeps its history and ownership visible.
- Action
- Use the customer's management link to reschedule.
- Result
- The booking moves to the new time; the old slot is released; staff see the change.
- Goal
- Unavailable state — the system refuses a slot the constraints reject.
- Action
- Book the last slot in a window, then try to book the same window for the same staff or resource.
- Result
- The slot is no longer offered. No double booking is possible.
- Goal
- Failed state — the operator sees enough to recover or escalate.
- Action
- Attempt a booking where a required dependency (resource, notification channel, payment provider) is misconfigured.
- Result
- The failure is surfaced with a typed error rather than silently swallowed; follow the error's guidance to fix the dependency.
What's next
With one service verified, extend deliberately: add a second service with different constraints, configure reminder messages with your own templates, connect Google Calendar so staff schedules reflect external commitments, and wire one outbound webhook to the tool your team lives in. Each of those tasks is documented in its own page under Operations and Customization.