A One-Page Policy: When Employees Can Order Virtual Numbers and When They Can't
A QA engineer needs a Kazakhstan number to set up a test Telegram account and check the company's bot with it. A marketer registers a demo account for screenshots. Support retraces the steps of a customer who got stuck signing up for a third-party service. Every one of these orders is legitimate. But a couple of months later, the history holds dozens of numbers, and nobody remembers who ordered them or why.
A one-page company policy on virtual numbers helps bring this under control. Below is a template. It starts with the terms of service, because a company policy can't allow more than the service itself allows.
What to carry over from the terms of service
The service is meant only for receiving verification codes. It is not meant for anything that breaks the law or a platform's rules.
Only people aged 18 and over may use the service. An intern under 18 doesn't get access to the company account, not even for testing.
Receiving an SMS doesn't guarantee a successful sign-up with a third-party service. The code can arrive, and the platform can still ask for a different number or reject the profile. In QA bug reports, these are two different results: "code didn't arrive" and "code arrived, but the service didn't let me in."
If the code doesn't arrive before a one-time activation expires, the amount goes back to the internal balance automatically, not to a card or wallet. 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. Once the SMS is received, the service counts as delivered, even if the sign-up fails.
Policy template
- Purpose: receiving verification codes for QA, support, and marketing tasks.
- Allowed:
- test accounts for checking sign-up, login, and account recovery;
- demo accounts for presentations, training, and screenshots;
- testing product integrations with external services that require a verified number;
- retracing the steps where a customer got stuck.
- Not allowed:
- bulk registrations and "just in case" accounts;
- getting around third-party platform rules: limits, bans, country restrictions;
- linking numbers to the main work accounts of the company or its employees;
- personal orders paid from the company balance.
- Order type: a one-time activation by default. A rental for 1, 3, or 7 days, where the service offers one, only for tests that need repeat codes. Those codes are free until the rental ends.
- Approval: the person doing the task submits the request, and the head of that function approves it. Rentals for 3 and 7 days also need sign-off from the budget owner.
- Record keeping: every order goes into a log with the date, number, service, country, term, purpose, and the task key from the tracker.
- Access: two-factor authentication at login. When an employee leaves, we change the password and end sessions on all other devices.
- Audit: once a month, the log is checked against the order history.
Why main accounts are off-limits
An activation currently lasts one hour (the catalog sets it per service), and a rental lasts 7 days at most. After that, the SIM card stays with the supplier, and the number may go to another buyer. If an account with access to ads or customer data is linked to that number, getting back into it depends on someone else's SIM. You can buy an expired number again. But if the SIM has gone offline, all you can do is ask the supplier to bring it back and wait.
The second reason: the SMS physically passes through the supplier's equipment. That's acceptable for test data. It's not acceptable for work email or payment services.
Approvals and audits in practice
A request fits into a single message: service, country, activation or rental, purpose. An order is always placed for a "service + country" pair, and you can see the price and availability for that pair before you pay. The manager approves, and the assignee places the order and adds the number to the log right away. An order that's no longer needed can be canceled before the code arrives, but no sooner than one minute after it was placed.
Run the check from both directions. Take each number from the log, search for it in "Order history," and confirm the service and date. Then go through the history since the last audit and look for orders that aren't in the log. For money, use the balance transaction feed filtered by period.
Reasons to follow up with an employee:
- orders for services the team doesn't work with;
- a series of orders for one service with no task in the tracker;
- a 7-day rental where an activation would have been enough.
One more signal is the share of orders that received a code over the last 7 days, shown in your account dashboard. If it drops sharply, use the history to find out who ordered what and for which service. The account's reputation determines the limit on concurrent orders for the whole team.
When you approve the document, add a link to the terms of service on sim-aggregator.com, where the legally binding Russian-language version is published. Schedule the first audit for this month: open "Order history" and search for each number from the log.