AI voice agents, on the roadmap
What is planned: an agent that answers, qualifies, books into the calendar and transfers to a person. What ships: outbound calls, logged on the record.
- Inbound not available
- Outbound calls work now
- Transfer rule part of the design
The short answer
- The plan: an inbound receptionist through Vapi or Retell that answers, asks a short set of qualifying questions, books an available slot and transfers to a human on the triggers you define.
- Nothing inbound works today. Outbound calls through your own Vapi account, started with call_start and logged with call_log, are the whole of the voice capability that ships.
- The design decision that matters most is when the agent stops. A voice agent that improvises a price or keeps talking to someone with an emergency is worse than a voicemail, so escalation is written as literal triggers rather than as judgement.
What it will do
The intended behaviour is narrow on purpose. Answer, find out what the caller needs, take a name and a number, offer two slots from the real calendar, and transfer to a person on anything outside that. Narrow is what makes a voice agent reliable; broad is what makes it embarrassing.
Its facts will come from the knowledge base rather than from a prompt someone pasted in six months ago. That means your service area, your hours and your terms live in one place and the agent cannot drift from them, and it refuses rather than guesses when asked something outside the list.
Everything it does will land in the same database as the rest: a contact, a meeting, a call record on the timeline, and an audit line naming the agent as the actor. A booking that lands nowhere is the failure mode this design exists to avoid.
What is planned, and why
It books into a real calendar
A meeting record, a contact and a source, in your database. Not a transcript in a separate dashboard.
Read moreIt transfers rather than improvises
Escalation written as literal trigger phrases, so an emergency reaches a person immediately.
Read moreIt starts in review like every agent
Modes, guardrails, an audit log and one kill switch that stops every agent at once.
Read moreHow it will be set up
The planned sequence.
- 1
Connect
A voice provider with your own key in your instance's vault, and a phone number, which is itself a roadmap item.
- 2
Configure
The facts it may state, the refusal rule, the escalation triggers and the booking flow. The prompt pack publishes a full working structure for this.
- 3
Run in review
Listening to real calls before it books anything unattended. Every agent ships in review, and voice is the one where that matters most.
- 4
Move to auto
Only after the refusal and escalation behaviour has been tested against real callers. Spend stays human-only regardless of mode.
In which tier
The receptionist ships with the local-services pack.
| Tier | Price | Voice status |
|---|---|---|
| Core | $299/mo | No voice agent. Outbound calls through your own Vapi key work today |
| Local | $499/mo | Defined around the phone pack including the receptionist. On the roadmap |
| Outbound | $699/mo | The phone pack when it ships, plus Campaign and LinkedIn agents |
| Agency | $1,200/mo | All agents, plus marketplaces, data sources and the marketing module |
Published tiers as of September 2026, unlimited seats on every one. Voice minutes are paid to your own voice provider and are not bundled into these prices.
Questions
- Can it answer my phone now?
- No. Inbound answering is on the roadmap and SalesCrew has no phone numbers today. If you need a receptionist this month, use a standalone voice platform.
- Which providers are planned?
- Vapi and Retell for the inbound receptionist. Vapi already works for outbound calls with your own key.
- What will a minute cost?
- Whatever your voice provider charges, paid to them. The components are platform fee, model, text to speech, speech to text and telephony, and the calculator page publishes the formula.
- Should it say it is AI?
- Several jurisdictions are moving that way and it is the safer default everywhere. Decide with your own counsel and write the answer into the prompt. This is not legal advice.
- What stops it inventing a price?
- A refusal rule that names the exact words to use when it does not know, and a fact list it may not generalise from. That is prompt design, and the prompt pack publishes a working version.
Build the database the agent will book into
Pipeline, calendar and knowledge base are live now; the voice half is written on the roadmap.