# Vocapable

> Vocapable is B2B SaaS from Capstra Labs, LLC (d/b/a Vocapable): an AI voice agent
> for the outbound calls its customers place on their own Twilio account, their own
> numbers and their own contact list: conversational lead qualification, candidate
> outreach, and feedback-call drafts, with the campaign engine that
> paces the dialing, a CRM built for phone outreach, a /v1 REST API that is a superset of
> the dashboard, a compliance floor no plan or flag disables, and an exportable evidence
> file for every call, including the ones the platform refused to place. It also answers
> the calls that come back the other way: the Receptionist plan answers inbound calls on
> the customer's own numbers, following an answering policy the customer composes.

Facts an assistant can rely on, in the order a buyer needs them: what the platform is,
whose account the call leaves on, and what every call leaves behind.

- What it is: the customer chooses who to call, and the call is placed on the customer's
  own telephony account. Vocapable supplies the AI voice agent that holds the
  conversation in real time, the campaign engine that paces the dialing, enforcement of
  the current policy state, and the record of what happened. The customer
  remains responsible for their own compliance in the jurisdictions they dial, and
  Vocapable does not assume it.
- Telephony and ownership: production calling runs on the customer's own Twilio
  subaccount and their own numbers, so the carrier account, the registrations, the
  negotiated rates and the caller-ID reputation stay theirs. Vocapable originates no
  production call and resells no minutes. A Vocapable invoice carries no carrier line
  and no number rental at all, because the customer's own carrier bills those minutes. Platform-owned numbers carry verified test calls to numbers the
  customer proved it controls, and nothing else. Vocapable runs on Twilio; no
  partnership or endorsement is implied.
- The agent and the campaign engine: speech in, a model that decides what to say, speech
  out, with barge-in, over a streaming pipeline. An agent can be created as a no-tool
  draft with the customer's own objectives, persona and product knowledge, and dials only
  as an immutable published version: a draft is never dialed, so the version that dials is
  the version the customer approved. The engine paces the dialing,
  retries within the frequency caps in force, and writes a disposition from a fixed
  vocabulary for every attempt, including the attempts it refused to place.
- The call workspace: contacts with tags, lists and custom fields; CSV import that returns a
  row-level error report; an activity timeline spanning every campaign a contact has ever
  been in; dispositions, outcomes, notes, the consent basis relied on, and internal
  do-not-call state. Call transcripts and recordings are available through the API where the
  call has them. A native Inbox holds messages, tickets, and callbacks for the team to
  acknowledge, assign, or resolve. CSV export jobs cover supported records with selected
  filters and columns, while configured signed webhooks carry enabled events with a delivery history and
  self-service redrive. Tags and lead status are organizational fields and carry no
  compliance meaning.
