The capacity and operational logic behind services are defined by two key factors: which resources are assigned to them and what type of service they are. With these settings, you control how many bookings can be created and how the service appears to customers.
Resource assignment
The resources assigned to a service (such as rooms, professionals, or equipment) determine the actual capacity. You can assign multiple resources to a single service, allowing you to flexibly shape availability and distribute load.
- Resource list overview: quickly review and select available resources.
- Assignment rules: the same resource can be assigned to multiple services.
- Capacity impact: the more resources you assign, the more flexible the booking calendar becomes.
Service types
The service type setting defines how the system handles bookings and presentation. Availability of service types depends on your plan, so always check that the required type is enabled.
single
The single type is the default format for classic, individual appointments. One booking usually represents one customer and one time slot. It is ideal when each participant needs personal attention and the service should run in isolated sessions.
- What it is: one-person booking logic for 1:1 sessions.
- Typical use cases: consultations, screenings, personal coaching, individual treatment sessions.
- Capacity behavior: capacity is usually 1 per slot, but assignment and scheduling rules still apply through the connected resources.
- Operational benefit: simple calendar management, predictable flow, and clear customer communication.
group
The group type allows multiple participants to register for the same slot. This format is useful when the service can be delivered to several people at once without duplicating staff time.
- What it is: shared booking slots with multi-participant attendance.
- Typical use cases: classes, workshops, orientation sessions, small group trainings.
- Capacity behavior: the configured capacity controls how many participants can fit into one slot.
- Operational benefit: better utilization and higher throughput for repeatable sessions.
monthly_batch
The monthly_batch type is designed for monthly planning workflows where participant requests are collected first and finalized later. Instead of immediate slot-by-slot booking, the process runs in predefined monthly windows.
- What it is: cycle-based allocation with monthly planning periods.
- Typical use cases: rota-like service allocation, recurring program participation, period-based scheduling processes.
- Capacity behavior: candidate options are gathered, then matching/finalization happens according to your monthly batch rules.
- Operational benefit: controlled planning at scale, reduced manual coordination, and transparent monthly operations.
How to choose: use single for strict 1:1 delivery, group when many people can join one occasion, and monthly_batch when scheduling must be coordinated in recurring monthly rounds.