Not checking for booking conflict

  • When I recently set up new booking dates for my client, I found that it doesn’t check for a conflict in time slots scheduled for the same worker but for different services. Please bear with me while I try to explain how this happens.

    My client offers two types of sessions: a Mini session (30 minutes) and a Full session (60 minutes). We book the Minis for 1:00-1:30, and the Full for 2:00-3:00. Yesterday I set up Full sessions for 4 dates in December. Then I cloned this Connection group and changed the service from Full to Mini sessions.

    What I didn’t notice was that I forgot to change the time, so it wound up with *both* a Full session and 2 Mini 30-minute sessions booked together for 2:00-3:00 on those dates. The “worker” was the same and the “venue” was the same in these Connections, but the Service was different. So, somehow the plugin thinks that a Worker can perform 2 services at the same time in the same place, which in most situations will not be possible.

    This seems to be a bug or at least a weakness in the plugin that really should be fixed. Ideally, if there are two services scheduled for the same time slot, for a particular worker, it should trip an error switch and warn you that the time is already scheduled for that worker. As it is now, however, it just goes ahead and schedules that time slot for both services; it doesn’t recognize that there’s a conflict.

    We noticed the problem because after all of the Full sessions for those dates had become booked (appt requests had been received), all of the Minis for those dates were also showing as being booked but no Mini requests had been received for those dates.

    It really just needs an error check for when two Connections include the same date and time (or overlapping times) for the same worker. I’m not sure if there would ever be a situation where the same worker could perform services in different Venus at the same time, but that might need to be an additional criteria to check. To account for unexpected uses of the plugin, it might be an idea to warn the person with a message (“Warning: there is a conflict with another date and time for this worker and venue” or something like that) and then allow them to accept/ignore the conflict anyway when the Connection is being set up.

    I’m hoping this can be changed/fixed in an upcoming update. Thanks! Let me know if you need me to clarify anything about this.

Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Author Nikola Loncar

    (@loncar)

    Hi,

    you can change right now, it’s part of settings. It is first option in Settings > Customize page called Multiple work. Just unselect that option and it will check all location/services for that worker.

    Best regards,
    Nikola

    Thread Starter Evolvingdoor

    (@evolvingdoor)

    Hi Nikola,

    Thanks for getting back to me. I had forgotten about that setting, however it is already unchecked. Autoreservation is also unchecked, since my client wants to approve all appointments before they are confirmed. Would autoreservation make a difference?

    Thx.

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘Not checking for booking conflict’ is closed to new replies.