What a per-minute quote leaves out

A per-minute figure is the easiest thing in this category to compare and one of the hardest to compare correctly, because two vendors quoting the same number can be pricing entirely different work. This is what sits behind ours, stated in the order a buyer actually needs it: what our invoice carries, what it does not, and the questions that make any vendor’s quote comparable to any other.

No figure appears below. Every rate is published on the pricing page, and a number retyped into prose is a number that goes stale somewhere nobody is looking.

What our invoice carries

A Vocapable invoice has a short list of line kinds, and the rate behind each one is published rather than quoted per deal:

• The monthly plan price for your workload class.
• Additional concurrent sessions, at a flat monthly price, in any quantity.
• A per-call-attempt fee, on the outbound plans.
• AI usage per minute on the calls your account places, at the month-to-month rate or the lower committed rate, stepped down by the published volume discount as monthly spend rises.

Inbound answering is priced on a different shape, and the difference is not a discount. A receptionist answers calls rather than placing them, so there is no call attempt to charge a fee against, and the per-minute AI-usage charge applies to the calls an account places rather than the ones it answers. A receptionist invoice is its monthly plan price plus its additional simultaneous connections, and that is the whole of it.

Where the rest of your money stays

• Your carrier minutes stay on your carrier’s bill, at the rates you negotiated. Every production call leaves a Twilio subaccount you own, and your carrier invoices that service to you directly, so there is no carrier line on ours to reconcile.
• Your numbers stay yours. You procure and hold them on your own account, so the caller-ID reputation a year of calling earns is an asset you keep.
• Going live carries no implementation or onboarding charge, on any plan.
• The compliance floor is free on every plan. The controls that have no off state run at no cost, and the local floor stages are excluded from the metered lookups by construction rather than by a billing rule somebody has to remember to apply.

The correction most people get backwards

Here is the subtle part, and it is worth its own section.

Our per-minute rate prices AI usage. It does not price carriage. Those are different goods that happen to be measured in the same unit, and sharing a unit is exactly why the comparison goes wrong.

So a minute on a Vocapable call is metered and it is priced — as AI usage, never as carriage. What is absent from the invoice is the carrier line: the minutes your carrier moved, the number rentals, the surcharges. Those sit on your own carrier bill, at the rates you negotiated, because that account was never ours to hold.

Stated precisely, because the imprecise version is a claim we would have to walk back: a Vocapable invoice carries no carrier line.

That single fact is why one per-minute figure and another are not necessarily the same quantity, and why comparing two of them without first asking which goods each one covers is arithmetic performed on two different units. The mechanics of who holds the account are on the telephony page.

The cost categories to ask any vendor about

The useful version of this section is a list of questions, and every one of them works on us too. Take it into any vendor conversation you are already having.

• Is the carrier leg inside the quoted minute, or billed separately, and by whom? A rate that bundles carriage is not comparable to one that does not, and the gap is not small.
• Whose name is on the carrier account? It decides who holds the registrations, who answers an industry traceback, and who keeps the caller-ID reputation when the software contract ends.
• Who pays for the numbers, monthly, and what happens to them if you leave? A number you do not hold is a switching cost that appears on no quote.
• What does an attempt that nobody answers cost? Unanswered dials are most of the volume in outbound calling, and a per-connected-minute quote says nothing at all about them.
• Is concurrency included, capped, or metered — and what happens at the ceiling? A queue, a refusal and a charge are three very different products.
• Is any compliance work metered per lookup, and can any of it be switched off to save money? A control with a price attached has an off state by definition, and the off state is the thing you are actually buying.
• Is the rate card published, or assembled per deal? Ask what the renewal rate is, in writing, before you sign the first one.
• What is the term, is it cancellable, and what is the refund posture? Ours is month to month, or a committed term that is non-cancellable with all sales final under a signed non-refund waiver — and we would rather you read that here than discover it in an order form.
• What does it cost to get your data out, and in what format? Export should be a resource on an API, not a professional-services engagement.
• What is the implementation or onboarding charge? Ask for it as a number, not as a range.

Why we publish the card at all

Speech recognition, speech synthesis and language-model serving run on infrastructure this company operates rather than on a rented hosted-voice API. That is an unusual choice in this category, and it is the reason the rate card can be published in full instead of assembled per deal. A published card is also the only kind of price a buyer can hold us to later.

So run your own numbers rather than ours: the estimator on the pricing page computes a campaign from the same arithmetic the bill uses, and the terms it prices are in the Master Services Agreement, published on this site.