Short answer: across voice, SMS, and AI agent infrastructure, pricing transparency splits into three shapes — a published per-destination rate card you can compute against before signup, a quote-only model where pricing arrives after a sales cycle, and a platform-reported pass-through where the upstream carrier or model cost is shown with the markup separated — and the shape a vendor picks decides how much of next month's bill is knowable today. Orbit by Devotel publishes the full rate card on one pricing page: $0.014 per voice minute, $0.0075 per SMS segment, $0.01 per RCS message, $0.001 per email, WhatsApp passing through Meta's own fees at zero platform markup, and the AI agent layer usage-billed with no per-seat license — one pricing posture across all three infrastructures, not three different ones. This guide compares the three transparency shapes on six scored rows, prices the quote cycle itself, and builds the normalized per-channel benchmark stack a buyer can verify without talking to anyone's sales team.
We publish with ourselves in the comparison, disclosed rather than hidden. Every figure below is a public page figure a buyer can check against the pricing page before any call happens.
1. The three transparency shapes
Pricing opacity is not a single posture; it shows up as three different shapes, and a buyer scoring vendors treats each as its own row.
Published per-destination rate cards. The vendor lists per-minute and per-destination voice rates and per-segment SMS rates on a public page, and the buyer can compute the bill before signup. Twilio's published per-country tables are the best-known CPaaS instance of this shape; Orbit's pricing page is the consolidated-platform instance. The property that matters: a finance team can model next quarter's spend tonight, at volume, without a meeting.
Quote-only models. Pricing arrives after a sales cycle — a discovery call, a rate negotiation, sometimes a proof-of-concept before numbers appear. Sinch and Infobip are the category names most associated with this posture; many enterprise UCaaS vendors sit here as well. Negotiated pricing is not inherently wrong: an enterprise with genuine leverage sometimes beats the public table. The property that matters is the one the quote-only shape fails: the bill cannot be modeled before the cycle closes, which is where most evaluations stall.
Platform-reported pass-through. The vendor shows the upstream cost — the carrier fee, the model-token cost — and its own markup as separate lines. Zero-markup WhatsApp, where Meta's per-message fees pass through at cost, is the canonical instance: the buyer sees exactly what the platform adds on top of the upstream price. This shape is the strongest form of transparency, because it separates the commodity underneath from the platform's value-add.
A vendor can run different shapes per channel — published SMS rates while the AI agent layer is quote-gated, or published voice while the pilot pricing is "contact sales." The correct unit of comparison is the full stack a workload actually runs: voice plus SMS plus the agent layer, scored on the same six rows.
2. Scoring the three shapes on six rows
Six rows separate a transparent pricing posture from an opaque one. A buyer can verify every row from public pages before any sales call.
- Published rate card. The per-destination tables are on a public page, in a currency the buyer uses, tonight.
- Markup-named pass-through. Where an upstream fee exists (carrier, Meta, a model provider), that fee and the platform's markup are shown as separate numbers.
- Billing-unit honesty. The billing units are named in public — per-minute versus per-second, per-segment versus per-message — and partial units do not round up silently.
- Idle cost. The pricing page states what an idle month costs. Usage-based with no floor costs $0 at zero traffic; a hidden platform minimum fails this row.
- Self-serve simulation. A calculator or published worked example prices a realistic traffic mix without signup. Orbit's /compare/pricing-overview hub runs this math in public; quote-only vendors cannot.
- One pricing posture across the stack. The same transparency shape covers voice, SMS, and the AI agent layer. A stack where two channels are published and the third is quote-gated inherits the weaker posture.
| Shape | Published rate card | Pass-through reported | Billing-unit honesty | Idle = $0 | Self-serve simulate | One posture across stack |
|---|---|---|---|---|---|---|
| Published rate card | Yes | Sometimes | Yes | Depends on model | Yes | Sometimes |
| Quote-only | No | No | Varies by contract | No | No | No |
| Pass-through reported | Yes | Yes | Yes | Yes (usage-based) | Yes | Yes (Orbit) |
No shape wins every row unconditionally — a flat-rate subscription can be published and still fail idle-equals-zero. The scorecard is a screen, not a verdict; it filters out postures where next month's bill cannot be modeled from public information.
3. What the quote cycle itself costs
Pricing opacity is not free. A five-business-day procurement cycle — discovery call, solution review, negotiated rate, redlines — is five days the workload does not ship. For a program sending 50,000 SMS segments a month at the published $0.0075 per segment, five days of industry-median cart-recovery throughput (roughly a 3% conversion lift on recovered carts, on a $80 average order) is worth more than any negotiated discount of the same order. That math rarely appears in a pricing comparison, because the comparison page treats the cycle as free.
The second cost is softer but real: pricing that cannot be modeled before launch is pricing that gets discovered in production. A team that sizes an AI agent layer in a pilot with unknown per-turn pricing finds the true monthly figure after the traffic scales, which is the least reversible moment to learn it. Published rates convert that risk into arithmetic done before the first API key.
4. A normalized-priced benchmark stack, per channel
Comparison pages hide behind channel-level percentages because channel price units differ. The normalized stack expresses every channel as cost per 1,000 units of traffic, using the rates published on the pricing page: $14 per 1,000 voice minutes, $7.50 per 1,000 SMS segments, $1 per 1,000 emails. At those figures, five days of pre-launch modeling for any traffic mix is a spreadsheet exercise, not a negotiation.
The all-in voice agent minute is the one number most pricing pages refuse to show. A self-assembled stack prices it as: the telephony leg, plus the speech-to-text leg, plus the LLM tokens per turn, plus the text-to-speech leg — usually four vendors, four bills, and four surfaces where a rounding or markup change can move the total. A consolidated platform prices the agent's call minutes against the same published voice-minute rate card as any other call, with the agent layer itself usage-billed and no per-seat license to normalize away. The AI voice agent pricing breakdown and the AI voice agent TCO model run the component arithmetic in full.
Transparency compounds here in a second way: one wallet, one pricing page, one posture means every channel's spend is explainable from the same public table. The CPaaS pricing models post prices the usage-based shape against flat-rate and revenue-share in TCO terms; this guide concerns the transparency shape a pricing posture wears, not the billing model itself.
5. The decision table
| Buyer's constraint | The transparency shape that fits | Why |
|---|---|---|
| Model next quarter's spend tonight, no sales call | Published rate card | Public per-destination tables are the only shape finance can compute from |
| Genuine enterprise leverage, volume to negotiate | Quote-only can win | A negotiated rate sometimes beats the public table — the screen only fails if you cannot model before the cycle closes |
| Pass-through channels with markup named | Platform-reported pass-through | The commodities (Meta, carrier, model tokens) show as cost-plus, separated from the platform's value-add |
| One consolidated bill across voice, SMS, and AI agents | One pricing posture across the stack | Mixed postures inherit the weakest one; consolidation only pays when the whole triangle is on one posture |
| Compare billing models in public math | Self-serve pricing simulation | The pricing-overview hub prices per-seat, per-product, and usage-based models side by side |
A buyer already midway through a quote cycle does not have to abandon it — two postures can be compared against the same traffic model. But a buyer who has not started should screen on the six rows first; the best Twilio alternatives guide scores the vendor field and the UK sibling guide screens the published-rates row per candidate.
Frequently asked questions
What does "transparent pricing" mean in communications infrastructure?
Transparent pricing is pricing a buyer can model before signup: per-destination rate tables published on a public page, billing units named (per-minute versus per-second, per-segment versus per-message), and idle-month cost stated. A "contact sales" posture fails the screen regardless of how competitive the eventual negotiated rate turns out.
How do pass-through markups report pricing?
Pass-through pricing separates the upstream cost — a carrier fee, Meta's per-message charge, a model provider's token cost — from the platform's own markup, and shows both lines. Orbit's pricing lists WhatsApp at Meta's rates with zero platform markup, which is the strongest form a pass-through posture takes.
Why does the consolidated one-posture point matter?
A stack that runs voice and SMS on published rates but gates the AI agent layer behind a sales cycle inherits the weakest posture — the agent traffic eventually dominates, and its pricing stays unmodelable. One pricing posture across the whole triangle keeps every channel computable from the same public page.
Can a quote-only vendor still be the right pick?
Yes, for an enterprise with enough volume and procurement leverage to beat the public table. The screen answers a different question: whether the bill can be modeled before the cycle closes. A team that negotiates from published comparators knows where the anchor sits; a team evaluating quote-only alone does not.
How do I price an AI agent layer before committing?
Reason in per-channel units: voice minutes at a published per-minute rate, message segments at a published per-segment rate, and agent turns usage-billed with no per-seat license. The all-in voice agent minute post runs the component math, and the AI agent billing docs show the usage terms. If any layer prices only after a pilot, size the pilot conservatively — pricing learned after scale is pricing learned at the least reversible moment.
Why does pricing opacity persist if buyers screen for it?
Some of it is genuine enterprise posture; some is page-level SEO that replaces a published table with a sales funnel. A buyer who screens on the six rows above filters both at once, which is why the screen is the first step, not the last comparison.