Your workforce 01
Get ready for the next shift.
Call your roster to collect availability and shift responses. Keep tentative answers visible for your team to confirm.
Keep track of worker responses.
Explore this workflow →Make business calls useful. Qualify leads, coordinate your workforce, collect feedback, and give inbound callers a useful first answer.
Start with the workflow your team needs today. Add reception, workforce outreach and sales qualification in the same workspace as your operation grows. Build around your business knowledge and questions, then keep call records, captured details and follow-up together.
Your Twilio account keeps carrier control with you; Vocapable keeps call records, policy evidence, and next steps close to the work.
Qualified leads
Product UI · synthetic data
Every outcome documented, with the reason Delivered by webhook
Your list, end to end
Watch a list become pipeline
Your list goes in. The campaign works its eligible contacts within the calling window and caps. Completed conversations return as qualified outcomes your team can review, route, and act on.
How a campaign runs. The list is yours, captured or acquired, with provenance attested at import and cold outreach signed for under the waiver you accept. You choose who on it gets called. Imported or delivered by API, at an illustrative size of 200,000, it passes three pre-dial checks before any number is called: normalization, suppression against your own internal do-not-call list, and the calling window and frequency caps. Refusals are recorded. Campaign attempts use your own Twilio subaccount and numbers. Connected conversations open with an AI disclosure and can be qualified against your rubric. Completed-call outcomes sort three ways: interested and opted in, with qualification and next-step details available to your workspace and systems; not now, with the reason documented and a retry inside the caps; or opted out, added to your internal do-not-call list and suppressed. Call activity and refusals write an exportable evidence trail, and completed call records are available in your workspace or through webhook, CSV, or API.
01 · The list
200,000 leads on your list
Yours, captured or acquired, with provenance attested at import and cold outreach signed for under the waiver. You pick who gets called, and campaign attempts use your own Twilio subaccount and numbers.
02 · The gate
Checked before any dial
Numbers are normalized, compared with your internal do-not-call list, and kept inside the calling window and frequency caps. The gate fails closed, and refusals are recorded.
- NORMALIZE ✓
- INTERNAL_DNC ✓
- DIALABILITY ✓
- on your internal DNC → REFUSED · never dialed
03 · The conversations
Completed conversations become qualified outcomes
Connected calls begin with an AI disclosure. The agent uses your rubric and product knowledge to capture the details your team needs.
agent ▸ “Quick heads-up: I’m an AI assistant calling for Acme.”
synthetic transcript
04 · The outcomes
Sorted, delivered, provable
Qualified outcomes and dispositions are written to the relevant contact in your workspace, then made available to your stack through configured signed events, supported CSV exports, or API reads.
- INTERESTED · OPTED IN → qualified outcome delivered to your stack
- NOT NOW → documented, retry inside your caps
- OPTED OUT → internal DNC, suppressed for good
data → check → call → qualify → outcome → webhook
call_evidence written · made or refused · exportable
Proven, per call
Illustrative scenario. Your list, your rubric, your numbers.
Every check a number passes before it is dialed: compliance enforced in code. What the record it writes actually contains: the per-call evidence file.
One platform · four jobs
Put better calls to work across your business
Build agents and workflows for revenue, operations, customer feedback, and inbound service. These workflows turn conversations into clear records and usable next steps.
Revenue · Lead qualification
Qualified pipeline from the leads you already have.
Run a calling workflow that qualifies the leads you already have against your rubric. Interested leads can share the time they named, while disposition reasons give your reps clear context for their next step.
- Qualified against your rubric
- Time captured in their words
- Reasons your reps can use
A cold call, from first hello to next step
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.”
Operations · Workforce calls
Coordinate roster outreach from one workflow.
Build confirmation calls around your sites, tone, and escalation language. Run roster outreach from one workspace and keep structured shift confirmations and decline reasons attached to the work.
- Workflows for your operation
- Roster outreach at scale
- Shift confirmations and decline reasons
Customer experience · Feedback calls
Hear what customers say while the visit is fresh.
Ask your questions in your voice after the transaction. Keep structured survey responses, call outcomes, and the context your team needs together for follow-up and reporting.
- Your questions and follow-ups
- Structured survey responses
- CSAT and NPS views
Inbound · AI receptionist
Give callers a useful first answer.
Configure business hours, holiday rules, menus, routing, and AI answers on the number you already publish. Calls that need follow-up can create messages, tickets, callbacks, or updates to an eligible caller record.
- Hours, holidays, and menus
- Routes you control
- Inbox follow-up
Published samples open with the AI disclosure callers hear.
One business. Connected conversations.
Your front desk, workforce and sales team.
In one workspace.
Think of a snow-service business preparing for a storm. It needs workers ready, customers supported and new applications followed up. Those are different conversations with a shared operating home.
Your customers and workers 02
Give both a place to call.
Configure reception for customer questions and worker support. Use your approved business knowledge and route requests to the right team.
Keep track of messages and support requests.
Explore this workflow → Your next customers 03
Find out whether you fit.
Follow up with applicants using your qualification questions. Capture their needs and the next step they agree to.
Keep track of qualification details.
Explore this workflow →Start with one job. Add the next when you need it.
Run multiple campaigns and add inbound reception to your outbound plan. Increase inbound connections and outbound sessions separately as more conversations need to happen at once.
Compare plans and calling capacity →Bring the work from the systems you already use.
Import a roster or lead list with CSV. Use the API and signed webhooks to connect your forms and send call outcomes back to your own tools.
Build your first workflowIllustrative operating example. Your team confirms staffing assignments and configures the calling permissions, business facts and integrations for each workflow.
From your list to live calls
Launch your first campaign in five guided steps
Build and test in the free sandbox, then use the portal to choose a plan, complete production readiness, and connect the carrier account you already own. Ready workspaces activate production there; a carrier or compliance decision routes with the same context to review.
- 1
Start from a no-tool draft
Lead qualification, staffing outreach, and feedback calls: structured objectives, not a flow-builder maze.
Direct no-tool draft
lead_qualificationSpeed-to-lead qualifier
Structured objectives, not a flow-builder maze. Start with a direct draft and make the job yours.
- objective: qualify against your rubric
- objective: qualify and capture next-step details
- guardrail: answer only from your knowledge
Start from a direct draft and publish when it sounds like you. Completed conversations return structured outcome fields to your workspace and connected systems.
- 2
Make it yours
Persona, objectives, your product knowledge, your voice. Drop in your pricing sheet, your FAQ, your product PDFs, and a knowledge pack turns them into what the agent actually says.
Knowledge pack
compiled- your pricing sheet
- your FAQ
- your product PDFs
- your objection notes
persona
Warm, direct, sounds like your best rep, in your voice, your vocabulary, your rules of engagement.
- 3
Hear it
Before you spend a cent, hear a call end to end as a simulated demo in AI voices, transcript published beside it, opening with the same disclosure the product plays on every call.
Sandbox dial
the disclosure goes firstopening line, played before the first response, always
“Hi, this is an AI assistant calling on behalf of your company. This call may be recorded…”
Iterate on the voice until it sounds like your best rep, then launch. The AI disclosure is enforced in code, so it is structurally impossible to remove, on every plan.
- 4
Launch
Choose a plan, accept the production order, add a payment method, and connect your own verified Twilio subaccount. The portal guides readiness and lets ready workspaces activate production; carrier or compliance decisions route with the same context to review.
Pre-dial checks
fails closedThe three pre-dial checks the platform performs, run in order before any number is dialed: normalization, suppression against your own internal do-not-call list, and the calling window and frequency caps. Any check that cannot complete stops the call before it is placed, and the refusal is recorded with the value that caused it.
- NORMALIZE E.164 · malformed rejected
- INTERNAL_DNC your suppression list
- DIALABILITY calling window · caps
+1 ••• ••• 4821 · on your internal DNC REFUSED · evidence recordedrun report → reviewed & acknowledged list proceeds
You read the run report before a single number is dialed, and every refusal in it is already an evidence row you can export.
- 5
Records land
Call records, webhooks, CSV, and your CRM, plus an evidence file for every call.
Live call → structured outcome
synthetic transcript- agent ▸ “What’s pushing you to look at this now?”
- lead ▸ “We miss inbound leads on nights and weekends.”
- agent ▸ “That’s exactly the job. When’s good for a walkthrough?”
- lead ▸ “Thursday morning, say 10:30.”
qualified · time captured · deliveredM T W T F→ intent and the time they named, captured as fields
→ available in the workspace, by configured event, CSV, or API
→ evidence file written · exportable
Simulated example. Real outcomes are available in the workspace and through configured signed events, supported CSV jobs, or API reads.
Step four in full, from verifying the subaccount to pointing a number and the signed callback: your carrier, your numbers. What lands in step five: the per-call evidence file.
Your carrier, your rates
Your Twilio rate is the rate you pay
Every production call leaves your own Twilio account: your number, your rates, your relationship with the carrier. Twilio bills those minutes straight to you at the price you already negotiated, with nothing of ours on top. It is also why our minute is priced the way it is: it buys the AI session, not the phone line.
What connecting involves, from verifying the subaccount to pointing a number and the signed callback: your carrier, your numbers. The two ways to buy a phone call, compared as models rather than as vendors: BYO carrier vs resold minutes.
Your account, your numbers
Production calls leave from a Twilio subaccount you own: your numbers, your registrations, the rates you negotiated, and the caller-ID reputation those numbers earn. You connect it and verify it once in the portal. Vocapable runs on Twilio Media Streams, our own stack, and the account underneath stays yours to take anywhere.
Your rate is the rate
Twilio bills you for the minutes, directly, at the price you already negotiated. Our per-minute rate covers the AI session: the model, the speech, the time the agent spends talking. Two bills, both itemized, and the carrier one is between you and your carrier.
Our numbers do one thing
The platform’s own numbers carry one kind of traffic and one only: a paid test call to a number you proved you control. Every other destination is refused at the dialability gate, and the refusal lands in that attempt’s evidence. Code, not a policy page.
You choose the list and the numbers it goes out on. We enforce what is set: the calling window, the frequency caps, the consent standard and the recording-consent class, applied on every attempt and recorded with the exact values that bound the call. That record is what you hand over when someone asks.
Inbound calls, configured for your business
Give callers a useful first answer.
Put an AI receptionist on the Twilio number you already publish. Define your open and closed hours, holidays, timezone, menus, routes, and agent handoff in one answering flow that reflects how your business works.
Your call flow, under your control
Guide callers through menus, ringing your team, AI conversations, voicemail, spoken messages, or forwarding. A reserved inbound connection is used for the AI conversation, while the rest of the flow follows the steps you set.
See the call flow →Follow-up your team can work
When a caller needs help, the agent can capture a message, open a ticket, schedule a callback, or update a known caller's lead. The shared Inbox keeps those requests close to the call that created them.
See the Inbox workflow →Predictable inbound capacity
$250/mo includes 1 concurrent inbound connection, with $150/mo for each additional one. Answered calls add no per-call or per-minute Vocapable fee.
View receptionist pricing →Add Receptionist on its own or alongside an outbound plan. Your inbound connections and outbound sessions each keep their own capacity.
Under every campaign
A CRM built for one job: calling
Campaigns need somewhere to put what they learned, and a general-purpose CRM with a phone bolted to the side is not it. Contacts carry your tags and your own fields. Lists are lists. Import maps your columns and hands back every row it refused. And a contact’s page is that person’s whole history across every campaign you have run, sitting beside the two facts that decide whether they get dialed again: what your do-not-call list holds, and what the dialability check returned.
contact con_01J9…F2K
Product UI · synthetic data
Priya Natarajan
Brightside Clinics · Ops Director
- webinar-q3
- multi-site
- sites: 4
- dialability
- REFUSED · outside the current calling window
- internal DNC
- not suppressed
- consent
- PEWC · your web form
purpose: marketing · America/Chicago, 8:12 PM · calling window and caps applied
read live from your do-not-call list, not from a flag on the row
captured Mar 4 · active
Activity · all campaigns
-
Outbound call · qualified
Q3 multi-site push · Tue 4:31 PM
-
Note · R. Cole
“Wants pricing for two more sites before she commits.”
-
Note · after the call
she asked for Thu 9:00 AM · written on the contact
-
Outbound call · voicemail
Spring reactivation · Feb 9
Exports to CSV · every field here is a /v1 read
What that page holds
One contact, everything that has ever happened to them, and the two facts that decide the next dial.
- Your tags, and the custom fields you invented, on the record itself
- Every call across every campaign, with its disposition, the transcript turn by turn, and the recording your recording-consent class kept
- Notes your reps typed, sitting beside the calls they came from
- Lead status, and the rep the contact is assigned to, on the record rather than in a spreadsheet
- What your internal do-not-call list holds for that number, when it landed there, and the call it came from
- The dialability verdict for the purpose you pick, the reason it refused, and the policy values that decided
- Consent records: class, source, when it was captured, when it expires
Your columns, not ours
Point an import at a CSV and map its columns onto the fields you keep. What survives lands in a list; what does not comes back row by row as JSON or as a CSV you can hand to whoever produced the file: the row number, the column, the value, and the reason. The consent attestation the import was submitted under, named signer and title, stays attached to the list it built.
Filter like you mean it
Every filter is a server filter and every page is a cursor, so a filtered view is the whole filtered set rather than the fifty rows your browser happened to be holding. Then act on what you filtered, up to a thousand contacts per request: add them to a list, take them off one, set lead status, or put the numbers on your internal do-not-call list.
Take it all with you
Contacts, attempts, calls, outcomes, your do-not-call list, your pre-dial results and your usage: nine resources, every one of them a CSV export you start yourself. Recordings come back as short-lived signed URLs, transcripts as ordered turns, dispositions with the whole history of how they changed. Leaving with your data is an afternoon, not a support ticket.
Already have a system of record? Keep it. Drive the campaigns from your stack and let outcomes land where your team already works. Every screen above is built on the same /v1 your engineers get, so anything you have just seen, your code can do too.
Metrics reported per campaign: Contact rate; Qualification rate; Demos requested; Disposition mix; Refusals, by reason; Cost per qualified outcome; Shift confirmations and decline reasons; Cost per completed call; Completed conversations; Structured survey responses; CSAT and NPS views.
From calls to decisions
Measure the work your calls create
Review the outcomes, disposition trends, and usage behind your campaigns. The numbers come from the call, campaign, and usage records that produced them, so your team can trace a dashboard read back to the work.
See the full reporting surface on the metrics we report.
Lead programs
- Contact rate
- Qualification rate
- Demos requested
- Disposition mix
- Refusals, by reason
- Cost per qualified outcome
Workforce calls
- Contact rate
- Shift confirmations and decline reasons
- Cost per completed call
Customer feedback
- Contact rate
- Completed conversations
- Structured survey responses
- CSAT and NPS views
- Cost per completed call
From conversations to next steps
Calls become work your team can see
Calls write their outcomes to records. Use the native Inbox for operational follow-up, or send the same context to the systems your team already uses through signed webhooks, exports, and the API.
A call record you can inspect
Open a call with its outcome and disposition history, plus available evidence such as a transcript, recording, or voicemail. The context stays with the conversation instead of getting lost in a handoff.
See what one record holds →Follow-up in one place
Messages, tickets, and callback requests give people a clear next action. When a caller matches an eligible record, the receptionist can update it too; assign and resolve requests from the operational Inbox.
See the receptionist workflow →Structured outcomes
Keep lead qualification, structured shift confirmations and decline reasons, and survey responses attached to the work. Campaign and survey views make progress, disposition trends, CSAT, and NPS easier to review.
Connect it to your systems
Receive signed call and outcome events, inspect or retry delivery, and use the /v1 API or CSV exports when your team needs the data in its own workflow.
See the API →Records that travel with the work
Calls your team can explain and act on
A call record captures the checks that ran, the signature behind the list, and what happened on the line. Use it to continue the work, investigate a problem, or export the evidence for someone who needs it.
attempt att_01J9…K7Q
Synthetic data
- stages_performed
- normalize · internal_dnc · dialability
- attestation_ref
- agr_01J9…B4T · signed by J. Rivera, VP Ops
- ai_disclosure
- played · before first response
- consent
- PEWC · your web form
- outcome
- qualified · time captured, in their words
- delivery
- webhook call.ended · 200
Every line is written by the platform as the call happens, with the signature that admitted the list attached to it. The file exports exactly as you see it.
Exportable evidence
attempt att_01J9…M2X
Synthetic data
- stages_performed
- normalize · internal_dnc
- result
- STOPPED · internal_dnc
- dial
- REFUSED, never placed
- list_row
- suppressed
- evidence
- recorded · exportable
Your suppression list is checked at import and again at dial time, so the policy decision remains attached to the record.
Refused, and proven
Policy controls that run with the call
Configure the calling policy your team needs, including normalization, your own do-not-call list, calling windows, and frequency caps. The AI disclosure and opt-out handling are recorded as the call runs.
A record your team can use
Made or refused, calls produce an exportable record: the checks that ran, the signature that admitted the list, and what happened on the line. It is written as the call happens, ready for the next person who needs it.
Clear carrier ownership
A published rate card and one bill. Every plan includes the compliance engine at $0, while the carrier leg stays on your own Twilio account at the rates you negotiated.
How each control works, one by one: the compliance engine. What one call's record actually holds, with a sample file to open: the per-call evidence file. Every control on this page in one place: the Trust Center.
Your CRM, or ours
Run it from the dashboards, or never open them.
Workspace
Your contacts, imported or sent through the API, and then everything from the dashboards: lists, campaigns, live boards, and a CRM built for one job, where every call that ever touched a record sits on one timeline with its disposition, transcript, notes and human follow-up context. Vocapable is your calling system of record.
See the CRM →Headless
Keep your stack as the system of record. Product resources use the /v1 API, so your code can create contacts, place calls on your own Twilio, and receive enabled events at your configured signed webhook. Signup, onboarding, and first-key setup run in the browser.
See the API →Same engine, same compliance floor, same pricing. Mix the two freely, per team, per campaign.
Published prices and usage rates. Start free in the sandbox.
Three outbound workload classes, starting at $349/mo with AI usage from $0.13/min - enterprise plans as low as $0.07/min. Inbound answering is priced separately, from $250/mo. Every rate we bill is printed on the pricing page, so the first invoice holds no surprises. Your Twilio minutes stay on your own account at your own rate. The sandbox is free, you pay when you go live, and the compliance engine is $0 on every plan.
Or put your own numbers in and price your own campaign against the published rates, before you talk to anyone.
Your list is sitting there. Call it.
The sandbox is free: your real use case, your real material, the whole dial path running with every gate live. And you hear the simulated demo calls before you sign anything.