The short answer
When, where and how each number was collected. A short record beside each contact is enough and is what any question turns on.
Help centre · Developers
Keeping records of consent for developers
Another messaging integration to maintain. What should I be able to show? When, where and how each number was collected. A short record beside each contact is enough and is what any question turns on.
- Developers
- Keeping records of consent
- Plain English
- Live in 5 minutes
Why developers ask this
Another messaging integration to maintain. It usually surfaces the first time a real list goes out, when codes, alerts and notifications straight from your own code stop being a plan and become a send.
What it changes for you
Get this right and the outcome is one key, one endpoint and statuses pushed back. Get it wrong and the cost shows up quietly, in messages nobody read and money already spent.
Doing it in the platform
The compose screen shows the segment count, the cost and the sender name before anything leaves, so the decision is made before the money moves.
Getting started
Message support on Telegram at @exerioco. The account is usually open in under five minutes. Then you log in, paste your numbers, write the message, pick the sender name and send.
FAQ
What should I be able to show?
When, where and how each number was collected. A short record beside each contact is enough and is what any question turns on.
Is this different for developers?
The mechanics are the same. What changes is the volume and the timing, because developers mostly send codes, alerts and notifications straight from your own code.
How do I get started?
Message support on Telegram at @exerioco. The account is usually open in under five minutes. Then you log in, paste your numbers, write the message, pick the sender name and send.
Related pages
Messaging for developers
Support on Telegram at @exerioco sets you up in under five minutes.