Earlier quoted context omitted.
This is absolutely a Twilio design flaw. It's an incredibly common use case to forward text messages from one incoming line to another number that is controlled by your company, and it's impossible to tell at the point of receipt (when it's still in Twilio's network) whether it's spam or not before forwarding it on. It's the same exact thing that you might do if you have a support@example.com email address; it probab…
Twilio is a carrier and nothing else by having zero tolerance against outgoing spam they are protecting their own core business. If OP or you in that regard would even glimpse at their ToS instead of just scrolling by when your business depends on it OP would not have made this user error.
Why not open that capability to an API so that somebody who is operating some sort of forwarding service to run spam detection before forwarding?