What shipped, and when

Fixed. The industry pages under /ai-receptionist printed the additional-AI-minute rate as zero dollars, because the per-minute rate went through a formatter that rounds to whole dollars. They now print the rate the pricing page publishes, and a build check (check-rates) fails the website and the developer docs whenever a page states a zero rate, a figure that is not on the rate card, or the retired overage ladder. The developer billing guide, which still carried that retired ladder, now repeats the current rate card.

Changed. The receptionist page, every industry page and every problem page carry the same capability table: what the receptionist handles on the call, what it captures for a person, and what it does not do (no dispatch, no text messages, no calendar writes, no full-call recording, English only, no guaranteed outcome). The receptionist page also explains how a number works (managed, forwarded, your own Twilio, transfers) and what is on the bill, with every figure read from the rate card. The pricing page shows the monthly bill at 100, 250, 500, 1,000 and 2,500 AI minutes on every plan.

Added. Four problem pages under /solutions: missed business calls (with the missed-call calculator), after-hours answering, overflow call answering (with the simultaneous-call limit of each plan) and lead intake and callbacks. Each has an illustrative example call that includes a fallback moment, the limits specific to that problem, and the questions buyers ask. The industry pages gained a safety paragraph and a worked month priced from the rate card.

Adding a concurrent inbound connection now charges a full month at purchase, whatever day of the billing period it falls on, and the connection is not reserved until that charge succeeds.

Why it works that way. A connection is not a feature flag. It is a slot withheld from every other claim on the fleet from the instant it is granted, busy or idle, so granting one ahead of payment gives away the scarce thing the price exists to ration. The charge is a full month rather than a fraction for the same reason: the reserve itself is not scaled to the days left in the period, so a fraction would price less than the platform actually gave up.

What you are told before you agree. The confirmation step states the exact amount and the exact date your subscription next renews, because a connection bought shortly before a renewal pays its prepaid month and then renews. That is disclosed rather than smoothed away.

Your existing lines are untouched. A connection you already hold keeps the dunning grace it has always had, so a receptionist you already pay for keeps answering while a payment retries. And if a new purchase fails on your own card, your connection count, your billing items and your line’s admission all stay exactly as they were.

Current pricing update, October 11, 2026: this entry describes the legacy BYO, connection-based release. New standalone Receptionist comes in Starter, Business and Scale with included AI minutes and an optional managed-number bundle. Their 2/3/5 simultaneous-AI limits use shared fleet capacity. Existing signed agreements and outbound-attached Receptionist retain their accepted legacy terms; see current pricing before ordering.

Vocapable now answers inbound calls as well as placing them. The original receptionist release runs on your own verified Twilio subaccount and the number you already publish, and is sold on its own or attached to an outbound subscription.

The whole policy engine ships, not a first slice. One answering policy per number, carrying an ordered chain for your open hours and another for everything else, built from the step types you compose: a keypress menu, ringing your own people, the AI agent, voicemail, a spoken message, and a forward to a number you configured. Open hours and holiday dates are yours, in your own timezone. The document is read, written and removed through /v1 under the telephony scope you already hold.

Who it is for. A business that publishes a number and wants it answered in the order it decided on. Only the AI step claims an inbound AI slot; menus, rings, forwards and spoken messages use no conversational AI slot. Legacy inbound entitlements are tracked separately from outbound sessions. Physical inference still uses the available shared fleet, and busy callers follow their configured fallback.

The original connection-based offer. Legacy receptionist-only subscriptions are priced for answering; outbound dialing has its own plan, with an attached legacy Receptionist option. Inbound and outbound admission enforce their separate accepted quantities. When the purchased AI entitlement is busy, the caller advances to the configured fallback. New standalone allowance tiers are a separate offer rather than a repricing of this earlier contract.

The receptionist page carries the shape in full, and pricing carries what it costs.

Run the list you already own. Contacts you purchased, rented, or had appended now call under the Cold Outreach & Data Provenance Waiver you execute, which is the same instrument that admits an artificial-voice voicemail and a call to someone from whom you hold no prior consent.