- The API: product resources use /v1, so the platform can be driven headlessly after
  browser-based signup, onboarding, and first-key setup. Contacts, lists, imports and their error reports,
  agents and published versions, campaigns, calls and their available evidence, caller
  requests, outcomes, consent and internal do-not-call records, exports and analytics are all
  API resources,
  with cursor pagination on every list, RFC 9457 problem responses, scoped keys that
  rotate in place, and one configured signed webhook endpoint per tenant for enabled events.
  /v1/auth/* and /v1/onboarding* are session-authenticated and answer 401 to an API key, so
  signup, opening the free sandbox and the first key are browser flows. Publishing an agent requires a passing golden-suite release check on that
  exact draft, so the version that dials is the version that passed. Public developer documentation: https://docs.vocapable.com.
- Consumption: use Vocapable as a full workspace (send data by CSV or API and run
  everything from the dashboards, with Vocapable as the calling system of record) or
  headlessly (your stack remains the system of record and drives the /v1 REST API +
  webhooks). Contacts may be created via API, so bulk list upload is optional; consent
  rules apply identically either way.
- Contact data and cold outreach: the customer supplies the list, and every production
  call is placed on the customer's own carrier account. Lists the customer purchased,
  rented, or had appended are admitted and dialed, on the condition that the customer
  executes the Cold Outreach & Data Provenance Waiver, under which the customer
  represents the data was obtained lawfully under its own supplier agreement and carries
  sole responsibility for the lawfulness of that program. Vocapable supplies software:
  it neither sells, rents, sources, nor supplies contact data, and it does not select
  whom a customer calls, when, or how often. Scraped or otherwise unauthorized-extraction
  data is refused on any plan and however it would arrive, and the waiver's own
  provenance representation excludes it rather than covering it. Every import carries a
  signed attestation of contact provenance, and the compliance floor below is unchanged
  by the waiver.
- The compliance floor is enforced in code, included on every plan at $0, and disableable
  by no API field, plan, flag, or support tool: the AI-disclosure opener played before
  the first model token, internal-DNC suppression applied at the batch run and re-checked
  at dial time, and phone normalization. On a configured live phone call, an opt-out
  phrase ends the current conversation and writes the durable internal suppression record
  before the call closes; browser sandbox and simulated test calls have no contact to suppress.
- One gate stands in front of every dial: campaign dials, ad-hoc calls and test calls
  all pass the same dialability check, and a check that cannot complete blocks the call
  instead of letting it through. Consent is held as a typed record and ranked against the
  consent standard in force for that purpose, and the values that bound the decision are
  written onto the attempt as it is made.
- Quiet-hours windows, frequency caps, consent-basis standards and recording-consent class
  are enforced at the gate on every attempt, in the contact's local time, and the values
  evaluated go into that attempt's evidence file. Calling-policy configuration is not
  exposed in the portal or the API, so nobody on either side loosens a window by accident.
  Vocapable enforces the values in force; it does not determine what the law requires
  where a customer dials.
- Every call, including calls the platform refused to place, produces an exportable
  evidence file recording which checks ran, which were waived, and on whose signature.
- Scope of service: Vocapable is a US calling platform; its privacy machinery is built
  on CCPA/CPRA. Calls involving protected health information are outside the Acceptable
  Use Policy. Tenant isolation is enforced by the database itself, call recordings are
  encrypted at rest under a dedicated managed key, and security questionnaires are
  answered directly and in writing about the controls themselves.
- Pricing: published outbound workload-class plans - Engage $349/month with 1 included concurrent
  session, Workforce $549/month with 2, Sales $1,199/month with 2. Extra concurrent sessions are
  $200/month each in any quantity, every outbound plan pays $0.005 per call attempt, and AI
  usage is $0.13 per minute month-to-month or $0.09 per minute on a signed 3-year
  commitment, which keeps the same base price and is non-cancellable with all sales
  final under a signed non-refund waiver. A volume discount steps the per-minute rate
  down with total monthly spend to a floor of $0.07 per minute, so enterprise plans
  run as low as $0.07/min. Receptionist is a fourth published plan and prices the
  inbound side: $250/month including 1 concurrent inbound connection, with additional
  simultaneous connections at $150/month each. It includes no outbound concurrent
  session and places no call, so it is charged no per-call-attempt fee, and the published
  per-minute AI-usage rate is charged on the calls an account places rather than on the ones
  it answers: a Receptionist invoice is its monthly plan price plus its additional
  connections, and nothing else. It is sold on its own or added to an
  outbound plan for the same monthly price, and it is bought from the billing page rather
  than chosen during signup. Entry is a free sandbox account, and payment starts only
  when a customer activates production under a signed Production Services Order. BYO
  carrier service remains on the customer’s Twilio bill. The published card is
  design-partner pricing: it may move, and a signed order keeps its rates for its term.
- Company: Capstra Labs, LLC (d/b/a Vocapable). Contact: support@capstralabs.com.
  GitHub: https://github.com/CapstraLabs

## Pages

- [AI voice agents that turn calls into work](https://www.vocapable.com/): Product overview: AI voice agents for calls the customer places on their own Twilio account, their own numbers and their own contacts. Vocapable supplies the agent that holds the conversation in real time, the campaign engine that paces the dialing, the calling policy in force on every attempt, and an evidence file for every call including the ones it refused to place. Vocapable also answers inbound calls on those same numbers: the Receptionist plan is priced separately at $250 per month including 1 concurrent inbound connection, and the customer composes the answering steps. Run product resources in a workspace or headlessly through /v1; signup, onboarding, and first-key setup use browser flows.
- [Pricing](https://www.vocapable.com/pricing): Published pricing: three outbound plans - Engage $349/month with 1 included concurrent session, Workforce $549/month with 2, and Sales $1,199/month with 2. Extra concurrent sessions are $200/month each, in any quantity. Receptionist is the inbound answering plan at $250/month, including 1 concurrent inbound connection and no outbound session, with additional simultaneous connections at $150/month each; it is sold on its own or added to an outbound plan for the same monthly price. Every outbound plan pays $0.005 per call attempt, and AI usage is $0.13 per minute month-to-month or $0.09 per minute on a signed 3-year commitment (same base price; non-cancellable, all sales final under a signed non-refund waiver). Both of those are charges on the calls an account places: Receptionist answers calls rather than placing them, so it pays no per-call-attempt fee and no per-minute AI-usage charge, and a Receptionist invoice is its monthly plan price plus its additional connections. A volume discount steps the per-minute rate down with total monthly spend to a floor of $0.07 per minute - enterprise plans as low as $0.07/min. Entry is a free sandbox; payment starts only when a customer activates production under a signed Production Services Order, and BYO carrier service stays on the customer's Twilio bill.
- [Start free in the sandbox](https://www.vocapable.com/get-started): How onboarding works: a free sandbox account (the full builder, and your real script running down the whole dial path, every compliance gate live and failing closed, before a number points anywhere), then choose a plan, accept the Production Services Order, add a payment method, connect your verified Twilio account, and activate production in the portal when the workspace is ready.
- [Talk to sales](https://www.vocapable.com/demo): Talk to Vocapable about complex rollouts, technical architecture, and Enterprise terms. The free sandbox and standard production path are self-service. Contact: support@capstralabs.com.
- [Qualify leads at scale](https://www.vocapable.com/use-cases/qualify-and-book): Lead qualification at speed: run a lead campaign that qualifies completed conversations against your own rubric, captures the time a lead names, and sends enabled outcomes to your configured webhook. Your scheduler books the meeting from the record the agent handed you.
- [Staffing calls at roster scale](https://www.vocapable.com/use-cases/fill-shifts-automatically): Staffing calls at roster scale: run a calling program for tonight's shifts from the agency's own numbers, then use durable shift confirmations and decline reasons linked to the call. Deliver enabled shift-confirmation events by configured signed webhook, and use supported CSV exports or the API for call details and decline reasons while your coordinator keeps the roster.
- [CSAT & feedback calls](https://www.vocapable.com/use-cases/csat-surveys): Customer feedback calls in your own voice: ask the people you already serve about a transaction that happened, collect structured survey responses from completed feedback calls, and use CSAT or NPS views to follow feedback by campaign and question. CSV export jobs cover supported survey-response records, while transcript evidence is available through the API where a call has it.
- [Voice agents & campaigns](https://www.vocapable.com/voice-agents): Build voice agents from shipped templates for staffing availability, shift reminders, candidate follow-up, customer feedback, and sales outreach. Set your own objectives, questions, voice, and knowledge; test drafts and publish immutable versions through golden-transcript release checks; import lists with row-level issue reports; and launch, pause, resume, or cancel campaigns. Structured outcomes and caller requests become work in the call workspace, with configured signed webhooks for enabled events, supported CSV export jobs, and API reads available to fit your workflow.
- [A CRM built for one job: the phone](https://www.vocapable.com/crm): The call workspace built for phone operations: contacts with tags, lists, and CSV import that returns a row-level error report; an activity timeline across campaigns; dispositions, notes, consent, and internal do-not-call state; call transcripts and recordings through the API where available; and a native Inbox for messages, tickets, and callbacks. CSV export jobs cover supported records with selected filters and columns, while configured signed webhooks carry enabled events to your stack with a delivery history and self-service redrive. Product resources use /v1; signup, onboarding, and first-key setup use browser flows.
- [Product resources, available by API](https://www.vocapable.com/api): The headless mode: product resources use the /v1 REST API, while signup, onboarding, and first-key setup use browser flows. Contacts, lists, CSV imports and their row-level error reports, agents and the immutable published versions that dial, campaigns and their pacing, calls and their available evidence, caller requests, outcomes, consent and internal do-not-call records, exports and analytics are all API resources: cursor pagination on every list, RFC 9457 problem responses, scoped keys with in-place rotation, and a configured signed webhook endpoint per tenant carrying enabled events with delivery history and redrive. Your stack stays the system of record and the dialing runs on your own Twilio account. Public developer documentation: https://docs.vocapable.com.
- [Trust Center](https://www.vocapable.com/trust): Security and compliance posture: the four-control compliance floor no plan, flag, or support tool disables; per-call evidence files recording which checks ran and which the customer waived under signed attestation; tenant isolation enforced by the database itself; and a clear division of responsibility: production dials ride the customer’s own Twilio account, cold outreach on lists the customer purchased, rented or had appended runs under an executed Cold Outreach & Data Provenance Waiver in which the customer carries sole responsibility for the lawfulness of that program while scraped and unauthorized-extraction data is refused, and Vocapable serves US calling with protected-health-information workloads outside its Acceptable Use Policy.
- [AI receptionist for your inbound calls](https://www.vocapable.com/receptionist): Inbound AI answering on the customer's own verified Twilio account and their own number. One answering policy per number: two ordered chains, one for open hours and one for everything else, built from six step types - a keypress menu, ringing the tenant's own people, the AI agent, voicemail, a spoken message, and a forward to a number the tenant configured - with open hours and holiday dates in the tenant's own timezone. Only the AI step claims a reserved concurrent inbound connection; menus, rings, forwards and spoken messages claim none, which is why a one-connection receptionist can publish a far larger answering flow than the concurrency it bought. When every connection is busy the caller advances to the next step the tenant wrote down, usually their own voicemail. Priced at $250 per month including 1 concurrent inbound connection, with each additional simultaneous connection $150 per month in any quantity; sold on its own or attached to an Engage, Workforce or Sales subscription for the same monthly money. That is the whole of a Receptionist invoice: it pays no per-call-attempt fee because it answers calls rather than placing them, and the published AI-minute rate is charged on the calls an account places rather than on the ones it answers. Each added connection is prepaid a full month at purchase, whatever day of the billing period it falls on, and is not reserved until that charge succeeds; a connection already held is not switched off over a single failed payment. Receptionist connections stay reserved for inbound calls, separately from campaign capacity.
- [About Capstra Labs](https://www.vocapable.com/about): The company behind the product: Vocapable is a product of Capstra Labs, LLC, a California limited liability company doing business as Vocapable, reachable in writing at support@capstralabs.com, with its public code at https://github.com/CapstraLabs. What it builds: the AI voice agent, the campaign engine, the CRM for phone outreach, the /v1 API, and a per-call evidence file - on speech and language infrastructure the company operates itself rather than renting from a hosted voice API. Where the service begins and ends: Vocapable serves US calling and its privacy machinery is built on CCPA/CPRA, every production call rides the customer's own Twilio account and numbers, and calls involving protected health information are outside the Acceptable Use Policy. Agreements are governed by the laws of the State of California.
- [Who to email, and what you get back](https://www.vocapable.com/contact): How to reach Vocapable: one written address, support@capstralabs.com, carrying four routes. Sales and production conversations go through the demo page and are answered by the founders. Support covers an existing account. Security questionnaires are answered directly and in writing about the controls themselves, and the control descriptions are published on the Trust Center rather than held back for a questionnaire. Legal covers the published agreement set. Vocapable serves US business calling in English.
- [Compliance enforced in code](https://www.vocapable.com/compliance): The compliance engine as a product surface: the four controls enforced in code on every plan and reachable by no API field, plan, flag or support tool, namely the AI-disclosure opener played before the first model token, opt-out detection writing the internal do-not-call list, internal-DNC suppression applied at the batch run and re-checked at dial time, and phone normalization; one dialability gate every campaign dial, ad-hoc call and test call passes, where a check that cannot complete blocks the call; a typed four-class consent record (PEWC, PEC, EBR, TRANSACTIONAL) ranked against the consent standard in force; one revocation write path honored across every channel it covers, ahead of the 47 C.F.R. § 64.1200(a)(10) cross-channel mandate effective 2027-01-31, while the statutory bar for honoring any revocation is ten business days; and an exportable evidence file for every call including refused calls, recording which checks ran, which the customer waived under signed attestation and on whose signature, retained at least five years. The floor is included on every plan at $0.
- [The per-call evidence file](https://www.vocapable.com/evidence): The per-call evidence file: for every attempt it places or refuses, Vocapable writes the calling window and caps that bound the dial in the contact's local time, the consent records relied on, the AI-disclosure playback confirmation, the internal-suppression result and the dial-time re-check, and the signed elections the customer made, each naming its attestation and its signer; the attempt row carries the snapshot and leaves by CSV through the exports API. A synthetic sample file is published beside the page.
- [Your Twilio, your numbers, your carrier bill](https://www.vocapable.com/telephony): Telephony ownership: every production call is placed on the customer's own Twilio subaccount, so the carrier account, the numbers, the registrations, the negotiated per-minute rates and the caller-ID reputation stay the customer's. Vocapable originates no production call and resells no minutes, and a Vocapable invoice carries no carrier line at all, because the customer's own carrier bills the telephony directly and the published per-minute rate prices the AI session rather than the carrier leg. Connecting and verifying the subaccount is an onboarding step rather than a choice between products: an account reaches verified only when its credentials prove out, the subaccount is reachable, and a conservative pacing floor is stored for the connection; a sandbox mock-verified account cannot dial, and the inbound Voice callback is a signed URL the control API accepts only after the callback URL, the form body and the Twilio signature verify against that account's vaulted auth token. Numbers held under Vocapable's own carrier account are permitted to carry paid test calls to numbers the customer proved it controls and nothing else, enforced at the dialability gate rather than asserted in a policy document. Workspace and headless consumption run on the same account, the same /v1 and the same compliance floor.
- [Outcomes: the metrics we report](https://www.vocapable.com/outcomes): The instrument panel: every metric Vocapable computes on a customer's own campaigns and commits to reporting, with the read that produces each one. The dial-to-outcome funnel with its stage rates, the disposition mix with each disposition's share of its group, and turn-level timing percentiles all ship on /v1, each over a bounded window the caller names, plus per-campaign live counters carrying spend to date. Refusals are reported by reason from the platform's own two ledgers, the batch run's blocked breakdown and the dial-time re-check's disposition sub-code. A stage with nothing beneath it reports empty rather than zero. Every figure is computed on the customer's own campaigns and each one names the read that produces it.
- [What we publish, and where to find it](https://www.vocapable.com/resources): The resource shelf: every artifact Vocapable publishes so a buyer can evaluate the product without a sales conversation. It links the complete published rate card and the campaign cost calculator on the pricing page, which prices a visitor's own campaign shape against those published rates in the browser and labels its output an estimate rather than a quote; the anatomy of the per-call evidence file, with a synthetic sample bundle to download; the compliance floor enforced in code on every plan; the Trust Center; the complete agreement set, published from the same source text the product serves for acceptance; the published simulated demo calls, each labelled as a simulation in AI voices with its transcript beside it; and /llms.txt and /llms-full.txt for machine readers. Nothing on the page is behind a form and no item asks for an email address.
- [Press kit](https://www.vocapable.com/press): The press and analyst kit: the approved one-paragraph boilerplate for Vocapable, a product of Capstra Labs, LLC, a California limited liability company doing business as Vocapable; the entity facts a writer can check, including that agreements are governed by the laws of the State of California and that the one published written address is support@capstralabs.com; and the brand files that exist with their usage rules, which are the icon and favicon files served from the site root. The wordmark is drawn inline in the site's own header rather than exported as artwork, so there is no logo-lockup file to ship. Vocapable runs on Twilio; no partnership or endorsement is implied. Vocapable confirms the entity facts on the page, the published rate card and anything in the legal set, and does not disclose customer names, headcount, funding or revenue.
- [BYO carrier vs resold minutes](https://www.vocapable.com/compare/byo-vs-resold-telephony): Two ways to buy a phone call, compared as models rather than as vendors. In the resold model the platform holds the carrier account and re-bills the minutes. Vocapable ships only the other one: every production call leaves the customer's own Twilio subaccount on the customer's own numbers, so the carrier account, the registrations, the negotiated rates and the caller-ID reputation stay with the customer, and the customer's own carrier bills the telephony directly. So your Twilio rate is the rate you pay: a Vocapable invoice carries no carrier line, no number rental and no markup on a single minute. Vocapable's own numbers are permitted to carry paid test calls to numbers a customer proved it controls and nothing else, enforced at the dial gate. No competitor is named on this page and no competitor's terms are reported.
- [A published rate card vs a quote](https://www.vocapable.com/compare/published-rate-card-vs-per-minute-quote): How Vocapable prices, compared with a per-minute quote as a model rather than as any vendor's terms. Every figure is published and rendered from one rate-card module, so a buyer can compute the bill before the first call: outbound plans at $349, $549 and $1,199 per month with 1, 2 and 2 included concurrent sessions, additional sessions at $200 per month each, $0.005 per call attempt, and AI usage at $0.13 per minute month-to-month or $0.09 per minute on a signed 3-year commitment, stepping down with total monthly spend to a floor of $0.07 per minute. The per-minute figure prices AI usage and not the carrier leg, so carrier minutes stay on the customer's own Twilio bill and a Vocapable invoice carries no carrier line. Inbound Receptionist is priced separately at $250 per month with $150 per additional connection. No competitor is named and no competitor's terms are reported. Design-partner pricing: published to plan against, and locked for the term of any signed order.
- [A compliance floor vs a setting](https://www.vocapable.com/compare/compliance-floor-vs-compliance-flag): The difference between a control that cannot be turned off and a setting that can. Vocapable enforces four controls in code on every plan at no charge: the AI-disclosure opener played before the first model token, opt-out detection writing the internal do-not-call list mid-call, internal-DNC suppression at the batch run and again at dial time, and phone normalization. They are not settings and no API field, plan, flag, support tool or spend cap reaches them; an account that has reached its spending limit stops dialing rather than dialing with the floor off. One gate stands in front of every dial the account makes, campaign dials, ad-hoc calls and test calls alike, and a check that cannot complete blocks the call instead of letting it through. The platform enforces the policy values in force and records them on every attempt; it does not determine what the law requires where a customer dials.
- [AI receptionist vs answering service](https://www.vocapable.com/compare/ai-receptionist-vs-answering-service): Two ways to buy inbound answering, compared as models rather than as vendors. Per-call human answering prices arrivals; a Vocapable Receptionist connection is a monthly price for one concurrent inbound answer, held against the customer's own traffic: $250/month including 1 concurrent connection, $150/month for each additional one, sold on its own or attached to an outbound plan for the same monthly price and bought from Billing. It answers rather than places calls, so it pays no per-call-attempt fee and no per-minute AI-usage charge, and the invoice is the plan price plus its additional connections. The customer authors the answering policy per number: open hours in their own timezone, then an ordered chain of a keypress menu, their own people, the agent, voicemail, a spoken message or a forward. Only the agent step claims a reserved connection. The call answers on the customer's own Twilio subaccount and their own number. Against other tenants the platform-wide reserve defaults to zero, exhaustion advances the caller to whatever the customer configured next rather than queuing, and a new connection is prepaid a full month and is not reserved until that charge succeeds.
- [Glossary of AI calling and TCPA terms](https://www.vocapable.com/glossary): Plain-language definitions of the terms in an AI phone-outreach contract: speed-to-lead, TCPA, prior express written consent, established business relationship, the internal do-not-call list, revoke-all revocation, BYO telephony, the concurrent session (extras at $200), the concurrent inbound connection ($250 including 1, additional at $150), answering-machine detection, the difference between a call attempt at $0.005 and a conversation billed as AI usage at $0.13 per minute, and the per-call evidence file.
- [The questions buyers ask first](https://www.vocapable.com/faq): The question index: every question this site answers, and the one page that answers it. Answered here, because no product page owns them: what an AI calling platform actually costs, whether AI cold calling is legal in the US, whether an AI can answer a business phone, whether the platform can be run without its dashboard, how a customer's data is protected, and what happens to call recordings. Every other question is answered on the page that owns it (pricing, receptionist, compliance, evidence, outcomes and telephony) and is linked rather than repeated, so no two FAQPage nodes on this domain ever answer the same question.
- [Changelog: what shipped, and when](https://www.vocapable.com/changelog): What shipped and when, newest first, grouped by month. Each entry states what changed, who it is for, and what a business gets from it. A capability is announced here on the day it ships and nowhere ahead of it, so this page is the running record of what the product does now. Every capability sentence carries the backend document and section it traces to, and the entry links the page that owns a number rather than restating it.
- [Compliance literacy for AI calling](https://www.vocapable.com/blog): Writing on two axes: plain readings of the rules that govern US AI calling, and buyer playbooks for the people who have to justify this internally. Every external fact carries its source and the date the source was last read, because a citation with no read-date is a claim with no expiry. Current posts: one revocation write path honored across every channel it covers, with the statutory ten-business-day bar stated separately from same-transaction propagation; what a Vocapable invoice carries and what it does not, with the cost categories to ask any vendor about; and the anatomy of the per-call evidence file, read line by line.

## Glossary

- [Answering-machine detection (AMD)](https://www.vocapable.com/glossary/answering-machine-detection): What the platform does when a machine picks up, not a person.
- [BYO telephony](https://www.vocapable.com/glossary/byo-telephony): Your Twilio subaccount, your numbers, your carrier bill. Always.
- [Call attempt vs conversation](https://www.vocapable.com/glossary/call-attempt-vs-conversation): Two things the platform counts separately, and bills separately.
- [Concurrent inbound connection](https://www.vocapable.com/glossary/concurrent-inbound-connection): Inbound answering capacity, reserved so outbound cannot eat it.
- [Concurrent session](https://www.vocapable.com/glossary/concurrent-session): The unit outbound plans are sold in: one live AI conversation at a time.
- [Established business relationship (EBR)](https://www.vocapable.com/glossary/established-business-relationship): A calling basis resting on a relationship already in your records.
- [Internal do-not-call list](https://www.vocapable.com/glossary/internal-do-not-call-list): Your own suppression list, read on every call the platform places.
- [Per-call evidence file](https://www.vocapable.com/glossary/per-call-evidence-file): What every call leaves behind, including the ones we refused.
- [Prior express written consent (PEWC)](https://www.vocapable.com/glossary/prior-express-written-consent): The strictest consent class, its disclosure text kept verbatim.
- [Revoke-all revocation](https://www.vocapable.com/glossary/revoke-all-revocation): One person asking you to stop, applied everywhere in one write.
- [Speed-to-lead](https://www.vocapable.com/glossary/speed-to-lead): The time from a lead arriving to the first attempt leaving.
- [TCPA](https://www.vocapable.com/glossary/tcpa): The statute governing calls placed with an artificial voice.
- [Upstream list screening](https://www.vocapable.com/glossary/upstream-list-screening): The screening you run on your own list, recorded on every call.

## Questions

- [What does an AI calling platform actually cost?](https://www.vocapable.com/faq/what-does-an-ai-calling-platform-cost)
- [Is AI cold calling legal in the US?](https://www.vocapable.com/faq/is-ai-cold-calling-legal-in-the-us)
- [Can an AI answer my business phone?](https://www.vocapable.com/faq/can-an-ai-answer-my-business-phone)
- [Can I run this without your dashboard?](https://www.vocapable.com/faq/can-i-run-this-without-your-dashboard)
- [How is my customer data protected?](https://www.vocapable.com/faq/how-is-my-customer-data-protected)
- [What happens to my call recordings?](https://www.vocapable.com/faq/what-happens-to-my-call-recordings)

## Changelog

- [A receptionist connection is prepaid, then reserved](https://www.vocapable.com/changelog/2026-08-18-receptionist-connections-prepaid): The reserved line is paid for before the slot is withheld.
- [The AI receptionist, and its answering-policy engine](https://www.vocapable.com/changelog/2026-08-17-ai-receptionist): Inbound calls answered on your own Twilio, in your own order.
- [Cold outreach, admitted under an executed waiver](https://www.vocapable.com/changelog/2026-08-15-cold-outreach-waiver): Purchased and rented lists, admitted under a waiver you sign.
- [One published rate card, priced on AI usage](https://www.vocapable.com/changelog/2026-08-13-published-rate-card): One base per plan, one attempt fee, one AI-usage minute rate.
- [Developer documentation](https://www.vocapable.com/changelog/2026-08-11-developer-docs): Quickstart, guides, and a reference generated from the spec.
- [Your screening arrangement, recorded on every call](https://www.vocapable.com/changelog/2026-08-11-screening-attestation-on-every-call): Sign once, and every call names your arrangement and its signer.

## Writing

- [Cross-channel revocation and the 2027 rule](https://www.vocapable.com/blog/cross-channel-revocation-and-the-2027-rule): One stop request, honored everywhere it covers. Ahead of 2027.
- [What a per-minute quote leaves out](https://www.vocapable.com/blog/what-a-per-minute-quote-leaves-out): Every line on a Vocapable invoice, and where the rest stays.
- [What is in a per-call evidence file](https://www.vocapable.com/blog/what-is-in-a-per-call-evidence-file): A waived stage is a signature. It is never a silent pass.

## Legal

- [Legal overview](https://www.vocapable.com/legal): Index of all legal documents.
- [Master Services Agreement](https://www.vocapable.com/legal/terms): The core agreement governing use of the Vocapable platform. Incorporates the addenda, AUP, AI disclosure, DPA, and privacy policy by reference.
- [Telecom Compliance Addendum](https://www.vocapable.com/legal/telecom-addendum): Your calling-law obligations for consent, scrubbing, disclosures, and revocation. Controls over the MSA body where they conflict.
- [Platform Test Calls Addendum](https://www.vocapable.com/legal/test-calls-addendum): The only permitted use of platform-owned numbers: verified test calls to numbers you control.
- [Acceptable Use Policy](https://www.vocapable.com/legal/aup): What may never run on the Service, and what happens when it does.
- [AI Technology Disclosure](https://www.vocapable.com/legal/ai-disclosure): A plain-language notice of what our AI is, what can go wrong, and what relying on it means.
- [Data Processing Addendum](https://www.vocapable.com/legal/dpa): CCPA/CPRA service-provider terms for the personal information we process on your behalf, plus the two retention carve-outs that survive a deletion request.
- [Cold Outreach & Data Provenance Waiver](https://www.vocapable.com/legal/cold-outreach-waiver): The document a customer signs to run cold outreach, calls to purchased, rented, or appended lists, and artificial-voice voicemail: their own list, their own carrier, and their own responsibility for the lawfulness of every call. It controls over the other documents for that outreach.
- [Privacy Policy](https://www.vocapable.com/legal/privacy): How we handle personal information: yours as a customer, and the data we process on customers’ behalf.
- [Website Terms of Use](https://www.vocapable.com/legal/website-terms): Terms for this website only. Use of the platform itself is governed by the Master Services Agreement.

## Optional

- [llms-full.txt](https://www.vocapable.com/llms-full.txt): full text of every page in one file