Workflow Trigger when booking on behalf of client via App

Hi ​@Ashley58565 - Thanks for reaching out.

Just to confirm, is this only happening through the mobile app? If you do the same process through the web version do you see the same issue?

Let me know!

Hi ​@David ,

Just checked - this happens through the app and the web interface.

The workflow doesn't trigger and the web interface shows a timeline without the workflow being triggered.

I've tried through both options in the app:

- quick actions (+ at bottom of home screen)

- via contact section 

Should the workflow be triggered? I wonder if Calendly sees a different event when the booking is done by admin/ host, instead of the client facing web interface.

Kind regards,

Ashley

Hi ​@Ashley58565 - Thanks for double checking that.

What kind of Workflow are you using? Is this an email or text workflow? At this time, Text Workflows won’t send if a host books on behalf of the invitee. This is because Text reminders require consent from the user to be sent (Which is filled out when an invitee makes a booking)

Otherwise, Email workflows/Reminders should send normally. If not, I would double check to make sure the workflows are assigned to all of your events as well.

Let me know!

Hi ​@David ,

Thanks for confirming that it's a consent issue.

So am I correct in now thinking that the phone number for a contact is never used to send text messages?

I was hoping I could use the contacts feature to schedule on behalf of clients, but looks like I need to use the web interface and manually enter invitee details each time if I want the text message to be sent.

Will the text message feature, in future offer a consent override? I.e. I have consent from clients to send text messages, and they can also opt out if they wanted, so why can I not do this on their behalf from within the account/ app?

Kind regards,

Ashley 

Hi ​@Ashley58565 - Thanks for reaching back out!

Yes you are correct, the contact phone number is not used to automatically send text messages - However this is something we’re looking into adding in the future, but at this time our carrier requires consent to be given from the user. This is to help prevent spam attacks to users who might give their phone number to the wrong person.

But yes, our team is looking into making this process more efficient so users won’t need to provide consent each time - I’ll pass this along as feedback to them! As soon as I hear anything, we’ll update the community. :) 

Thank you for your help ​@David  it is very much appreciated 🙏