The short answer
A long unique password, changed if anyone leaves, and API keys stored on the server only. Repeated failed logins lock the address out temporarily.
Help centre
How do I protect the login? A long unique password, changed if anyone leaves, and API keys stored on the server only. Repeated failed logins lock the address out temporarily.
A long unique password, changed if anyone leaves, and API keys stored on the server only. Repeated failed logins lock the address out temporarily.
This comes up most often for account owners. It is one of the questions people ask in the first week and rarely think about again once it is set up.
Everything described here happens on screen while you work: the segment count, the cost, the sender name and the status of every message. Nothing is hidden behind a report you have to request.
Support on Telegram at @exerioco answers in minutes and can look at a specific send with you rather than sending you a help article.
Create your account with email and password. No KYC and no approval queue. Add credits, paste your numbers, choose your sender name and send in under five minutes.
A long unique password, changed if anyone leaves, and API keys stored on the server only. Repeated failed logins lock the address out temporarily.
Yes, a person on Telegram at @exerioco, not a ticket queue.
Create your account with email and password. No KYC and no approval queue. Add credits, paste your numbers, choose your sender name and send in under five minutes.
Message support on Telegram at @exerioco and get a straight answer.