Free tool · Data & IoT
RFQ checklist: data, SMS & China quotes
Pick the lines you are buying, work through the fields that decide a comparable quote, and send the answers as an RFQ.
Pick the lines you are buying, then work through the fields that make a quote comparable.
0 of 36 checked
The print view leaves out the site navigation. Choose Save as PDF in the print dialog.
This browser cannot save your answers. They stay on the page until you leave.
Requirements and scope
-
Why it mattersThe use case decides which product model and route fit.
What a good answer looks likeOne paragraph: the application, who uses it, the traffic or data type, and what a good outcome looks like.
-
Why it mattersA quote is scoped per site and per endpoint, not per company.
What a good answer looks likeA short table with each site or system, its country and city, and its role at each end.
-
Why it mattersLead time depends on access, registration and testing, not only on the order.
What a good answer looks likeA target date, whether it is fixed or a preference, and the first step you need.
-
Why it mattersIt sets the contract and onboarding path.
What a good answer looks likeCPaaS, eSIM brand, MVNO, IoT maker, enterprise, carrier or reseller, in one line, with the main markets.
Volumes and growth
-
Why it mattersMessages, data, devices and bandwidth are sized in different units.
What a good answer looks likeOne figure per product: messages, terabytes, active devices or Gbps.
-
Why it mattersCapacity is sized for the busy hour, and an average hides it.
What a good answer looks likeThe peak rate and when it happens, plus how you measured it.
-
Why it mattersGrowth changes the headroom the design needs.
What a good answer looks likeA percentage or range, the assumption behind it, and any launch dates.
Coverage and destinations
-
Why it mattersCoverage and rules are per country, and a partial list returns a partial quote.
What a good answer looks likeCountry names or ISO codes, split into launch markets and later phases.
-
Why it mattersThe handoff and the testing differ, and so does the route you can compare.
What a good answer looks likeA per-country answer: direct, off-net, or not available, with the handoff named.
-
Why it mattersA local profile, a roaming profile and multi-IMSI fit different movement patterns.
What a good answer looks likeA country list per fleet segment, with the expected time in each country.
-
Why it mattersA China circuit is quoted between two named locations, not between two countries.
What a good answer looks likeCity A to city B, the China landing city, and the hosting or last-mile address at each end.
-
Why it mattersTwo paths that share a segment fail together.
What a good answer looks likeThe route options, the segments each one shares, and how diversity is verified.
Technical
-
Why it mattersConsumer devices and IoT devices use different provisioning paths.
What a good answer looks likeThe standard, the device types, and who manages the profile lifecycle.
-
Why it mattersQR code, one-tap and push-to-unit need different platform work.
What a good answer looks likeThe flow, the trigger, and which side runs each step.
-
Why it mattersA private APN, fixed addresses and IPsec are design choices, not add-ons.
What a good answer looks likeAPN model, IPv4 or IPv6, fixed or dynamic addresses, and the sites that connect.
-
Why it mattersBand support decides which networks a device can use.
What a good answer looks likeLTE and 5G bands, the module model, and any certification already held.
-
Why it mattersA data-only profile has no voice, SMS or VoIP capability.
What a good answer looks likeYes or no per fleet, the fallback channel, and any exception you need.
-
Why it mattersThe protocol sets the integration work and the delivery-report model.
What a good answer looks likeProtocol and version, bind model, redundancy, and whether you need a test endpoint.
-
Why it mattersLong numbers, short codes and alphanumeric senders follow different registration paths.
What a good answer looks likeA per-country table: sender type, what you already hold, and what is still to register.
-
Why it mattersThe mix and the content decide the route and the review.
What a good answer looks likeApproximate shares for OTP, transactional and opt-in marketing, plus two or three sample messages.
-
Why it mattersThroughput and volume are different numbers, and reconciliation needs per-message receipts.
What a good answer looks likeMessages per second at the busy hour, bind count, delivery-report format and export method.
-
Why it mattersUnder 1, 1 to 10 and over 10 Gbps change the access and the equipment at each end.
What a good answer looks likeBandwidth per site, fixed or burstable, and the physical handoff.
-
Why it mattersIP transit, premium China routing, DIA, SD-WAN and private lines are different products.
What a good answer looks likeFor each option: the path, the handoff, and what is included at each end.
-
Why it mattersA target without a measurement method cannot be compared.
What a good answer looks likeRound-trip target, the two measurement points, the test method, and when you will test.
Compliance and KYC
-
Why it mattersVerification is part of onboarding, not a step after the quote.
What a good answer looks likeRegistration number, registered address, and the documents your legal team can share.
-
Why it mattersA named contact keeps the review from stalling.
What a good answer looks likeName, role, work email and time zone, with a backup.
-
Why it mattersIt supports company verification and the route decision.
What a good answer looks likeWho sends or connects, to whom, why, and what content or data moves.
-
Why it mattersA route can be ready while the sender or template is not.
What a good answer looks likePer country: sender, template status, owner and reference number, or the plan to register.
-
Why it mattersA data-only declaration changes the registration path in some markets.
What a good answer looks likeYes or no per fleet, with any voice or SMS exception named.
-
Why it mattersHosting changes the filing path and the access design.
What a good answer looks likeYes or no, the city, and whether a filing is held or still needed.
Commercial terms to ask about
-
Why it mattersMessages, sessions, terabytes, Mbps and ports are invoiced differently.
What a good answer looks likeThe unit, the rounding rule, the measurement window, and what is excluded.
-
Why it mattersA minimum changes what a small first order can look like.
What a good answer looks likeMinimum quantity, minimum term, and how a ramp is handled.
-
Why it mattersA test is the only way to compare delivery or latency before you buy.
What a good answer looks likeWhat the test includes, how long it runs, what results you receive, and who supports it.
-
Why it mattersThe terms decide how fast you can add a destination or a site.
What a good answer looks likeInitial term, renewal, notice period, and how additions or upgrades are handled.
-
Why it mattersA named escalation path and consistent numbers matter more than a general statement.
What a good answer looks likeHow a case is opened, who owns the escalation, the report fields, frequency and export format.
-
Why it mattersNumber porting, profile migration and address return take planning.
What a good answer looks likeNotice period, porting or migration support, and what is handed back.
Editable templates
Download the template for your line, fill it in offline, then copy the answers into the form.
- Wholesale data & eSIM Spreadsheet (.csv) Plain text (.md)
- IoT & device fleets Spreadsheet (.csv) Plain text (.md)
- A2P SMS Spreadsheet (.csv) Plain text (.md)
- IP transit & China connectivity Spreadsheet (.csv) Plain text (.md)
How this works and its limits
Runs in your browser: what you enter stays on your device and is never uploaded.
Each item comes from a field our RFQ form uses, or from a route term our cable and latency tools use. Pick one or more product lines at the top; the list hides fields that do not apply to them.
Checks and answers stay in this browser. Nothing is sent while you work. When you choose Send this as an RFQ, the checked items and answers travel in the link to the RFQ form; the form stores the inquiry only when you submit it.
The print view leaves out the site navigation, so you can save a PDF. The editable spreadsheet and plain-text templates carry the same fields for offline work.
No prices are shown. The quote states what is offered, for which destinations and volumes. Compliance items are planning prompts, not legal advice; registration and filing rules are confirmed per market.
Data sources and licences
Operator names, brands and codes shown here are public reference data compiled from national regulators and other public sources. Their appearance does not indicate any partnership, endorsement, agreement or connectivity between unicomam.com and the named operators. All trademarks belong to their owners. Data is provided “as is” with no warranty; verify against the official source before relying on it for routing, billing or compliance decisions.
Regulatory information is for reference only and is not legal advice; check the regulator link and the “last verified” date.
What makes an RFQ quotable
A quote comes back faster when the request answers the questions the provider would ask next. Those questions are predictable: what the service carries, how much of it, where, over which protocol or handoff, with which registrations, and on what commercial terms.
The checklist groups them in the order a provider reads them. Scope and volume decide the model. Coverage and technical fields decide the route and the integration work. Compliance documents decide whether onboarding can start. Commercial questions decide what you can compare.
Two failures cause avoidable delay. The first is a request that names a product but no destinations or volumes, so the reply can only be a question. The second mixes products in one paragraph, so each line has to be separated before it can be sized. The checklist keeps the lines apart and asks for one set of answers per line.
A good answer is specific enough that two providers would quote the same scope. "Data for Latin America" is not specific. "Ten thousand active devices in Mexico and Brazil, 2 TB a month, local profiles, private APN, growth of 20 percent in the first year" is.
The same rule applies to messaging and China connectivity. For SMS, name the sender types, the traffic mix and the peak throughput. For China, name both ends, the bandwidth tier, the handoff and a latency target with a measurement method.
Use the checklist as a working document. Check an item when you have the answer, write a short answer where you have one, and send the result as an RFQ. The provider can then quote the same scope you described, and you can compare replies line by line.