Platform · Telephony ownership
Your Twilio rate is the rate you pay
Every production call leaves a Twilio subaccount in your name. Twilio bills you for the minutes at the price you negotiated, straight to you. Vocapable bills you for the plan and the AI time, and that is the entire list. The numbers, the registrations and the reputation they earn stay yours, and they go where you go.
What stays yours
You already pay a carrier. Here is what each piece of that is worth the day an AI agent starts dialing on it.
The account
A Twilio subaccount in your name, on your commercial terms. The credentials you hand the platform sit in an encrypted vault, and every dial resolves them from your account.
The numbers
Bought and controlled by you. Each one connects under your account, and that account decides its credentials and its pacing budget.
The registrations
Your 10DLC brand and campaign registration, your FTC Subscription Account Numbers, your Robocall Mitigation Database entry where it applies, your STIR/SHAKEN attestation and your caller-ID authority. Your registrations are the ones a carrier looks at, so nothing here is waiting on ours.
The rates
The per-minute price you negotiated with your carrier, unchanged. It is the same price on the day an AI agent starts calling on it as it was the day before.
The reputation
Caller-ID reputation builds on numbers you keep, so it comes with you wherever the software goes.
The authority
You are the originating party on your own calls, which is another way of saying the account answers to you. Traceback and regulatory inquiries come to you, and the evidence file for every call is already in your hands.
Your own contract says it in one line: you are the originating party and the party on whose behalf the calls are placed (MSA §6.1). We publish the contract, so you can read the sentence instead of taking our word for the summary.
Twilio bills you for the minutes. We bill you for the software.
Your carrier invoices you directly, at the rate you negotiated with it. Our invoice carries your plan and your AI usage. That is the whole list, and it is the reason the per-minute number below is as small as it is.
The published rate is $0.13 a minute month-to-month and $0.09 on a signed commitment term, before the volume discount takes it further. It prices the AI session: the model, the speech, and the session time on our own hardware. Your carrier prices the carrier leg, which is why our rate is the same whoever carries the call.
The whole rate card is on the pricing page. Every figure is published, so you can price a campaign before you talk to anybody.
Where each charge comes from
- Yours The minutes, the number rental and the registration pass-throughs, invoiced to you by your own carrier on your own agreement with them.
- Ours The plan, and the AI usage rated against it. That is the list.
Two bills from two companies, each for the work that company actually did. You can check both of them line by line.
Whose account carries what
Every production call leaves your account
Our own carrier account exists for one thing: a paid test call to a destination proved through code verification. Your traffic leaves the subaccount in your name, all of it. That is why the only caller-ID reputation in this conversation is yours, and why nothing we own ever sits in the middle of your calls. The dialability gate enforces that in code, not on a policy page.
Your own contract says the same, two clicks from here: MSA §6.2 and the Platform Test Calls Addendum.
Vocapable runs on Twilio Media Streams. That is a fact about our stack rather than a partnership.
Connecting is a step, not a decision
You connect the account you already have, and the platform proves it works before it will dial on it. Four steps, in the portal, in this order.
- 1
Connect the subaccount
Add the Twilio subaccount you already have. The account identifier and auth token go straight into an encrypted vault, and every credential a dial needs resolves through your account.
- 2
Verify it
Verification is proof rather than a checkbox. The account reaches verified when the credentials prove out, the subaccount is reachable, and the platform stores a conservative pacing floor for the connection. You find out your account is ready before a customer does. A sandbox account carries mock evidence and stays in the sandbox, so a practice run is never mistaken for the real connection.
- 3
Connect a number
A number you own connects under that account and becomes a record of its own rather than a string in a config field. That account decides its credentials and its pacing budget. If the number should answer as well as call, you choose which published agent version receives it.
- 4
Take the signed callback URL
The platform hands you the exact signed inbound Voice URL to point the number at. When your carrier calls it, we answer only once the public callback URL, the full form body and the Twilio signature verify against your account’s vaulted auth token, and only for an active, carrier-confirmed voice number on your account with a receiving agent selected. Nobody makes your agent talk by guessing a URL.
When something on your carrier account goes wrong, you see it. A suspension, a rejected registration, or a calls-per-second ceiling lower than the account claims each shows up as an error on the account and on the attempt it stopped, so you are reading a message instead of guessing at a silence.
Workspace or headless, on the same account
Use the dashboard, use the API, or use both in the same afternoon. Either way the call goes out on the account you just connected.
Workspace
Send your data as a CSV or through the API, and Vocapable becomes your calling system of record: contact records, lists, campaign boards, outcomes, dispositions and exports, with every call that ever touched a contact on one timeline.
Headless
Your own stack stays the system of record. Contacts are created through /v1, calls are driven programmatically, and enabled outcome events can reach your
configured signed webhook. The dashboard stays available as a read-only window;
signup, onboarding, and first-key setup run in the browser.
Same engine, same /v1, same compliance
floor, same pricing. The only thing that changes is where your contacts live.
The trust close
Your call, your account, your evidence
Every production dial leaves your account, aimed at a list you chose. The proof of what happened lands with you as well.
The calling windows, the frequency caps, the consent standard and the recording-consent class are yours to set. Set them yourself, or adopt one of the starter sets we publish. Either way we apply them on every attempt and stamp the values that bound the call into its record, along with who chose them and when, so what you hand a regulator is your own policy and the proof that it ran.
The floor does not move because the account changed. The AI disclosure plays before the first model token, an opt-out writes your internal do-not-call list at once, that suppression is applied at the batch run and again at dial time, and every number is normalized. On your carrier account exactly as on ours, on every plan, and no flag anywhere turns it off.
Vocapable serves US calling. The Trust Center lays out who holds what.
What getting started actually looks like
Sandbox first, your carrier in the middle, a signed order before production. The rate card is on the pricing page, and the two ways to buy a phone call are compared on BYO carrier vs resold minutes.
Start in the sandbox
A free sandbox account gets you the whole builder, and no card. It runs your script down the dial path with every gate live, before a number points anywhere.
Connect what you already have
Your Twilio subaccount, your numbers, and the registrations already sitting on them. It is the step with the most waiting in it, and it is the step that keeps the rates yours.
Production on your carrier
Going live is a signed Production Services Order and your own subaccount, connected and verified once in the portal. From then on Twilio bills you for the telephony and Vocapable bills you for the software.
Bring the account you already have.
Start free in the sandboxQuestions people ask first
Do I need my own Twilio account?
Yes, and it is the reason the pricing works the way it does. Every production call leaves a Twilio subaccount you own, so the numbers, the registrations, the rates you negotiated and the caller-ID reputation those numbers earn all stay yours. Connecting and verifying it once is a step in setup.
What does a Vocapable invoice charge for the calling?
Your plan and your AI usage. Twilio invoices you for the telephony directly, at the rates you negotiated, so those are the two bills you reconcile and every figure on ours is published before you sign anything.
Why is the per-minute rate the same either way?
Because it prices the AI session: the model, the speech, and the session time on our own hardware. Your carrier prices the carrier leg under your own agreement with them, which is why whose account a call rides on changes nothing about what Vocapable charges for it.
What are Vocapable’s own numbers for?
Paid test calls, to a destination proved through code verification, and that is the whole of it. Every production call leaves the subaccount in your name, which is why the caller-ID reputation being built here is yours. MSA §6.2 and the Platform Test Calls Addendum say the same thing in the contract you sign.
What happens when my own carrier account has a problem?
You see it. A carrier suspension, a rejected registration, or a calls-per-second ceiling lower than the account claims each appears as an error on the account and on the attempt it stopped, so you are reading a message instead of guessing at a silence.
Does connecting my own carrier change which controls run?
No. The compliance floor is the same on your carrier account as on ours: the AI disclosure plays before the first model token, an opt-out is detected and durably written to your internal do-not-call list, that suppression is applied at the batch run and again at dial time, and every number is normalized before anything reads it. It runs on every plan, through every entry point, and no flag anywhere turns it off.
Can I take my numbers and my account elsewhere?
Yes, and there is nothing to negotiate. The subaccount is in your name and you bought the numbers, so leaving is a matter of pointing them somewhere else. You keep the reputation they earned on the way.