Firstly, our customers specifically have to enable it, and can easily disable if they don't want it.
Secondly, I don't see why the AWS returning 200s while silently discarding our stuff is the right way to handle this. If you want to block our numbers (which I aboslutely think you should be able to do) the API should return something that tells us that instead of pretending like everything is fine.
> If you want to block our numbers...the API should return something that tells us that
As a consumer, I disagree. When I send a message to spam, it doesn't let the spammer know they should switch the e-mail address they're sending from. If I block a phone number, that's not something for the dialer to know.
To be clear, it wasn't consumers that blocked our numbers, it was AWS. I wrote my previous message sloppily.
AWS was sending our messages into the bit bucket and returning 200s. Our customers not only wanted the messages, but were complaining to support that messages were not getting through.
Secondly, I don't see why the AWS returning 200s while silently discarding our stuff is the right way to handle this. If you want to block our numbers (which I aboslutely think you should be able to do) the API should return something that tells us that instead of pretending like everything is fine.