call_evidence cev_01J9…K7Q
Synthetic data
- scrub_report
- 8/8 PASS
- ai_disclosure
- played · before first response
- consent
- PEWC · your web form
- outcome
- meeting_booked · Thu 10:30 AM
- delivery
- calendar invite + SMS sent
Exportable evidence
Point it at the leads you’ve captured — imported, or sent straight from your stack. Vocapable calls each one, discloses it’s AI, qualifies interest against your rubric, books the interested, and documents the rest. Shift confirmations and CSAT surveys run on the same engine.
Runs on your captured, opt-in leads. Purchased lists are refused — always.
Qualified leads
Product UI · synthetic data
Your list, end to end
This is the machine: your captured leads called, the protected ones refused with proof, the interested ones booked and opted in. Without hiring a single caller.
How a campaign runs: your list — imported or delivered by API, illustrative size 200,000 — is scrubbed through the eight-stage compliance gate before any dial; protected numbers are refused and suppressed, each refusal recorded. Cleared leads get a phone conversation that opens by disclosing it’s AI and is qualified against your rubric. Outcomes sort three ways: interested and opted in — booked to your calendar; not now — reason documented, compliant retry scheduled; protected — never called. Every call, made or refused, writes an exportable evidence file.
01 · The list
Yours — opt-in, consent attested. Purchased lists are refused.
02 · The gate
Eight stages, fail-closed. Protected numbers never ring — each refusal recorded.
03 · The conversations
Opens by disclosing it’s AI. Qualifies against your rubric. Answers from your product knowledge.
agent ▸ “Quick heads-up — I’m an AI assistant calling for Acme.”
synthetic transcript
04 · The outcomes
Interested leads become pipeline — webhooks fire, signups land, revenue follows.
data → scrub → call → qualify → pipeline → webhook → signup → paid ✓
call_evidence written · made or refused · exportable
Proven, per call
Illustrative scenario — your list, your rubric, your numbers.
One engine · three jobs
Revenue teams: work every lead in seconds. Operations teams: call all your people at once. Same engine — it never gets tired.
Flagship · Qualified pipeline
Every name on your list gets a real conversation — the interested say yes to a demo built for their business, the rest leave reasons.
Hear a cold call become a booked demo
Simulated demo · AI voices
Staffing · Fill shifts
The whole candidate list called in one window — confirmations straight back to your ATS.
Hear a shift confirmation
Simulated demo · AI voices
CX · Measure satisfaction
Structured, scored phone surveys — verbatims captured word for word.
Hear a CSAT survey call
Simulated demo · AI voices
Every published sample opens with the AI disclosure — exactly as your customers hear it.
From your list to live calls
You’ve seen the machine run. This is how you start it — the same five steps founder-led onboarding walks with you. No flow builders. No prompt-engineering degree.
Lead qualification, shift confirmation, CSAT — structured objectives, not a flow-builder maze.
Agent template
lead_qualificationSpeed-to-lead qualifier
Structured objectives, not a flow-builder maze. The template already knows the job.
Persona, objectives, your product knowledge, your voice. Knowledge packs turn your site, docs, and pricing into what the agent actually says.
Knowledge pack
compiledpersona
Warm, direct, sounds like your best rep — your voice, your vocabulary, your rules of engagement.
Call your own phone before any customer does. Iterate until it sounds like your best rep.
Test call
your phone rings firstopening line — plays before the first response, always
“Hi — this is an AI assistant calling on behalf of your company. This call may be recorded…”
The AI disclosure is enforced in code — it is structurally impossible to remove, on every plan. Iterate on the voice until it sounds right, then launch.
Bring your list — import it, or send contacts through the API — with a consent attestation; review the scrub report, acknowledge, go.
Pre-dial scrub
fails closedEight-stage pre-dial compliance scrub, run in order before any number is dialed. A stage that cannot complete blocks the call — uncertainty never resolves in favor of dialing.
scrub report → reviewed & acknowledged cleared list proceeds
Boards, webhooks, CSV, and your CRM — plus an evidence file for every call.
Live call → structured outcome
synthetic transcript→ SMS confirmation delivered
→ synced to CRM as structured data
→ evidence file written · exportable
Metrics reported live, per campaign: Lead-to-call time, Contact rate, Qualification rate, Meetings booked, Show rate, Pipeline value handed to CRM, Fill rate, Time-to-fill, Response rate, Confirmation SMS delivery, CSAT / NPS, Verbatim coverage, Cost per outcome.
From calls to numbers
Other sites lead with stats you can’t check. We show the instrument panel instead: every metric here is computed on your campaigns and reported live, with cost per outcome on all of them. The funnel above ends in whatever these instruments read. That’s the claim — and it’s the only one we make.
From numbers to your tools
Meetings booked in-call on your reps’ real calendars — Google and Microsoft — with the invite in the prospect’s inbox before hangup.
Confirmations and recaps by text, so every voice outcome has a written trail the contact can act on.
Every outcome delivered to your CRM or ATS as structured data — webhooks for real time, CSV for everything else. And it runs both ways: your stack can drive Vocapable through the same API the dashboards use.
The proof, per call
Every dot in that funnel is a phone call to a real person — which is exactly why some are refused. Vocapable writes the file either way: what ran, what blocked, what was said, what booked. When counsel asks, you hand them the export.
call_evidence cev_01J9…K7Q
Synthetic data
Exportable evidence
call_evidence cev_01J9…M2X
Synthetic data
A stage that did not run never reads as a stage that found nothing.
Refused — and proven
Every dial passes a pre-dial scrub that fails closed. Quiet hours, frequency caps, and the AI disclosure are enforced upstream of anyone’s intent — the illegal call is made impossible, not discouraged.
Every call the platform makes — or refuses to make — produces an exportable evidence record. When counsel asks, you hand them the file.
A published rate card and one bill. The compliance floor is on every plan at $0 — baseline scrubbing is never a paid add-on.
Your CRM — or ours
Send us your data — CSV or API — and run everything from the dashboards: contacts, campaigns, boards, outcomes. Vocapable is your calling system of record.
Keep your stack as the system of record. Drive calls through the /v1 REST API with your own Twilio; outcomes return by webhook. No bulk upload — send each contact as you dial it.
Same engine, same compliance floor, same pricing — every surface above runs on the same API and webhooks your engineers will use. Public docs at GA.
Three workload classes with real numbers on the page — from $299/mo — plus prepaid capacity blocks and a calculator that runs on your inputs. One invoice, $0 implementation fee, and the compliance floor is $0 on every plan.
The sandbox is $49, credited against your first invoice: your real use case, your real material, your agent calling your own phone — before anyone signs anything.