Resources
What we publish, and where to find it
Judge this product on the material. The rates we will charge you, the record we write for every call, the agreements you would sign, and calls you can listen to right now. Every item is a public page or a public file, and not one of them asks for your email first.
Price it without talking to us
Both of these are on the pricing page, and neither of them ends in a form. You can build the number your finance team will ask for and leave without telling us you were here.
/pricing
The published rate card
Every plan, the usage charges that sit on top of them, the volume discount and the floor it steps down to, all printed on the page. Read it, build your comparison sheet, and know the number before anyone at this company knows your name.
For: Procurement, and anyone building a comparison sheet across vendors who is tired of writing “contact us” in a cell.
/pricing#calculator
Campaign cost calculator
Put in your list size, how long you want to work it, attempts per contact, minutes per conversation and the answer rate you expect. It prices your campaign against the published rates, in your browser, as you type. Every default is yours to replace with your own numbers, so what comes out is an estimate you built rather than a quote we handed you.
For: Whoever has to put a defensible number on a budget line before anyone will approve the spend.
Check what we actually write down
The artifact first, then the anatomy of it, then the pages that explain what produced it and what you would be signing. This is the group a compliance reviewer came for, and it is deliberately the longest one on the shelf.
/media/evidence/sample-evidence-bundle.json
Sample evidence bundle
The compliance record written for a call attempt, as a JSON file you can open in an editor and hand to your own engineer. It is synthetic: a file we authored to show the shape, not an export the product generated, and no customer data of any kind is in it.
For: The engineer or reviewer who would rather read the object than read about it.
/evidence
The per-call evidence file
The same record rendered key for key, with the part that matters explained: what bound the dial, which checks ran, and which were waived, each waiver carrying the document it stands on and the officer who signed it. When somebody asks how a call happened, that file is the answer.
For: Compliance and legal review, and the buyer who has been told “it’s all logged” by every vendor in this category and shown it by none.
/compliance
The compliance floor
What runs in code on every dial, on every plan, at no charge, with nothing on our side able to switch it off: not an API field, not a plan tier, not a support ticket. Plus the gate every dial passes before it becomes a call, written as engineering with the qualifiers attached.
For: The person who has to answer “what stops a bad call from going out” in front of their own leadership.
/trust
The Trust Center
The security and data posture, control by control, written for the person whose job is to find the gap. Most of a security questionnaire is answered there before you send it.
For: A security review, and the questionnaire that always follows it.
/legal
The agreement set
Every document, in full: the master agreement, the addenda it incorporates, the waiver signed only on election, and the site policies. Each one is published from the same source text the product serves for acceptance, so the version you read here is the version you accept, hash-verified.
For: Your own lawyer, before the first call rather than deep into a redline.
Hear a call before you commit to anything
The published demo calls are scripted simulations in AI voices, labelled as such on the player, and every one prints its transcript beside it: every turn, in order, so you can read what you just heard instead of taking our summary of it.
Listen for the first sentence. The AI disclosure plays before the first model token on every call the product places, and the demos open the same way, because a demo that skipped it would be demonstrating a different product.
Another published call, a qualification conversation from start to handoff, plays on the talk-to-sales page, and the call playing here also runs in context in the use-case section of the home page. Same label, same transcript, no email required.
Play it here
A cold call, start to handoff
Simulated demo · AI voices
Transcript ＋－
- agent ▸ “Hi Dale, being upfront: I’m an AI assistant calling for Crestway Software. We help trucking companies cut dispatch paperwork. Worth thirty seconds?”
- lead ▸ “Uh, go ahead.”
- agent ▸ “Who runs dispatch and invoicing today? Is that all in-house?”
- lead ▸ “My office manager. Takes half her week, honestly.”
- agent ▸ “That’s the exact fit. Here’s my offer: we build a short demonstration around your operation, your lanes, your paperwork, and send it over. Fair?”
- lead ▸ “Yeah, I’d look at that.”
- agent ▸ “Done. And once you’ve had a look, when’s good to walk through it - mornings any use to you?”
- lead ▸ “Tuesday after nine works.”
- agent ▸ “Tuesday after nine - noted, with everything else you told me. It’s in front of the Crestway team the second we hang up, and they’ll lock the time in. Thanks, Dale.”
Scripted and synthesized: AI voices reading a written conversation, so nobody on this recording is a real prospect. What it shows you is the shape of a call.
For machines, and for the people who send them
Assistants are going to be asked about this company whether or not we make it easy, so the same facts the pages carry are published in a form a model can read whole.
/llms.txt
llms.txt
A structured index of every page on this site with a one-line description of each, plus the company facts and the published pricing in prose. It is generated from the same registry the pages themselves are built from, so it cannot drift away from what the pages say.
/llms-full.txt
llms-full.txt
The full text of every page in one file, assembled from the built HTML after the templates, the markdown and the data files have collapsed into the bytes a visitor actually receives.
https://docs.vocapable.com
Developer docs
The reference for the API, built straight from the published contract artifact rather than written alongside it, so what it documents is what the API serves.
For: the engineer who has been handed the integration and wants to know what they are in for.
Read all of it, then open an account and check the rest yourself.
The sandbox costs nothing and runs the whole builder: no card, no carrier account. If a question on this page went unanswered, write to us and a person answers.
Questions people ask about this page
Do I have to talk to anyone to get a price?
No. The complete rate card is published on the pricing page: every plan, the usage charges on top of them, and the volume discount with the floor it steps down to. A calculator on that same page prices your own campaign shape against those published rates, in your browser, so you can walk into your budget meeting with the number already in hand. What it produces is an estimate you built from your own assumptions rather than a quote from us.
Is the downloadable evidence file real customer data?
No. It is a synthetic file Vocapable authored to show the shape of the compliance record written for a call attempt. It is not an export the product generated, and no customer data of any kind is in it. It is offered so an engineer or a reviewer can read the object itself instead of reading a description of one.
Are the demo calls recordings of real calls?
No. They are scripted, simulated conversations in AI voices, labelled as simulations on the player itself, and each one publishes its transcript beside it, every turn in order. They open with the same AI disclosure the product plays before the first model token, which is the part worth listening for.
Is anything on this page behind a form?
No. Every item here is a public page or a public file, and none of them asks for an email address, a company name or a phone number first. Open what you want, read it on your own time, and talk to us when you have a real question.
Can I point an AI assistant at this site?
Yes, and this site publishes files built for exactly that. /llms.txt is a structured index of every page with a one-line description of each, generated from the same registry the pages are built from so it cannot drift from them. /llms-full.txt carries the full text of every page in a single file, assembled from the built HTML.