A pilot week: how your team can test a phone number marketplace before committing to regular purchases
A week of small manual orders will tell you more about a phone number marketplace than any single price list. You'll see which "service + country" pairs deliver a code, where you need a rental, and which pairs you're better off dropping. We don't offer an SLA, and we don't promise that a code will arrive for every order. So when people ask how to test a virtual number service before buying, our answer is simple: run a pilot on your own tasks. Below is a seven-day plan and a small budget.
Day one: a list of pairs and the catalog without signing in
Start with a spreadsheet where each row describes one "service + country" pair. Here's an example. A QA team is testing phone verification in its own app across three markets. It also needs to test signing in to a test account from a new device, where a second code gets sent. Split the pairs into must-haves and nice-to-haves. That decides what you do with a pair that fails the check: look for a replacement or just cross it off.
Then click "View prices" on the landing page. It opens the same order window you get in the dashboard, with real prices and stock. You can browse without signing in, but you need to sign in to buy. For each pair you'll see the price and stock of every supplier. Each one is shown under an approved nickname or anonymously, for example "Supplier #1042". Write down the lowest price, the number of suppliers with stock, and the stock levels themselves. If only one supplier has numbers, or nobody does, the pair goes straight onto the risk list.
Columns you'll use all week:
- pair and order type: activation or rental;
- price and supplier: the cheapest one by default or one you picked manually;
- result: code received, auto-refund, or manual cancellation;
- notes: whether you got a link instead of a code, and whether the target service accepted the code.
Days two through six: small manual orders
Order through the dashboard, one or two numbers per pair per day. Don't build an integration at this stage. First figure out which pairs are worth buying at all. If you don't choose a supplier, the number comes from the cheapest one. If you pick a specific supplier, keep in mind that the price you submitted the order at acts as a ceiling. The order won't go through at a higher price. Test both options on at least one pair.
Each service has its own activation window, currently one hour, and the catalog sets it. While the order is open, the funds are reserved. If the window runs out and no code has arrived, the money goes back to your internal balance automatically. You can cancel an order before the code arrives, but not until one minute after purchase. In the "result" column, keep auto-refunds and manual cancellations separate. An auto-refund means the code didn't arrive in the allotted time. A manual cancellation usually says more about your own process: the tester didn't wait long enough or took a number from the wrong country.
Build three limitations into your conclusions up front. Refunds go only to your dashboard balance. Money isn't sent back to a card or wallet. Once the SMS arrives, the service counts as delivered, and the code itself doesn't guarantee that the target service will accept the registration. We don't show success rates or speed for individual suppliers, so your spreadsheet is the only place those stats will come from.
If you need a repeat code, for example to sign in from a new device or recover access, get a rental for 1, 3, or 7 days. The buttons only show the rental terms the selected service offers. Repeat codes on a rented number are free until the rental ends. When a number expires, you can get it again with the "Buy again" button.
Day seven: numbers from the dashboard
At the end of the week, open your dashboard. It shows the share of orders that got a code over the last 7 days and your concurrent order limit. Both the current limit and how much of it is in use come from the server. The limit depends on your account's reputation. It shows how many orders you'll be able to keep open at once when you start buying for real. Your order history and the balance transaction feed will help you reconcile payments and refunds with your spreadsheet.
How to read the results
Each pair ends up with one of three decisions:
- Activation is enough. The code arrives on time, and you don't need repeat codes. The pair moves into regular purchasing.
- You need a rental. The scenario requires repeat codes, or the number has to stay active longer than the activation window. Work out the budget for 1, 3, and 7 days.
- The pair doesn't fit. There are lots of auto-refunds, few suppliers with stock, or the target service rejects the code. Drop that pair or recheck it later, once availability changes.
Numbers on the marketplace are meant only for tasks that don't break the law or the rules of the platforms where you sign up.
Check your list of pairs with "View prices". After a week of orders, open your dashboard to see the share of orders that got a code over the last 7 days and your current concurrent order limit.