Improve Availability Copy when using Limit Future Bookings settings

[yordis]

Is your proposal related to a problem?

I set up the "Limit future bookings" to be "3 calendar days" into the future.

When a user is trying to book, the availability feels a bit misleading, and I am worried that people will be discouraged from checking again (in my case) every three days.

There is indeed availability in the following months, just that it is too far into the future, so you must wait until the threshold is met if you care about a particular day.

Describe the solution you'd like

Improve the copy text, making it clear that the user can not book that far into the future.

Describe alternatives you've considered

• Disable the configuration

Additional context

Requirement/Document

[github-actions[bot]]

Thank you for opening your first issue, one of our team members will review it as soon as it possible. ❤️🎉

[sarthaksharma27]

@yordis can you explain what the issue more clearly ?

[PeerRich]

what would be the ideal solution here?

[yordis]

In an ideal scenario, the component is aware of "Limit Future Bookings", "Limit total bookings duration", "Limit bookings frequency," and so on.

At the very least, change the "No availability" copy.

Maybe something like "You can not book that far into the future" with a question mark icon or something explaining the availability.

I am not sure honestly. As a customer, I ended up removing the "Limit future bookings" setting because I rather let people book that far into the future, than thinking the whole year is unavailable 😭 While at the time, I would like to keep it, I am trying to avoid canceling meetings because I have no clue what I am gonna do a week from today 😄

[yisalk]

@yordis, Can you please record a video and share it here? So we all can have an idea of the issue you are highlighting?

[yordis]

https://github.com/calcom/cal.com/assets/4237280/6d73c7b7-8580-43ad-8029-51da5102e51e

[Kunal-debug-png]

Provide clear information about the booking threshold and when additional slots are likely to open up. For example, you can say, "New booking slots open every three days. Please check back for availability." This helps users understand the booking process and encourages them to return. Also, can I work on this issue?

[mjsf1234]

I have understood the issue ...we can note down the limit -future-booking variable and show the user that the slot for booking is available to ${limit -future-booking variable} from today. @yordis can you assign this issue to me? I have done the local setup and am ready to raise the PR

[khushalmajoka]

Hi @yordis, I got the issue and trying to work on it. Can you please check the below:

Is this what you want?

[yordis]

@khushalmajoka I think that is a decent message, yes.

[khushalmajoka]

Ok so should i make the changes, finalize and create a PR? @yordis

[yordis]

I would recommend you do so, and wait for people to review it!

[khushalmajoka]

Okay @yordis, Thankyou ❤️

[Kick933]

Hi, Since the previous PR has been marked stale, should we continue the discussion ahead? The last PR did not account for few cases, like if date after threshold-days falls in next month, we should continue to show view next month. But if the date after threshold-days falls in current month, we should change the message to saying "Please check back after x days" and remove the CTA (Button) as it becomes irrelevant in this case. This will keep the Check next month feature intact for all cases except what is required. Also, is there any impact that I am not accounting for? Would love to work on this.

[Kick933]

Hi, just wanted to check for any updates here? Can I pick this up and start working?

[Hitarthsheth07]

Hey there,

I am new to the codebase and trying to solve this issue just for learning and would greatly appreciate some help. Here's what I am trying to do...

The popup message will show "Can only book no_of_days in advance" (see screenshot below)

The problem:

I cannot get the no of days the user has configured in the "Limit future Bookings".

I am declaring a new variable "advanceBookingDays" to store the no of days user has set in Limit future bookings but it is always 'null'. Whereas the const "isBookingInPast" works perfectly fine.

Feel free to ask for some context and code files...

[v-a14]

Hello @PeerRich Can I take this issue ?

[PaulZeliq]

May I be assigned to this?

[eklavya172004]

I also want to work on the issue I got what are you trying to fix if you assign me this issue I would like to solve this