One of the most powerful features of SuperSaaS is the ability to combine multiple calendars to create complex scheduling scenarios. For example:
- Multiple resources are required for one booking. For example, a booking for a treatment requires that both a room and a therapist are available.
- Pooled resources, presented as a single entity. For example, you have 20 identical pieces of equipment for rent and you don’t want the customer to select a particular one.
- Single resource, presented as multiple entities. For example, a club allows members to book a tennis court, but also allows walk-in customers. Members could be allowed to book the same court at a lower price or further in advance.
- Combine schedules into one view. For example, you have a different constraint on a single day of the week. You can create a separate schedule for that day and then combine it to present the user with a unified week view.
Service schedules can use resource schedules
Of the three schedule types in SuperSaaS, the “service” type schedule is the only one that can connect to other schedules, and it can only connect to “resource” type schedules. (This ability has the trade-off that you cannot create repeating appointments or appointments of variable length on the service schedule.)
Multiple resources are required for one booking
A service often requires one or more resources to be available. For example, the service “massage” would require the resource “therapist” to be available. And the service “Meeting room with projector” would require both one meeting room and one projector to be available. When calculating availability, the system would need to ensure that all required resources are available. For this to work, you create one or more resource type schedules that the service depends on. You can do this before creating the service schedule or afterwards. You can then connect the resource schedule on the page Configure > Services of the service schedule. This tutorial gives a step-by-step example.
All resources can be placed in a single resource schedule, or you can put them in separate schedules. As a rule, if you have interchangeable resources (for example, you have multiple rooms and the service can be provided in any of them) then it’s best to place those in the same resource schedule.
Pooled resources, presented as a single entity
It can be inconvenient, or undesirable, to allow the user to select from a number of similar resources. For example, you may not want a candidate to choose from a list of interviewers, but rather assign the first one available, or assign one at random.
When you connect a service to a resource schedule that has multiple resources, you will see the option to connect to Configure > Services page of the service schedule you can find an option . You have the option to let the user choose, select a resource at random, or give out the first one available in the order listed on the schedule.the resources. You can also combine resources across schedules by clicking the button. On the
It’s also possible to combine pooled resources with multiple resources for one booking, explained above. An example would be a group booking for a tour that needs 5 bikes and one guide, where you do not care which guide, nor which specific bikes get selected from the pool. Simply select theoption several times.
Single resource, presented as multiple entities
You may want to present different schedules to different audiences while ensuring that the total number of resources is not overbooked. An example would be a consultant who works in multiple locations and wants to provide a schedule tailored to each location. Each location could have a different price, different services, and different opening hours.
In this case, you would create a resource schedule as the basis and then create one or more service schedules that connect to the same resource schedule. You can define user groups to ensure that users intended for one schedule do not end up on a different one.
Combine schedules into one view
Sometimes you need more flexibility than the settings of single schedule can provide, in that combining schedules can provide a solution. For example, you may have a scenario where on weekends you need the buffer time to be different from weekdays, because travel time is different during the weekend. Or you want the limit per user to be different on Fridays to encourage more people to book on that day.
In this case you would create two (or more) resource type schedules, let’s call them “Weekday” and “Weekend” and apply the different constraints to each one. After that you create a service type schedule and define a service to be dependent on “Weekday” or “Weekend”. The result will be a logical combination of the settings on each schedule. See the next section for details on how the schedules interact.
How schedules interactWhen the system checks availability it takes into account if there are conflicting appointments for any of the requested resources, of course. However, there are many other scheduling constraints that you can configure:
- Opening hours
- Special days such as holidays
- Limit how long in advance a booking can be made
- Limit appointments per time period or in total
- Ensure a synced Google or Outlook Calendar is available
A time period is only available if it complies with all those constraints including the constraints for each resource that the service depends on. For example, if Schedule A is available at 9:00 and 10:00, and Schedule B is available at 10:00 and 11:00 then a service that depends on both Schedule A and Schedule B would only be available at 10:00. If a service depends on Schedule A or Schedule B, then it would be available at 9:00, 10:00 and 11:00.
The “Opening Hours” tab for each schedule, on the “Supervise” screen, has a section at the bottom that determines how the availability information is applied and a checkbox to allow the administrator to ignore all time constraints for the schedule. If you switch off a constraint there, it is also ignored in dependent services.
All other settings on the schedule only apply to bookings made on that particular schedule. In particular, only one email confirmation and one email reminder is sent, as defined by the confirmation setting on the schedule where the user created the booking. Email settings for the dependent resources are ignored. Also, only the price and payment settings apply to the schedule where the appointment was made.