Dealing with appointment durations

Can we please have a way to either specify an appointment duration (which is NOT the same duration as the booking time slot) or hide the appointment duration?

My booking time slots are two hours long, but they need to account for drive time to the next appointment, and the type of service. Some appointment durations are only 30 or 60 minutes, but YCBM always shows the duration at two hours because that’s the duration of the time slot. That’s misleading and confusing for clients.

I asked for this by email to support in July 2020.

Please and thank you.

The grid display is set with the increment you choose, so if you have a 2 hour timeslots then we can only display time with that increment. We hope to have an updated booking grid in the future that will hopefully allow for this level of complexity. It will be a bit of time before this is updated and I can’t guarantee that this change will be possible once that happens.

Right, but there’s a key distinction between the the duration of a time slot and the duration of an appointment. Those are two different things.

It doesn’t seem overly complicated for YCBM to allow us to:

  1. Hide the duration from clients so that they aren’t getting confused by the misinformation.
  2. For each appointment type allow us to specify a duration to display to clients (which is different from the time slot duration).

Pretty please?

Is there any update on this?

@LeroySchulz The new infrastructure changes we will be implementing over the next 6 months will need to be accomplished before looking at something like this. But again since we haven’t had too many folks looking for this, it may not be something we will implement.

With that said when you hide the duration, you would still need to specify the start time. Would that be enough for your workflow, essentially allowing the customer to choose when the start time would be?

Noted about the infrastructure changes.

With that said when you hide the duration, you would still need to specify the start time. Would that be enough for your workflow, essentially allowing the customer to choose when the start time would be?

Yes, hiding the duration would be enough for now, though it would be better to be able to specify a duration as well.

As it is, my booking slots are two hours apart to account for both the appointment duration as well as an averaged drive time to get to the next appointment. (All of my appointments are in the field.)

Currently, the YCBM system makes it appear that an appointment is two hours in duration, which in reality is never more than 60-75 minutes. That has a cascading effect in that for each appointment, multiple people (my clients, plus my client’s customers) are given a wrong expectation.

Ideally, for each type of booking I could specify a duration. But lacking that, at least being able to hide the duration would be better than the status quo.

@LeroySchulz thanks for the initial details. I had a call with another customer that is asking for this same thing. Both hiding the duration and a way to have admin overrides. Meaning the customer sees one time to book, but in the back end it accounts for drive time and other things into account.

1 Like

I’m not looking for something complicated, like YCBM having to account for GPS locations. (It seems beyond the scope of what YCBM should offer.) In my usage case, even something simple like this would be useful:

  • Specify duration of booking slots. (YCBM does this.)
  • Specify duration for each type of service, regardless of the booking slot duration. (YCBM doesn’t do this.)
  • Show the service duration instead of the booking slot duration. (YCBM doesn’t do this.) That way I can communicate to clients an accurate expectation of how long my work takes.
  • Have the option to hide the duration instead. (YCBM doesn’t do this.)

I hope that makes sense.

1 Like

Hi Ben, have those infrastructure changes been implemented now? Can we start to see some of these feature suggestions that I’ve made over the last couple of years be implemented?


HI @LeroySchulz we are testing things in small batches with some of our free users. We are very close (not definitive time) to opening this up to more folks. We also have been discussing the '23 roadmap and I will work to get this flexibility scoped out and on the list.

Okay, thanks. I also sent you a private message.

Is there an update to this feature request?