Your messaging provider asked you to prove three numbers opted in
Someone reported your texts as unwanted. Now your provider needs to show the carrier those people agreed. Here is one way that week can go, and another.
An illustration, not legal advice. The messages are ours, not any provider’s, and nobody in them is real. What a provider can ask for and do is drawn from published policies and industry guidance, listed at the end.
Nobody in this story is the bad guy. The provider has to answer to the carrier. The carrier answers to people who are tired of texts they never asked for. Those texts come from marketers who will message anyone, at any cost, and they are the reason everyone else now has to show their work. You, your provider and the carrier are on the same side, and all of you need the same small thing: an answer about three phone numbers.
Have you been here?
Same Monday, same notice. This time every signup, every YES and every STOP was recorded as it happened, with the exact words the person saw. You look up the three numbers and export each one's history: when they signed up, what the form said that day, their YES, and no STOP since. You reply before lunch with three files instead of three days of digging.
What this can and can't do. It works for opt-ins recorded from the day you start. It can't rebuild what was never written down, it doesn't see your sign-up form, and nobody can promise your provider will accept an answer. What it changes is how fast you can give one.
Asked about people who signed up before you used Redoubt Vault? Send that history in as imported, with the name of the person who vouches for it. Your packet shows it for what it is: your records, given to us now, not something we saw happen. From then on, every new signup is recorded as it happens.
Keep a record of every opt-in from now on
Or read the API reference first. Pricing is on one page.
What this is based on
- a provider's published messaging policy: on written request, “you must provide proof of a recipient’s consent and the date and the method through which that consent was obtained.”
- a provider's US messaging best practices: carrier complaint notices include the “destination phone number, timestamp, and original message ID”, and a number “may have its sending rights suspended while opt-in is being confirmed.”
- CTIA's Short Code Monitoring Handbook: audit notices “provide the stipulated timeframe for such written response”, and if there is no response “CTIA may temporarily suspend the short code”.
- CTIA's Messaging Principles and Best Practices: the records a sender should keep, from the “Timestamp of consent acquisition” to the “Capture of experience (e.g., language and action) used to secure consent”.
Other stories
- One customer's texts drew complaints, and your platform is asked for proof of opt-in
- An escalated complaint: your email provider asks how you got an address
- All of them, and why this happens
Last checked against the sources below: 5 October 2026. Redoubt Vault is not affiliated with any messaging or email provider, or with CTIA.