I just talked to Greg, he said something that might help would be to add "FWD: " before the forwarded message. Or possibly "Forwarded from XXX.XXX.XXXX: "
I can confirm that my system did forward the message without any modifications at all. (my employee knew what it was because he knows all text messages from that number are forwards)
This sounds like a highly problematic solution. If twilio actually greenlights spam that starts with "Forwarded from XXX.XXX.XXXX:" as Greg suggests, you can be sure actual spammers reading this thread will catch on and start sending spam texts with a header intro like that, probably by EOD today.
I think one of the key contexts here is being forgotten:
These are all internal messages. Someone cannot use our system to text random people. It's literally one person seeing them. We're a local service company. We're not SAAS or something like that. It's just people messaging us "Hey can you guys come Thursday?"
This would be like if you signed up for a VOIP provider for your business phones and they suspended your account because someone sent you a phishing text message.
With due respect, you are the one ignoring key context:
From the employee's carrier perspective those are external messages originating from you.
All that Verizon/T-Mobile/at&t see is spam coming from you, they don't know about the employer/employee relation. So when those carries complain to your carrier, your carrier has little options but to lock you.
