Individual custom availability for team Meetings links for international teams
The team calendar should allow every member to customized their available time slots. In another words have the option for default availbility to overwrite customized availbility.
This is because if i am looking to implement a 24 hours meeting link (i.e Customized availability is set to all day). If one of my colleagues are seated in the States while I am seated in Singapore, their 12pm is my 12am.
However due to the customized availability overwriting the default availability ---> if my colleague is not available at 12pm and I did not block off myself at 12am in my Google calendar, it will identify me as available and have the option available for selection in my meeting link. This resulted in me having to block off every day when I am off work in my google calendar and it becomes really cluttered.
It will be helpful if we have a feature to block off the timing that we are off work.
Sharing an update, as we are still actively reviewing this idea, and exploring potential solutions.
We are exploring solutions that would likely address this issue, and the idea for 'User specific time zones' together, as the root problems are very related. We will first look to explore ways to solve more holistically for user time zones, and apply that solution to this case. For example, once there is a central way to pull the timezone of a user, we can then apply that timezone to shared availability in a number of ways. We are hoping to avoid a solution that would introduce a way to 'set' a timezone for users specifically in a Meetings scheduling page, or he Meetings app, and instead "pull" from the user time zones from a more centralized user setting.
I hope this context is helpful, we will update here and on the User specific time zones ideas once we have made progress and have a set plan for when this will be prioritized!
We are currently reviewing the ability to set individual times for users of a team meeting link across multiple timezones. I will update here once we have plans in place for a solution.
Adding my vote to this. Is there any movement on this? I have teams based in AU, UK and US who all need to use the meeting scheduler - not to mention just the different timezones in AU or the US.
Sharing an update, as we are still actively reviewing this idea, and exploring potential solutions.
We are exploring solutions that would likely address this issue, and the idea for 'User specific time zones' together, as the root problems are very related. We will first look to explore ways to solve more holistically for user time zones, and apply that solution to this case. For example, once there is a central way to pull the timezone of a user, we can then apply that timezone to shared availability in a number of ways. We are hoping to avoid a solution that would introduce a way to 'set' a timezone for users specifically in a Meetings scheduling page, or he Meetings app, and instead "pull" from the user time zones from a more centralized user setting.
I hope this context is helpful, we will update here and on the User specific time zones ideas once we have made progress and have a set plan for when this will be prioritized!
This is absolutely necessary and missing in HubSpot. In Calendly you can set each availability according to each person and it takes automatically the timezone from the google calendar.
We have a few persons who take over different timezones, but they still need to have different availabilities.
My team could definitely benefit from having this functionality added.
For example, a BDR will be working in a different time zone next week and wants their availability to reflect this now without impacting the ability to schedule meetings in the current time zone this week.
As shown in the screenshot below, there is currently no way to accomplish this. Users are limited to a generic ongoing schedule. In a new era where workers are increasingly mobile and move between time zones more frequently, HubSpot needs to be more open to supporting greater flexibility in their availability window options for scheduling meetings.
@AGagnon - sorry to say, but I suggest you start moving now. HubSpot has not done a single thing in this very basic area about being in a World with more than one time-zone for 5+ years.
So don't hold your breath, but use it to get an alternative solution up running.
Round Robin Calendar is completely unworkable if you have round-robin participants that are in different time-zones or if you have reps with different hours of availability. This has been a known issue for 5 years and nothing's been improved - doesn't seem like a solution will be forthcoming. So annoying.
Unfortunately, we have to ditch the round-robin meetings on Hubspot and go to Calendly.
Adding my vote to this. This is really the most vital function of a round Robin as it gives customers access to team members across multiple timezones and availability. I see this is ongoing since 2017, do we have any update on a timeline of a resolution on this?
Echoing many of the points that have been made previously on this.
With a team across multiple timezones, this is an extremely important functionality for any round-robin events. Without this functionality, the round-robin events in HubSpot are close to unusable.
Calendly manages this very smoothly through its "Availability" feature.
I also don't think dynamically identifying the timezones will necessarily solve the problem.
For example, one user might work 9-5 Eastern time, while someone else works 8-4 Pacific time. Just setting the timezones to be 9-5 in YOUR timezone won't address this issue at all.
Custom team member is a must have for this kind of tool. In our tests, we had to define team member availability by creating fake events on our personal agendas. This is non sense.
So, we decided to use Calendly in the meantime, hopping Round robin will be improved soon.
PS: Hubspot dev team should consider that some companies use Hubspot for BtoC and not only BtoB. From this point of view, you will see how we struggle with some features as the one we're discussing here 😉
Você deve ser um usuário registrado para adicionar um comentário aqui. Se você já estiver registrado, faça logon. Se você ainda não estiver registrado, registre-se e faça logon.