@bt-chris.brown I am not sure this is what you are saying, but one thing I feel I should point out is based on my own misunderstanding early on.
TCR applies to all communications between a business and consumer. TCR does not disambiguate between 1-on-1 communications between a business representative and a customer. So if you and I are corresponding with one another via SMS, me from my RingCentral phone number and you as one of its customers, if you text STOP to me, I am obligated not to text you again -- even if we are talking about what we both did last summer. You know? I thought I would share, because again, I thought TCR governed how I use SMS to market to you or sell to you. But it governs more than that.
Let me take a step back and look at your request fresh. You are not talking about an auto-reply to a request to STOP, START, etc. You are looking for a way to inform the people you correspond with of their ability to unsubscribe if they want to. I think that is correct, but let me know if I got that wrong - otherwise, the rest of my advice below is likely to be wrong. :-/
Ok. So I see two ways to solve this problem: one is through the use of SMS templates. SMS templates allow you to write and share a message across your organization that you can easily insert into a text you intend to send to someone. This would not be automated, but would at least let you create a consistent message that could be sent to the people you correspond with. The downside being that it is not automated, and your employees would need to be trained to send this disclosure reliably. Ug.
Ideally we could automate this message using Workflow Builder. We don’t have a trigger for SMS sent - that seems like the ideal trigger. The workflow would work like this:
- At a frequency of once per month or even once per year, when you send an SMS to someone, the workflow would be triggered and send a second SMS shortly thereafter saying, “FYI - you are corresponding with INSERT NAME from COMPANY NAME. If you would like to no longer receive messages from them, you may send ‘STOP’ at any time.” The workflow would periodically send this disclosure based on the workflow’s frequency settings - in this way it would also work to remind users of their rights on a recurring basis. In this scenario, the following would be possible:
- Byrne: “Hey Chris, I wanted to follow up regarding our phone call.”
- Workflow Builder to Chris: “Disclaimer: you are corresponding with Byrne Reese from RingCentral. If you would like to no longer receive messages from Byrne, you may send ‘STOP’ at any time.”
- Chris: “Oh hey Byrne. No problem. It was great speaking with you.”
- Byrne: “Likewise. Let’s schedule a meeting to chat...”
- Alternatively, you could bind the same logic to the “SMS received” trigger. So the interaction would be slightly different, but it would still work to achieve the same results. In this mode though the following interaction would be more common.
- Byrne: “Hey Chris, I wanted to follow up regarding our phone call.”
- Chris: “Oh hey Byrne. No problem. It was great speaking with you.”
- Workflow Builder to Chris: “Disclaimer: you are corresponding with Byrne Reese from RingCentral. If you would like to no longer receive messages from Byrne, you may send ‘STOP’ at any time.”
- Byrne: “Likewise. Let’s schedule a meeting to chat...”
You can see the only difference between the two would be the order in which the messages are sent. What do you think of these ideas?