Phone numbers and calling, on the roadmap
This page describes what is planned, not what ships. Outbound calls through your own Vapi account and call logging work today; the rest does not.
- Not available today
- Outbound calls work now
- Consent gate part of the plan
The short answer
- The plan: phone numbers held on your instance with inbound routing, business hours, whisper messages and voicemail that arrives as a transcription in the same thread list as email.
- Also planned: a browser softphone with recording, dispositions and power dialling, so a call is logged on the record without anyone typing a note afterwards.
- Available now: outbound calls placed through your own Vapi key with call_start, and the outcome written back with call_log. Nothing answers an incoming call.
What it will do
The intended shape is that a phone number belongs to your instance rather than to a separate telephony dashboard. An inbound call will route by your rules, respect your business hours, play a whisper to whoever picks up, and drop to voicemail that arrives as text in the shared thread list rather than as an audio file somebody has to remember to check.
A browser softphone will let a person dial from the record, with recording, a disposition on hang up and power dialling through a list. The point is that the call becomes a row on the timeline automatically, in the same database as the emails and the deal.
None of that exists. What exists is outbound calling through Vapi, where call_start places the call and call_log writes the outcome onto the record. Those two tools work today and behave like every other tool: the same permissions as a person, and an audit line naming the actor.
What is planned, and why
The call lands on the record
A call that is not logged did not happen as far as the pipeline is concerned. Automatic logging is the reason to have the phone inside the CRM at all.
Read moreOne thread list for everything
Email, voicemail transcription and call notes in the same queue, so a conversation is not split across two tools.
Read moreConsent before the dial
A DNC scrub at audience freeze and a consent gate on call start are planned as part of the feature rather than as advice in a help article.
Read moreHow it will be set up
The planned sequence, for when it ships.
- 1
Connect
A telephony provider connected with your own credentials, held in your instance's vault. Twilio is the planned provider.
- 2
Configure
Numbers, routing rules, business hours, whisper text, voicemail behaviour and the disposition list your team will use.
- 3
Run in review
Any agent involvement, such as a receptionist answering, starts in review like every other agent. Nothing goes on a live line unsupervised.
- 4
Move to auto
Only the classes you decide, after a clean week. Spend stays human-only in every mode regardless.
In which tier
The Local tier is defined around this pack and ships when the pack ships.
| Tier | Price | Phone status |
|---|---|---|
| Core | $299/mo | No phone features. Outbound calls through your own Vapi key work today |
| Local | $499/mo | Defined around phone numbers, SMS and speed to lead. On the roadmap |
| Outbound | $699/mo | Core plus the SMS and phone pack when it ships, plus Campaign and LinkedIn agents |
| Agency | $1,200/mo | Everything above plus marketplaces, data sources and the marketing module |
Published tiers as of September 2026. Seats are unlimited on every tier. Do not buy Local today for a capability that is on the roadmap.
Questions
- Can I get a phone number in SalesCrew today?
- No. Numbers, routing and the softphone are all on the roadmap. The changelog is where a feature becomes real, not this page.
- What can it do with a phone right now?
- Place an outbound call through your own Vapi account and log the outcome onto the record. That is the whole of it.
- Should I buy the Local tier?
- Not for phone features. Local is defined around this pack and ships with it. Core is the tier that is fully live today.
- Will calls be recorded?
- That is the plan, and recording brings consent obligations that differ by state and country. Two-party consent states require all parties to agree. Take your own advice; this is not legal advice.
- Which provider will it use?
- Twilio for numbers, SMS and voice, and Vapi or Retell for the AI receptionist. All of that is roadmap.
Start with the parts that are live
Pipeline, inbox, cadences and the MCP server today, with the phone pack written on the roadmap.