Same -- it is a good work around, but ideally it would be nice to not have to do this in every workflow. And it won't always work, because depending on which the user is assigned "based on the appointment", I need to make sure that the correct user is "reassigned to it" after the webhook is fired. GHL you can't map specific users, only select a user, which makes me have to use a bunch of if/else logic to predetermine the assigned user then remove, then re-add.

Has this been updated? @Ross Christifulli

@Ross Christifulli - Any follow up on this?

Lol, makes sense! So the Function Calling launches tomorrow or just the appointment booking updates? @Ross Christifulli

@Russ Ward -- Great stuff! I'm trying to do something similar, but it seems like the Webhook is the same exact webhook when creating bots for the same location. Is the only way to get a different webhook is to connect it to a different GHL Location? @Ross Christifulli -- Maybe we can get this updated that a new webhook is setup based on the unique Assistant ID? I have a client, that has only one sub-account (not agency admin so I can't create more sub-accounts for them) but we have a few different assistants that we want to use depending on lead source and outcome. I set up two different bots, but it gave me the same exact webhook.

@Russ Ward - Ah, you're right. I'm so use to just checking the end of URL to see if they are different.