Texting Compliance
J
Joseph Lamothe
In USA it is required to have opt in records to text people. TCPA SMS Compliance requires a clear and unambiguous opt in to receive text messages. Consent must also be captured for each phone number used, not simply one number that the business owns.
In Go High Level right now there is no way to ensure that a lead has opted in. You could technically text anyone directly or through an automation from any number in your account. This needs to be fixed.
Suggested solution: System has a default opt in message that can be set in settings/phone_number?tab=advanced-settings where the opt out message and sender information messages are already. If a user or workflow sends an SMS to a contact on a number for the first time the message body is automatically replaced with the opt in message. The original message is queued. If the lead replies "Yes" or "Y" then the original message is released and sent. Otherwise it is discarded after a timeout.
This is a very important feature as TCPA law is strict in the USA and it could open clients of our agencies up to significant lawsuits. Please add it quickly!
Log In
C
Clifford Paulick
Yes! Like DND controls specific to SMS. Maybe a Location-wide setting like "enforce strict texting opt-in compliance settings" that would disallow everyone from texting anyone that's DND-disabled, and DND texting is enabled by default. They have to text "START" to opt-in and _unlock_ DND texting.