A support request about a number order that gets handled from the first reply: 5 facts and 3 things you should never send
If you send "the code didn't arrive, refund me" with no order details, we can't find the order. We have to reply with a question first, and the review gets pushed to a second round of messages. Below is a checklist for contacting support about a number order so we can start on it right away. It also lists three things you shouldn't send to anyone, including us.
First, check whether you need to write at all
Some disputed orders get resolved without support. If the time on a one-time activation runs out with no code, the money goes back to your internal balance automatically, and a refund entry shows up in the "Transactions" feed. A rental with no code isn't refunded this way: you have to cancel it yourself within the first hour after purchase, before any SMS or call arrives. The catalog sets the activation window for each service, currently one hour. As long as a timer is running in the "Numbers" feed, the order is active: a code can still arrive, and you can cancel the order yourself, though not until one minute after purchase.
Before you write "the code didn't arrive," open the number in the "Numbers" feed. Some services send a link instead of digits. The dashboard detects it and offers to open it in your browser.
If you rented a number for 1, 3 or 7 days and the supplier's SIM went offline, press "Ask to bring the SIM back." The request goes to the supplier right from the dashboard, so there's no need to contact support.
You should write to us in three cases: the timer ran out, but there's no refund in the "Transactions" feed; the order status in "Order history" doesn't match what you saw in the "Numbers" feed; or the "Transactions" feed shows a payment you can't link to any order.
Five facts that help us find the order right away
Look for an active order in the "Numbers" feed and a completed one in "Order history," which lets you search by phone number.
- Order time and phone number. The date, hour and minute, plus your time zone. Without the time zone, we end up searching the wrong hour.
- Service. Exactly as it's named in the order, plus the type: one-time activation or rental, and for how long.
- Country of the number. Prices and suppliers in the storefront differ for each "service + country" pair, and you may have ordered the same service in two different countries on the same day.
- Status. Word for word, as it appears in the feed or in the history. If you're unsure of the exact wording, attach a screenshot of the order card.
- Your entries in the "Transactions" feed. Filter the feed by date range and find the entries for this order: the payment, and the refund if there was one. If there are no entries at all, or only the payment, tell us that.
Here's an example of a message we can give a real answer to: "One-time activation, Discord, Kazakhstan, number +7 7XX XXX XX 41. Ordered on 24.09 at 14:32 Moscow time. The timer ran out, no code came. In the transaction feed: payment at 14:32, no refund."
A separate case: the code arrived, but the third-party service wouldn't let you go any further. Under the user agreement, the service counts as delivered once the SMS is received, and the code itself doesn't guarantee a successful sign-up on another platform. If the code shows up in your history, say so. Writing "the code didn't arrive" will only drag out the review. Refunds on any order go only to your internal balance, not to the wallet you used to top up your account.
Three things you should never send
"Order history" and the "Transactions" feed give us everything we need for a review. We don't need access to your accounts through any channel.
- Your SimAggregator account password. Not the whole thing, and not part of it "for verification." We find orders by phone number and time.
- Two-factor authentication codes. Together with your password, a code from your authenticator app lets someone sign in to your dashboard and reach your balance.
- Login details for third-party accounts: the username and password for the messenger or email account you registered with the number, plus backup codes and recovery codes. We have no reason to sign in to your account on another service.
If someone in the community chat DMs you claiming to be support and asks for a password or a code, don't reply. If you've already shared them, change your password on the sign-in page and log out of sessions on other devices.
Where to write with which question
- Support Telegram bot: anything about a specific order and your money. A disputed order, a refund that never showed up, a payment in the feed you don't recognize, balance questions.
- Community chat: general questions where other buyers' experience comes in handy. How rentals and repeat codes work, which country to pick a number from for a particular service. Prices and availability are easier to check yourself, since the storefront opens without signing in. Don't post phone numbers, screenshots of your "Transactions" feed or order details in the shared chat. Every member can read it.
- Support email: if Telegram isn't available to you or you need to send a detailed message with attachments. Include the five facts in your email too.
Open "Order history," find the disputed order by phone number, and note the time, service, country and status. Add this order's entries from the "Transactions" feed and send it all in one message to the support Telegram bot.