I am having trouble setting up the Resources for our desired functionality.
The goal is to have 3 services available with capacity for 2 distinct appointments each, but with the condition that different services cannot overlap. So if Service A has been booked for a day, then a second booking for that day can only be another Service A booking, and not Service B or C. Note that the two distinct appointments (so they can partially overlap) is a requirement for our needs.
For proof of concept I tried to configure this for only 2 services, but already got stuck there. What I tried was to create several resources shared between different employees, such that if an employee for service A was booked, it would take a resource that it shared with both employees for service B. For example:
- employees A1, A2, B1, and B2, 2 for services A and B respectively, - Resource, unique for the location, shared with services A and B, single location, and employees A1, B1, and B2. - Resource unique for location, shared with services A and B, single location, and employees A2, B1, and B2
It didn't work as I expected: Although booking a service with employee A1 did block appointments with B1 and B2, the same was not the case when a service was booked with A2. Deleting the first Resource did make A2 bookings block appointments for B1 and B2. It seems that only 1 resource is being taken into account.
Is this a bug? Is there a different way to get the desired result?
Based on what you’ve shared, it looks like you're trying to configure resources in a way that blocks overlapping appointments between different services. The issue you're experiencing could be due to how the resources are being shared or assigned.
Amelia's resource booking feature allows for both shared and unique resources, and understanding the difference is key here:
Shared Resources: These resources are shared among services, locations, and employees. When using a shared resource (like chairs in your example), if three chairs are shared among multiple services, bookings will be restricted once all the chairs are taken, regardless of the service being booked. This could explain why multiple services are being blocked once one resource is taken.
Unique Resources: These resources are unique to specific services or locations. If you want to prevent overlap between different services but allow multiple bookings within the same service, creating unique resources for each service would be the way to go. This will ensure that each service has its own set of resources and doesn't interfere with others, even if appointments partially overlap.
To fix your issue, I recommend setting up unique resources per service (instead of sharing them across multiple services). This will ensure that each service has its own resource limit and prevents cross-service bookings from overlapping.
If the problem persists or if you need further clarification on how to assign the resources properly, feel free to let me know!
Could you be more specific about the details of the configuration you suggest? I tried to configure it as you described but it did not give the desired result: a booking of service A now no longer blocks bookings of service B. Could you also explain how making a resource unique to a service (for example, service A) makes it so it can't overlap with bookings for service B?
To make the situation more concrete: A room can be booked for different services. The room has space for 2 to work (no employee is necessary), but the different services require different configurations of the room which cannot occur at the same time. So there are always 2 workspaces, but the first booking for a timeslot determines what kind of service is available for the second work space during that timeslot.
Here’s how you can configure resource booking in Amelia to achieve your desired setup:
Create a Resource for the Room
Go to Amelia → Services → Resources
Click + Add Resource
Name it something like “Room”
Set the quantity to 2 (since there are two workspaces)
Under Apply Resource To, select Services
Choose “Resource quantity is shared among selected items”
Assign it to all relevant services that use the room
Ensure Resource-Based Availability
Since the room configuration changes based on the first booking, the key is that once one workspace is booked for a service, the second workspace must be restricted to that same service for that timeslot.
Amelia doesn’t have a built-in feature for this exact scenario, but you can approximate it by ensuring services are linked to exclusive resources.
Alternative: Unique Resource per Service
Instead of sharing, you can create separate room resources per service (e.g., "Room for Service A" and "Room for Service B").
Set both to quantity = 2, but apply each resource only to its respective service.
This way, once a service is booked, only that specific resource is used, blocking the other service.
Expected Result
If a customer books Service A at 10:00, one workspace remains open, but only for another Service A booking.
If both workspaces are booked with Service A, Service B is unavailable at 10:00.
This ensures that a different configuration cannot be booked in the same timeslot.
Would you like more clarification or adjustments based on your needs?
Hi Uros, I was hopeful at first but on trying this out it became clear that this is not helping.
I am not sure what the numbering in your reply suggests: Step 1 does by itself not give the expected outcome (I skipped "Under Apply Resource To, select Services" since it is not available in the UI) and step 2 has no instructions and step 3 describes an alternative approach. Step 3 actually comes close to the approach I mentioned in opening this ticket, but it did not work as expected.
Can you share some screenshots of how you configured this use case?
Thank you for your feedback. Could you please provide more details about what didn't work with Step 3? It would help me understand where the issue lies so I can offer a more tailored solution.
Additionally, if you could share any screenshots of your current setup, that would also be very helpful in resolving the issue more efficiently.
I attached a screenshot of the resources page and the booking page for the 4 employees (booking element per employee to easily see if it works as intended). Z/W could be considered service A and Kleur would then be service B.
The following bookings were made:
- Z/W1 was booked on Feb 10 the entire day, and partially on Feb 11 - Z/W2 was booked on Feb 11 the entire day - Kleur1 was booked on Feb 12 the entire day - Kleur2 was booked on Feb 13 the entire day
I think this resource configuration is what you suggested, but on the resulting image you can see the following:
Even though Feb 10 and 11 have been booked the entire day by at least one of Z/W1 and Z/W2, the other employees (Kleur1 and Kleur2) can be booked on those days. The same goes the other way around for Feb 12 and 13. The expected result is that Feb 10 and 11 would be blocked for Kleur1 and Kleur 2, and that Feb 12 and 13 would be blocked for Z/W1 and Z/W2.
With the resource setup I think this makes sense: there is no connection between the two different services.
Hi,
I am having trouble setting up the Resources for our desired functionality.
The goal is to have 3 services available with capacity for 2 distinct appointments each, but with the condition that different services cannot overlap. So if Service A has been booked for a day, then a second booking for that day can only be another Service A booking, and not Service B or C. Note that the two distinct appointments (so they can partially overlap) is a requirement for our needs.
For proof of concept I tried to configure this for only 2 services, but already got stuck there. What I tried was to create several resources shared between different employees, such that if an employee for service A was booked, it would take a resource that it shared with both employees for service B. For example:
- employees A1, A2, B1, and B2, 2 for services A and B respectively,
- Resource, unique for the location, shared with services A and B, single location, and employees A1, B1, and B2.
- Resource unique for location, shared with services A and B, single location, and employees A2, B1, and B2
It didn't work as I expected: Although booking a service with employee A1 did block appointments with B1 and B2, the same was not the case when a service was booked with A2. Deleting the first Resource did make A2 bookings block appointments for B1 and B2.
It seems that only 1 resource is being taken into account.
Is this a bug? Is there a different way to get the desired result?
Kind regards
Hello Rick,
Thanks for providing the detailed explanation!
Based on what you’ve shared, it looks like you're trying to configure resources in a way that blocks overlapping appointments between different services. The issue you're experiencing could be due to how the resources are being shared or assigned.
Amelia's resource booking feature allows for both shared and unique resources, and understanding the difference is key here:
Shared Resources: These resources are shared among services, locations, and employees. When using a shared resource (like chairs in your example), if three chairs are shared among multiple services, bookings will be restricted once all the chairs are taken, regardless of the service being booked. This could explain why multiple services are being blocked once one resource is taken.
Unique Resources: These resources are unique to specific services or locations. If you want to prevent overlap between different services but allow multiple bookings within the same service, creating unique resources for each service would be the way to go. This will ensure that each service has its own set of resources and doesn't interfere with others, even if appointments partially overlap.
To fix your issue, I recommend setting up unique resources per service (instead of sharing them across multiple services). This will ensure that each service has its own resource limit and prevents cross-service bookings from overlapping.
If the problem persists or if you need further clarification on how to assign the resources properly, feel free to let me know!
Kind Regards,
Uros Jovanovic
[email protected]
Rate my support
Try our FREE mapping plugin! MapSVG - easy Google maps, interactive SVG maps, and floor plans, choropleth maps and much more - https://wordpress.org/plugins/mapsvg-lite-interactive-vector-maps/
wpDataTables: FAQ | Facebook | Twitter | Instagram | Front-end and back-end demo | Docs
Amelia: FAQ | Facebook | Twitter | Instagram | Amelia demo sites | Docs | Discord Community
You can try wpDataTables add-ons before purchasing on these sandbox sites:
Powerful Filters | Gravity Forms Integration for wpDataTables | Formidable Forms Integration for wpDataTables | Master-Detail Tables
Hi Uros,
Thank you for your reply.
Could you be more specific about the details of the configuration you suggest? I tried to configure it as you described but it did not give the desired result: a booking of service A now no longer blocks bookings of service B.
Could you also explain how making a resource unique to a service (for example, service A) makes it so it can't overlap with bookings for service B?
To make the situation more concrete: A room can be booked for different services. The room has space for 2 to work (no employee is necessary), but the different services require different configurations of the room which cannot occur at the same time. So there are always 2 workspaces, but the first booking for a timeslot determines what kind of service is available for the second work space during that timeslot.
Kind regards,
Rick
Hello Rick,
Here’s how you can configure resource booking in Amelia to achieve your desired setup:
-
- Go to Amelia → Services → Resources
- Click + Add Resource
- Name it something like “Room”
- Set the quantity to 2 (since there are two workspaces)
- Under Apply Resource To, select Services
- Choose “Resource quantity is shared among selected items”
- Assign it to all relevant services that use the room
-
- Since the room configuration changes based on the first booking, the key is that once one workspace is booked for a service, the second workspace must be restricted to that same service for that timeslot.
- Amelia doesn’t have a built-in feature for this exact scenario, but you can approximate it by ensuring services are linked to exclusive resources.
-
- Instead of sharing, you can create separate room resources per service (e.g., "Room for Service A" and "Room for Service B").
- Set both to quantity = 2, but apply each resource only to its respective service.
- This way, once a service is booked, only that specific resource is used, blocking the other service.
Expected ResultCreate a Resource for the Room
Ensure Resource-Based Availability
Alternative: Unique Resource per Service
Would you like more clarification or adjustments based on your needs?
Kind Regards,
Uros Jovanovic
[email protected]
Rate my support
Try our FREE mapping plugin! MapSVG - easy Google maps, interactive SVG maps, and floor plans, choropleth maps and much more - https://wordpress.org/plugins/mapsvg-lite-interactive-vector-maps/
wpDataTables: FAQ | Facebook | Twitter | Instagram | Front-end and back-end demo | Docs
Amelia: FAQ | Facebook | Twitter | Instagram | Amelia demo sites | Docs | Discord Community
You can try wpDataTables add-ons before purchasing on these sandbox sites:
Powerful Filters | Gravity Forms Integration for wpDataTables | Formidable Forms Integration for wpDataTables | Master-Detail Tables
Hi Uros,
I was hopeful at first but on trying this out it became clear that this is not helping.
I am not sure what the numbering in your reply suggests: Step 1 does by itself not give the expected outcome (I skipped "Under Apply Resource To, select Services" since it is not available in the UI) and step 2 has no instructions and step 3 describes an alternative approach. Step 3 actually comes close to the approach I mentioned in opening this ticket, but it did not work as expected.
Can you share some screenshots of how you configured this use case?
Kind regards,
RIck
Hello Rick,
Thank you for your feedback. Could you please provide more details about what didn't work with Step 3? It would help me understand where the issue lies so I can offer a more tailored solution.
Additionally, if you could share any screenshots of your current setup, that would also be very helpful in resolving the issue more efficiently.
Looking forward to your response!
Kind Regards,
Uros Jovanovic
[email protected]
Rate my support
Try our FREE mapping plugin! MapSVG - easy Google maps, interactive SVG maps, and floor plans, choropleth maps and much more - https://wordpress.org/plugins/mapsvg-lite-interactive-vector-maps/
wpDataTables: FAQ | Facebook | Twitter | Instagram | Front-end and back-end demo | Docs
Amelia: FAQ | Facebook | Twitter | Instagram | Amelia demo sites | Docs | Discord Community
You can try wpDataTables add-ons before purchasing on these sandbox sites:
Powerful Filters | Gravity Forms Integration for wpDataTables | Formidable Forms Integration for wpDataTables | Master-Detail Tables
Hi Uros,
I attached a screenshot of the resources page and the booking page for the 4 employees (booking element per employee to easily see if it works as intended). Z/W could be considered service A and Kleur would then be service B.
The following bookings were made:
- Z/W1 was booked on Feb 10 the entire day, and partially on Feb 11
- Z/W2 was booked on Feb 11 the entire day
- Kleur1 was booked on Feb 12 the entire day
- Kleur2 was booked on Feb 13 the entire day
I think this resource configuration is what you suggested, but on the resulting image you can see the following:
Even though Feb 10 and 11 have been booked the entire day by at least one of Z/W1 and Z/W2, the other employees (Kleur1 and Kleur2) can be booked on those days.
The same goes the other way around for Feb 12 and 13.
The expected result is that Feb 10 and 11 would be blocked for Kleur1 and Kleur 2, and that Feb 12 and 13 would be blocked for Z/W1 and Z/W2.
With the resource setup I think this makes sense: there is no connection between the two different services.
Hope this clarifies things!
Kind regards,
Rick
Attached files: amelia_alternative.png
amelia_result.png
Hi Rick,
Thanks for the detailed explanation and screenshots! I’ll take a closer look at this and get back to you as soon as I have more information.
Appreciate your patience!
Kind Regards,
Uros Jovanovic
[email protected]
Rate my support
Try our FREE mapping plugin! MapSVG - easy Google maps, interactive SVG maps, and floor plans, choropleth maps and much more - https://wordpress.org/plugins/mapsvg-lite-interactive-vector-maps/
wpDataTables: FAQ | Facebook | Twitter | Instagram | Front-end and back-end demo | Docs
Amelia: FAQ | Facebook | Twitter | Instagram | Amelia demo sites | Docs | Discord Community
You can try wpDataTables add-ons before purchasing on these sandbox sites:
Powerful Filters | Gravity Forms Integration for wpDataTables | Formidable Forms Integration for wpDataTables | Master-Detail Tables