I'm wanting to set up an automation that triggers an SMS confirmation both when a calendar event is added, and when/if it gets updated inside the software by a user. However, I don't want to send the confirmation text every single time the appointment is changed by the user for various scheduling reasons. What would you suggest?
—
The original post in the GoHighLevel Official Facebook group is asking for assistance in setting up an automation that triggers an SMS confirmation when a calendar event is added or updated within the software by a user. However, the poster wants to avoid sending the confirmation text every time the appointment is changed by the user for scheduling reasons.
In GoHighLevel, you can achieve this by utilizing their automation features and conditions. To set up the automation, you can create a workflow that is triggered when a calendar event is added or updated. Within the workflow, you can add conditions to control when the SMS confirmation should be sent.
One possible approach is to use a custom field or tag for the calendar events that have been confirmed already. When a calendar event is added, you can include the condition to check if the event is already confirmed. If it is, then the SMS confirmation won't be sent. If the event is not confirmed, you can proceed with sending the SMS confirmation.
When the calendar event gets updated by a user, you can add a condition to check if the event has already been confirmed. If it has, then the SMS confirmation won't be sent again. If the event has not been confirmed, you can proceed with sending the SMS confirmation.
It's important to be cautious while setting up the conditions to ensure that the SMS confirmation is sent only when necessary. Testing the automation thoroughly before implementing it is advised.
To stay updated on any additional insights or further responses regarding this topic, I encourage you to read the comments below this article or check the source link provided below.
Please note that this response is only based on my expertise on the topic of GoHighLevel CRM software.
Source
I’m relatively new to HighLevel but could you place conditions on the SMS Confirmation Event?
Hey a little confused. But so you only want it to happen the first time? Whether I. The app or otherwise but everytime after to not trigger? Lol did I understand that correctly?
Skyler Chapman what is the first “update event” that the user would do that you want to be notified of?
Example that I think you mean:
1. Appointment is new (unconfirmed) = send SMS to somebody (who?)
2. User assigns to self/confirms = send another SMS to same person or another person?
3. Next change = no action to notify the prior recipient(s).
About right?
Skyler Chapman make sure you’re TCPA compliant with proper opt-in tracking. -No SMS automation unless contact explicitly opt-in
I think you need 2 workflows, one that sends SMS when an appointment is scheduled, and a second that triggers and sends SMS if a change is made. You could either have a wait function before the person could re-enter the change automation, or prohibit them from entering it more than once.
that is totally possible to achieve via APIs, Skyler Chapman, happy to help
A possible solution could be to trigger the SMS confirmation only on the initial creation of the calendar event and on significant time or date changes. This way, you can provide the necessary confirmation without overwhelming users with unnecessary notifications for minor updates. 📅✉️
Separate your workflows or logic path so SMS messages are not sent out when the contact makes appointment changes
I’d break down it into multiple workflows making the things go smooth accordingly.