Sandbox or Live Test Account: When an Integration Developer Needs a Real Phone Number
A developer is about to hand off a bot for a client's Telegram channel. The day before the demo, it turns out the buttons under the bot's messages wrap differently on the client's phone than they do in the test environment. You can only reproduce that from a live account, and the one closest at hand is usually the team lead's personal number. Our advice: start with the platform's sandbox, and get a live number only for a specific task. Don't put it on an employee's phone.
Start with the sandbox
Many messengers and bot platforms offer test environments: separate servers, test numbers, and developer service accounts. That's where you debug conversation logic, webhooks, error handling, and rate limits. A test account can be reset and recreated, and a bug in your code won't touch your production account. If you can finish the task in the sandbox, you don't need a live number.
When you can't do without a live account
The sandbox mirrors the API, but it doesn't show everything a regular user sees. You need a live account in three cases.
- Testing on a real client. How the bot's messages look in the mobile app, how notifications arrive, and whether buttons, link previews, and deep links work.
- Regional behavior. A service may treat accounts from different countries differently: default language, available features, number format, extra checks at login. To see what a user in another country sees, you need an account on a number from that country.
- Client demo. A demo on a test server doesn't look convincing, and a developer's personal account shows their own chats and contacts in the interface. A separate demo account solves both problems.
Why not an employee's phone
Most often, the account gets registered to whoever happens to be nearby. Six months later, that person leaves the team, and access to the staging setup leaves with them. Login codes reach them on weekends, work tests get mixed up with personal chats, and the number ends up in logs and in screenshots sent to the client. If you need a test account for bot development for a week or a sprint, set it up on a separate number that belongs to the task, not to a person.
How to set up an account on a rented number
For staging, a number rented for a single service for 1, 3, or 7 days works well. A one-time activation lasts one hour (the catalog sets it per service) and covers one login. With a rental, repeat codes to the same number are free until the term ends. That helps when the staging session drops after you reinstall the app. A rental is tied to one service, so pick the one where the test account will live.
- Open the catalog and choose a "service + country" pair. You can see each supplier's price and stock before you pay, even without signing in. To buy, sign in to your dashboard.
- Choose a rental period. The buttons show only the periods this service offers. If you don't pick a supplier, the number comes from the cheapest one.
- Enter the number when you register with the service, then pick up the code in your dashboard. If the code never arrives, the money goes back to your internal balance automatically when a one-time activation ends. You have to cancel a rental with no code yourself within the first hour after purchase, before any SMS or call arrives: after that it is paid even if the code never arrives. You can also cancel the order before the code arrives, but not until one minute after purchase.
- Right away, set up a password or another login method in the service itself, and save the number in your team's shared credentials vault.
- If the rental has expired and you still need staging, buy the same number again with the "Buy again" button. If the supplier's SIM is offline, you can ask the supplier from the order page to bring it back online.
A verification code doesn't guarantee that the service will accept the registration, since the platform may run its own number checks. Also keep the refund rule in mind: once the SMS arrives, the service counts as delivered, and the order isn't refunded. If the account wasn't created, try a number from another country or go back to the sandbox.
How to stay within platform rules
Keep one live account per task: a client, a region, or a demo. Read the platform's rules on test and secondary accounts. If the platform lets you mark an account as a test or service account, do it. Don't register accounts in bulk, and don't use a rented number to recover a banned account or get around verification. The service isn't meant for anything that breaks the law or platform rules. Keep only test data on staging. SMS messages pass through the supplier's hardware, so don't put real customer data on this kind of account.
Open the catalog, find the service and country you need, compare supplier prices, and take a 7-day rental. Until it ends, repeat login codes for your staging account will arrive free of charge.