CRM
Receptionist
Conversation overview Last 14 days
Lead source
Recent operations
Activity feed — what the receptionist actually did
- No activity yet.
Launch Control
First client onboarding
One guided flow for getting a customer from signup to a tested live receptionist.
Onboarding checklist
Access
Team & roles
Invite users, review active sessions, and manage API keys with role-safe controls.
Invite teammate
Create API key
Invitations
Sessions
API keys
Audit Trail
Actions
Every recorded receptionist, workflow, routing, lead, escalation, and system action for this tenant.
Action log
Calls & conversations
Every conversation across voice, SMS, and web chat. Click a row for the transcript.
Leads
Project Intake Packages built during conversations — not voicemails.
Customers
Contacts the Customer Brain recognises on future calls.
Projects
What the receptionist can speak to once a caller is verified.
Pipeline
Appointments
Booked by the Scheduling Agent during live conversations, lead conversion, or manual office follow-up.
Schedule
Escalations
Urgent situations the receptionist stopped and handed to a human.
Results
Two kinds of number live here and they are never mixed. Counted means we can show you the calls behind it. Estimated means we multiplied a counted number by something we assumed — and every one says what it assumed.
Period
Counted from your own records
Estimated assumptions applied
The assumptions behind those estimates
Leave a box empty to keep our figure. Anything you fill in is used instead, and every estimate above says which of the two it used.
Conversations
How they ended
Leads and escalations
Workflows
What happens after the call — the follow-up text, the lead handed to a salesperson, the emergency paged to a superintendent.
Your workflows
Recent runs
Every run keeps a per-step record — this is the answer to “why did that text go out?”
Receptionist Setup
Knowledge
Company services, FAQs, policies, custom instructions, and documents the receptionist can use.
Knowledge lanes
Organize what the receptionist can use by source. Uploads still land in one searchable knowledge base, but these lanes make setup clearer for customers.
Upload documents
Custom instructions
Use this for behavior rules: what the receptionist should always do, never say, when to transfer, and how to handle uncertainty.
Knowledge sources
Services
Team & routing
FAQs & policies
Phone numbers
Choose which receptionist answers each number before it goes live. Vapi can remain the live voice source while optional carrier numbers are purchased and assigned here.
Get a new number
Pick country, number type, area code, or memorable digits.
Choose one available number and hold it for review.
Choose the receptionist or agent that answers first.
Confirm the recurring charge, attach the route, then test the line.
Number routing
Your numbers
Keep the number you already have
The number on your trucks and your yard signs can move here. It takes days and two carriers have to agree, so nothing on this page will ever tell you it has moved until the carrier confirms it.
Before you start — what to have in front of you
Numbers you are moving
Start a port
Everything below comes off a recent bill from your current carrier. It is saved as a draft first — nothing is sent to anyone until you submit it.
Connections
Integrations
Connect the receptionist to the systems that receive leads, messages, appointments, and alerts.
Customer channels
Website chat embed
Launch Control
Customer Go-Live Checklist
Automated launch checks plus the human approvals that still matter before a customer goes live.
Phone number assignment
Assign an existing number to this receptionist or buy a new number. Buying a number starts a recurring carrier charge and configures it to point at this deployment.
Owned numbers
How to use this page
Automated checks prove the platform can see required configuration and recent test evidence. Review checks are deliberately manual: they are approvals for voice quality, policy accuracy, emergency language, workflow copy, and customer sign-off.
Automation
Event feeds
Send real-time events to CRMs, dispatch boards, Zapier/Make, reporting tools, or your own software.
What this page is for
Event feeds are outbound webhooks. When something important happens in the receptionist, the platform queues a signed JSON delivery to systems you choose. This is how a lead can appear in a CRM, an emergency can hit a dispatch board, or a completed conversation can enter a reporting warehouse.
Where we send events
Signing secrets are not listed here. Each one is shown once when you add the endpoint and is never readable again — not by this console, and not by the API.
Supported events
Add an endpoint
Recent attempts
This is the answer to “did you actually send it?”. Anything still retrying will pick itself up on its own — a restart does not lose it.
Test your receptionist
A real conversation through the same engine that answers the phone.
Try: “There’s water coming through the ceiling at 1458 Oak Street” · “I need a deck built, about 16 by 24” · “I’m calling about my kitchen renovation”
Settings & deployment
Brand, non-live status controls, and the exportable configuration package. Live launches are managed from Go-Live.
Config sanity check
AI rep studio
Configure the receptionist persona, voice behavior, languages, and guardrails. These settings are saved into custom instructions, so the phone assistant, web chat, and knowledge search all receive the same operating rules.
Brand colors
These colors are saved into the receptionist package and used by the console, website chat widget, and customer-facing messages where supported.
Export & import
The package contains this company’s configuration only — no platform code, and no credentials.
Raw configuration
Create AI Receptionist
Eleven steps. Everything except the company name has a sensible default, so you can go live and refine later.