Who it is for. Accounts whose program is genuinely theirs — their data under their own supplier agreement, their carrier, their targeting, their script. The screen admits a closed list of conditions under the waiver, each rides out on the verdict by name, and electing one without the executed waiver refuses rather than proceeding. Production activation re-verifies the document at the served bytes, so the checkbox on the screening form is an intent to sign and was never an agreement.

What the waiver covers. Contact data you hold under your own supplier agreement: purchased, rented, appended. The bar is provenance you can name, and an applicant who cannot name theirs reaches a human review before anything dials. The four controls enforced in code run on this traffic exactly as they run on every other call, so admitting cold outreach costs you none of the floor you already have.

A signature records who carries responsibility for the program. Whether the call was one you were entitled to place is yours to determine with your own advisors. The Trust Center states the same division, and the waiver itself is published in the legal set so you can read it before you sign it.

The card a buyer can price a campaign against is now a monthly base per plan with included concurrent sessions, a flat add-on for each further session, a per-attempt call fee, and a per-minute rate for AI usage that steps down as total monthly spend grows. Every figure is published on the pricing page rather than quoted on request, and each one is read from the same constants the rating engine bills from.

Who it is for. Anyone comparing us against a vendor whose price is a conversation. Month-to-month and the signed committed term share a base fee and differ only in the per-minute rate; the annual term was retired as a product and its plan ids were deleted rather than repriced, so no subscription can inherit a commercial promise nobody made.

What the per-minute rate prices. It prices the AI session — the GPU, the speech and the language work — and not the carrier leg. That is why a completion on your own Twilio account emits an AI-usage minute exactly as any other completion does, and why a BYO Vocapable invoice carries no carrier line: your own carrier bills the telephony directly, at the rates you negotiated. Telephony ownership is the page that owns that division.

A refusal costs you nothing. An attempt the compliance gate stopped before any dial existed emits no charge at all, so the floor you are protected by never reaches your invoice.

Current phone options. The separately elected managed-number offer now has published rental and carrier prices, but managed numbers are not yet available to purchase or activate. BYO carrier billing remains unchanged.

Keep the screening arrangement you already run, and the pricing you negotiated for it. Before your first production dial you sign one attestation naming that arrangement, its signer and its date. Its reference and its signer are written onto your compliance profile from then on, and each stage that attestation covers rides into every call’s evidence file as a named election carrying the document and the officer behind it. Six months later, when somebody asks who screened this number, the answer is on the call rather than in an email thread.

Who it is for. Every production account. You keep the supplier you already hold, you never pay twice for a lookup you already buy, and your posture is never locked to a vendor somebody else picked for you.

The record cannot be half-built. Every election on your profile carries both a document reference and the officer who signed it. A waiver holding one without the other is rejected the moment the object is built, so it cannot exist in memory, let alone reach a dial, and the database refuses the row from the other end. While your attestation is unsigned, your contacts screen undialable with the missing document named, so the dial waits for the signature instead of going out on an open question.

What a signature gets you. A named owner for the screening behind every call, on the record, dated to the moment the call was placed. Whether the call was one you were entitled to place is yours to determine with your own advisors.

The four controls enforced in code are unchanged by this and run on every call either way. The compliance engine is the page that owns them, and the evidence file is where an election lands.

A developer documentation site: a quickstart, guides for headless mode, authentication and scopes, webhooks, conventions, test mode, and billing and meters, plus a per-operation reference for the whole /v1 surface.

Who it is for. The person deciding whether this gets integrated at all. Every dashboard action is a /v1 call, so the reference is the product rather than an integration surface bolted onto one — the API page makes that argument, and the docs are where you check it.

How it is built, and why that matters. The reference is generated from the same published OpenAPI document the dashboard’s own client is typed against, so every route in it is a route that answers, and it moves the day the API does. The error registry is generated the same way: every problem code the API returns resolves at the exact path its type URI points at.