Skip to main content

I have an issue with the Round Robin from the backend settings point of view. There used to be a setting that allowed clients to reschedule with the original host, but now all of a sudden it's rescheduling with someone different and it's causing chaos and confusion. I always put the setting at “Keep original host”

 

However, I noticed a few dozen instances where it kept getting scheduled to different team members when the client rescheduled. When I went into the Round Robin settings where I usually find the “reschedule preference”, it’s no longer there! 

 

This is the specific setting I mean (that’s disappeared):

 

What was happening before as of a month ago when everything was working fine:

Client booked a call with Host #1. Client needs to reschedule, and find another time that Host #1 is available and rebooks the call.

 

What’s happening now (once reschedule preference disappeared)

Client booked a call with Host #1. Client needs to reschedule, somehow reschedules with Host #2 or Host #3.

 

Hypothesis: I think that the client is re-entering the round robin somehow and it asks them if they want to pick a specific team member or random round robin - but this wasn’t always the case. 

 

Is there a way to disable giving the Client a choice in rescheduling, and just automatically assign them back to the original Host when they click “reschedule”? This is a terrible user experience from both the client-side and host-side

Hi ​@Hana20003 - Thanks for reaching out - Sorry for the inconvenience that this has caused!

Our Product team is aware of this unexpected behavior and is currently looking into the issue; however we don’t quite have a timeline on when this would be fixed. However, in some cases you can try recreating the Round Robin meeting from scratch, and the option should appear again, but we’re working and getting this option added again to older Shared Event types.

I have this post saved, so I’ll follow up as soon as I have any update for you. 


+1 to ​@Hana20003’s issue — we rely on this setting of preserving the original host and this unexpected behavior has caused downstream issues with other internal workflows. Any additional info you can provide on when this will be fixed will be helpful to us since we’re currently scrambling to fix this in other places.

Can you clarify what you mean by recreating the Round Robin meeting from scratch? How do you ensure you book with the original host with a Round Robin meeting? Thanks!


Hi ​@Claire1239 - Thanks for reaching out about this.

After some more digging into it I understand why recreating the event can be an issue, especially when you’re working with rescheduling clients. I’m working with our teams internally to see what other options we have in the meantime.

I’ll keep this post updated with any changes or anything else I find.


Reply