Product · The AI receptionist
Your number, configured around your business
$250 a month puts an AI receptionist on the number you already publish, on the Twilio account you already own. You write what it does: a menu, your own reps, the agent, a voicemail. Answer fifty calls this month or five hundred, and the Vocapable price is the same.
You write what happens, step by step
One answering document per number, holding two ordered chains: one for your open hours, one for everything else. Your hours and your holiday dates, in your own timezone. Six kinds of step, in any order you like.
- 1
A keypress menu
Speak the options, read the key they press, follow that branch. Menus nest four levels deep, and you write the branch for the caller who presses nothing.
- 2
Ring your own people
Your reps, in the order you listed them. Destinations resolve at the moment the call is built, so the rep who changed their number this morning still gets the call.
- 3
The AI agent
Hands the caller to a published version of your agent, which answers in English from the material you gave it. This is the step people mean when they say receptionist.
- 4
Voicemail
Takes a message and keeps the audio on the call record with the rest of that call’s evidence. You press play.
- 5
A spoken message
Say one thing and hang up. It is the fastest closed-hours answer you can publish.
- 6
Forward
Bridge the caller straight to a number you chose. Your carrier carries it, and it claims none of your connections.
You have room for sixty steps across both chains and menus four levels deep, and the editor holds you to that when you save. A caller never finds the edge of it.
Business knowledge and caller requests
Keep the receptionist informed, and keep follow-up visible
Give the agent reviewed business facts, then turn the calls that need a person into work the right teammate can see. The knowledge and request workflow lives alongside the answering flow, not in a separate system.
Reviewed business knowledge
Build facts from documents or website source snapshots, review what belongs in the receptionist, and keep the business information your callers need in one place.
Preview, then publish
Preview the reviewed facts an agent version will use, then publish a version you can trace. Published versions stay tied to the knowledge and configuration they were released with.
An Inbox for caller requests
The agent can capture messages, open tickets, schedule callbacks, or update a known caller's lead. Your team can assign and resolve those requests from the operational Inbox.
Release control
Change the answer with evidence, not guesswork
Author regression cases for the questions that matter to your business and keep release evaluation evidence with the version you publish. Each release has a traceable configuration, knowledge set, and proof of what was checked.
A recoverable version history
Published agent versions are immutable. When a compatible healthy version needs to return, the platform can restore it with the matching configuration rather than recreating the receptionist from scratch.
Only one of those steps costs you a connection
Menus, rings, forwards and spoken messages run on the carrier leg and claim none of your connections. That is why one connection can publish an answering flow far larger than the concurrency you bought: most of the flow costs you nothing to hold.
The AI step is the one you are actually buying. It claims a reserved inbound connection for as long as the conversation lasts, and gives it back the moment the caller hangs up.
What claims a connection
- AI The agent conversation. One connection, for as long as it lasts.
- MenuNone.
- RingNone.
- VoicemailNone.
- SayNone.
- ForwardNone.
Your carrier still bills you for those seconds, at the rate you already pay it.
What a connection actually buys
Reserve inbound capacity for your receptionist
A connection you buy is held for your inbound AI flow from the moment its charge clears, including while your own dialer is running at full pace. It is held whether or not anyone is on the line, so inbound and outbound capacity stay distinct.
When a caller arrives while your connections are busy, the call keeps moving: it advances to the next step you wrote down, which is usually your own voicemail. What happens then is the thing you chose, which is why the last step in the chain is the one worth writing carefully.
The whole price, on one line
The plan
$250/mo
Includes 1 concurrent inbound connection on the number you already publish.
Each additional connection
$150/mo
In any quantity. Each one lets one more caller talk to your agent at the same moment.
On its own, or attached
Receptionist answers the phone. Attach it to an Engage, Workforce or Sales subscription when you want the agent placing calls too, for the same monthly money. Inbound connections and outbound sessions never draw from one another.
The plan plus your connections is the whole Vocapable invoice. The calls it answers add nothing per call and nothing per minute, so a busy month and a quiet one come to the same number. Carrier minutes stay where they already are: on your own Twilio bill, at the rate you negotiated.
Adding a connection charges a full month for it up front, whatever day of the period you buy on, and the checkout shows you the exact amount and the exact date your subscription next renews before you agree. The line goes live when that charge clears. A connection you already hold keeps its grace period, so one failed card does not take your receptionist off the phone.
The trust close
Every answered call leaves a file you can hand to somebody
Four controls run on a call you answer exactly as they run on a call you place, and no setting in your answering document can knock them out of place: the AI disclosure plays before the first model token, an opt-out is heard and written to your internal do-not-call list, that list suppresses, and numbers are normalized before anything reads them.
The checks that belong to outbound calling are recorded with the reason they do not apply, so the file explains itself to whoever reads it next. A check that did not apply never reads as a check that passed.
Recorded on an answered call
- AI disclosure: played before the first model token.
- Opt-out: heard, and written to your internal do-not-call list.
- Suppression: that list applied before the next contact.
- Numbers: normalized before anything reads them.
- The controls that belong to outbound calling: written down with the reason they did not apply, because this caller dialed you.
Read the whole shape of a call’s record on the Trust Center.
Where a connection earns its money
Three moments in an ordinary week, and the same one line covers all of them.
Nine at night
Your closed-hours chain picks up. A spoken message, a menu, or the agent taking the whole enquiry. In the morning the call record is waiting for you.
While your reps are talking
One caller is already on with your team. The next one reaches the agent, because ringing your own people claims none of your connections.
The question you answer all day
Hours, address, what you charge, what you do. The agent answers it off the material you gave it, in your words, and hands over anything you want a person for.
What getting started actually looks like
Three steps, and the middle one is your carrier’s. See pricing for the plan itself.
1 · Verify your Twilio account
Your own subaccount, your own credentials, connected once. Start here: it is the step with the most waiting in it.
2 · Point your number at us
The number you already publish, aimed at a signed webhook. Point it back whenever you like. It stayed yours the whole time.
3 · Write the steps, buy the line
Compose the whole answering document first, then buy the connection from Billing that lights up the AI step.
Questions people ask first
Do I need my own Twilio account?
Yes, and it is the reason the price reads the way it does. The receptionist answers on your own Twilio subaccount and the number you already publish, so the carrier relationship, the registrations and the caller-ID reputation stay yours, and the minutes stay on the bill you already negotiated.
What happens when every connection is busy?
The call keeps moving. The caller advances to the next step you wrote down, which is usually your own voicemail, so what happens next is the thing you chose to happen next. It is worth writing that last step with some care.
Can I run outbound campaigns on a Receptionist plan?
Receptionist is the inbound plan: it answers the phone. When you want the agent placing calls as well, attach the receptionist to an Engage, Workforce or Sales subscription for the same monthly money. The inbound connections and the outbound sessions never draw from one another.
How do I hear a message somebody left?
You press play on the call record. An inbound voicemail is kept there as audio, alongside the rest of that call’s evidence.
What is on a Receptionist invoice?
$250 a month, plus $150 for each connection you added. That is the list. The calls it answers add nothing per call and nothing per minute, so a busy month and a quiet one cost you the same. Carrier minutes stay on your own Twilio bill, at the rate you negotiated.
Build it before you buy it
Write the whole answering document in a free sandbox, before a number points anywhere. Weighing it against a per-call answering service? The two models, compared.