A good route request says exactly where the traffic goes, what the receiver must see (CLI or sender ID), what kind of traffic it is, how much and how fast you send, and what you want to pay. With those details a supplier can quote the right route in one reply instead of five rounds of questions.
Why the details matter
"Need Nigeria, best rate" can mean a dozen different routes with prices that differ several times over. Without details, a supplier either quotes the cheapest route (which may not accept your traffic) or asks questions and you lose days. A complete request gets a faster, more accurate offer, and avoids a route that is blocked after the first hour of traffic.
Voice route request: the fields
| Field | Example | Why |
|---|---|---|
| Destination and breakout | Mexico mobile, all operators | Prices differ by breakout (see breakouts) |
| CLI type | CLI or Local CLI, non-CLI acceptable | Changes price and answer rate (see CLI vs non-CLI) |
| Traffic type | Call center, predictive dialer | Many routes refuse dialer or short calls (see traffic types) |
| Volume | 500,000 minutes per month | Decides price tier and capacity |
| Channels and CPS | 300 channels, 30 CPS | The route must handle your peak |
| Average call duration | 45 seconds | Affects the useful increment |
| Target rate and increment | 0.012 USD, 1/1 | Shows if a deal is possible |
| Codec | G.729 preferred | Avoids transcoding |
| Payment terms | Prepaid | Speeds up onboarding |
The example values are for illustration only. Use your own numbers.
SMS route request: the fields
- Country and operators: all networks or specific ones.
- Traffic type: OTP, transactional or promotional (see transactional vs promotional).
- Sender ID: alphanumeric or numeric, and whether it is already registered in the destination (see sender ID registration).
- Sample content: one or two typical messages, with links if you use them.
- Volume and TPS: messages per month and the peak per second.
- Encoding: GSM-7 or Unicode, and typical length.
- Connection: SMPP or HTTP API.
- Target price: per message, in a stated currency.
Set a realistic target
A target rate helps, but only if it is in line with the market for the route quality you ask for. A premium Local CLI price will not buy a premium Local CLI route at a non-CLI rate. If you are unsure, give a range, or list several CLI types or route types you can accept so the supplier can offer options at different prices. See what drives VoIP termination prices and how A2P SMS pricing works.
Mistakes that slow a request down
- Asking for "A-Z" when you only send to five countries.
- Leaving out the traffic type, then having the route blocked.
- Not saying whether you can accept non-CLI, so only CLI routes are quoted.
- Missing volume, so the supplier cannot judge whether to prioritise you.
- Sending the same request with different details to many suppliers, then comparing offers that are not comparable.
After the offer arrives, plan a test before moving traffic (see how to test a VoIP route).
The VoIPMatcher request form starts with the essentials: destination, route type, target rate and volume. Keep the other details above ready, so the route fits your traffic from the first call or message. We source the route from our carriers and manage it, and your company data is never shared or sold. Browse the open requests to see how other companies describe their needs, read about VoIP termination and A2P SMS, then request a VoIP route or request an SMS route.
Frequently asked questions
What is a route request in telecom?
A route request is a message from a buyer to a carrier or marketplace describing the voice or SMS route it needs: destination, CLI or sender ID, traffic type, volume, capacity, target price and payment terms. The supplier uses it to pick a route that accepts the traffic and to quote a price for it.
Should I share my target rate?
Yes, if it is realistic for the route quality you need. A target rate tells the supplier quickly whether a deal is possible and which route type to offer. If you are unsure of the market, give a range or list several acceptable CLI or route types, so you receive options at different prices.
Can I request several destinations at once?
Yes, but list each destination with its own details, because CLI type, traffic type, volume and target rate usually differ between countries. Asking for A to Z coverage when you only send to a few countries slows the quote and returns prices you do not need. Put the destinations that carry most of your traffic first.
What happens after I send a route request?
The supplier checks whether it has a route that accepts your traffic and replies with an offer, or with questions if details are missing. If the offer fits, both sides complete onboarding, agree terms and set up the connection. Then run a test with limited volume before moving production traffic to the route.
Need a route?
Send the destination, route type and target rate. We reply with what we can deliver.