Calls belong beside the pipeline

Outbound calls through Vapi, phone numbers, text-back and an AI receptionist, all writing to the same database your team already works.

Want to see it first? Book a demo

Unlimited seats
Your own database
Consent gate on every call

app.salescrew.io/today

The short answer

SalesCrew places outbound calls through Vapi and logs each one against the contact it belongs to.
The phone and SMS pack adds phone numbers, two-way SMS, missed-call text-back, a browser softphone and the AI receptionist.
The same pack scrubs do-not-call numbers when an audience is frozen and checks consent before any call starts.
A voice agent needs a database behind it. SalesCrew is the CRM the voice agent books into.

What the phone side does

Calls run as a channel beside email, LinkedIn and inbound. A call starts from the app or through the call_start tool, and the outcome is logged against the contact with call_log. Bookings from Calendly arrive as meetings, linked to the contact and the deal.

The phone and SMS pack adds phone numbers and inbound routing with hours, whisper and voicemail transcription. Two-way SMS runs through Twilio with templates, consent handling and STOP processing. A missed call gets a text back. A softphone in the browser records calls, takes dispositions and power dials a list. The AI receptionist answers, qualifies, books and transfers. Reminders and no-show recovery send by SMS and email.

The rest of this page is the design underneath: why a voice agent needs a database behind it, and how each piece writes to the same records your team already works.

The seven phone jobs

Each job writes its result to the contact, the deal and the timeline.

Answer after hours

An AI receptionist picks up, qualifies the caller, books into the calendar and transfers a live one to a person. Vapi or Retell is the inbound provider.

Text back a missed call

A missed call triggers an SMS within seconds, so the caller who was about to try the next company on the list replies to you instead.

Reach a new lead fast

Speed-to-lead actions on a new inbound: an automatic SMS reply, an AI callback, round-robin assignment, and an escalation when nobody has touched the lead in time.

Work a call list

Outbound calls run through Vapi. A browser softphone adds recording, dispositions and power dialling for the person working the list.

Log and transcribe

Every call is logged against its contact. Voicemails are transcribed, and calls sit in the same thread list as email.

Remind and rebook

Reminders go out at 24 hours and 2 hours before a meeting. A no-show gets a recovery message with a reschedule link.

Choose a voice platform

SalesCrew runs Vapi in production for outbound calls, with Retell as the inbound receptionist option. Picking a voice platform is a separate question from the CRM behind it.

How a phone lead flows

Six stations, each writing to the same records.

1
The call arrives
A number is routed by business hours. Inside hours it rings your team; outside them the receptionist answers.
2
The caller is qualified
Name, reason for calling, address or company, urgency. The receptionist works from your knowledge base, so the answers sound like your business rather than a generic script.
3
A booking is made or a person is fetched
The agent books into the same calendar your team uses, or transfers a caller who needs a human. Bookings land as meetings, including those made through the Calendly webhook.
4
A confirmation goes out
An SMS with the time and a reschedule link, then reminders at 24 and 2 hours.
5
The record is written
The contact, the call, the transcript and the booking land in your own database as linked rows.
6
The follow-up runs
A no-show enters a recovery cadence; a completed job enters a review request. Cadence steps run as email, LinkedIn queue items, SMS and call tasks.

Why a voice agent needs a CRM behind it

A voice agent on its own is a good demo and a poor system. It answers, it sounds fine, and then the call ends and nothing happened. The reason is that a voice platform is a conversation engine, not a record of your business.

Three things go wrong without a database behind it. The agent does not know who is calling, so a customer of four years is treated as a stranger. The booking it makes lands in a calendar and nowhere else, so no one follows up when the caller does not show. And the call itself leaves no trace on the contact, so the next person who speaks to them starts from zero.

Put a CRM underneath and each of those closes. The agent can look up the caller before it speaks, because contact_search is a tool it can call. The booking becomes a meeting linked to a contact and a deal. The call is logged with its outcome on the same timeline as the emails. And the follow-up is a cadence that runs whether or not anybody remembers.

This is where dual-control earns its keep. Every action a voice agent needs is an MCP tool, and every one of those tools has a screen twin. The agent is not calling a private back door; it is doing exactly what a person in the app would do, under the same scopes, with the same audit row written afterwards.

SalesCrew is the database the voice agent books into, so every call leaves a clean record behind it.

Consent, do-not-call and recording

Phone contact is the most regulated channel in the product, so the controls sit in the design itself.

Two controls are built in. A do-not-call scrub runs when an audience is frozen, in the same place the email suppression list is applied, so a number on a DNC register drops out before a list becomes callable. And a consent gate sits on call_start: the tool that begins a call checks for a recorded consent basis rather than trusting the list.

The obligations themselves stay with you. In the United States the TCPA governs calls and texts to mobile numbers and carries statutory damages per message, which is why cold SMS to consumer mobiles is a poor idea without clear consent. Application-to-person SMS in the United States also requires 10DLC registration of your brand and campaign with the carriers before traffic flows. Call recording law varies by state: some require only one party to consent, others require every party on the call, so a recorded call across state lines needs the stricter rule. A lawyer who knows telephony rules in your markets is worth the hour before you dial.

The product makes the mechanical parts hard to skip: the scrub at freeze, the gate at call start, STOP handling on SMS, and an audit row for every call an agent begins.

This page is not legal advice

TCPA, 10DLC registration and call-recording consent rules differ by country and by state, and they change. Get advice covering the markets you call before you run a phone campaign.

Who the phone side is for

A strong fit when

Your outbound calling runs through Vapi and you want those calls logged against real contacts.
Email, LinkedIn and inbound already feed the pipeline and you want the phone in the same place.
You want a voice agent that can look a caller up, and you need the database that makes that possible.
Missed calls cost you jobs and a text back within seconds would win them.

What the phone and SMS pack brings

Phone numbers routed by business hours, with the AI receptionist outside them.
Two-way SMS with templates, consent handling and STOP processing.
Missed-call text-back and reminders that send at 24 and 2 hours.
A browser softphone with recording, dispositions and power dialling.

Which tier covers phone and SMS

Per month, unlimited seats on every tier.

Tier	Price	Phone and SMS
Core	$299/mo	Outbound calls through Vapi as a channel, call logging against contacts, and inbound bookings from Calendly landing as meetings.
Local	On the pricing page	Core plus phone numbers and inbound routing, two-way SMS, missed-call text-back, speed-to-lead pools, reminders and no-show recovery, review requests, forms, quotes with payment links, and the Inbox and speed-to-lead agents in review. Telephony and SMS billed at cost plus 20 percent.
Outbound	$699/mo	Core plus the SMS and phone pack, the Instantly send provider and the Campaign and LinkedIn agents. Allowance of about 25,000 model calls a month.
Agency	$1,200/mo	Outbound plus marketplaces, data sources, the marketing module and every agent. Allowance of about 60,000 model calls a month.

Prices verified 3 September 2026, in US dollars, per instance.

What phone-first businesses ask

What can I do with calls in SalesCrew?: Start outbound calls through Vapi from the app or the call_start tool, and log every outcome against the contact with call_log. The phone and SMS pack adds phone numbers, inbound routing and the AI receptionist.
How does SMS work?: Two-way SMS runs through Twilio, with templates, consent handling and STOP processing. Missed-call text-back is part of the same pack.
Which voice provider do you use?: Vapi for outbound calls, which SalesCrew runs in its own production setup. Retell is the option for the inbound receptionist. Twilio carries numbers, SMS and the browser softphone.
How are minutes and messages billed?: Telephony and SMS are billed at cost plus 20 percent, on top of the tier price. That is a pass-through model, so you pay for the minutes and messages you use. The AI allowance is separate and metered by model call.
Will the AI call people on its own?: Only when you decide it should. Any external action from an agent, a call included, defaults to review, and anything that spends money is human-only regardless of mode. The consent gate on call_start adds a second check before a call begins at all.
What about do-not-call lists?: SalesCrew scrubs do-not-call numbers when an audience is frozen, in the same place email suppression is applied, so a registered number never reaches a call list.
Can I record calls?: Yes, the browser softphone records calls. Consent law varies: some states need one party's consent and others need everyone on the call, so a call that crosses state lines follows the stricter rule.
Can a voice agent I already run book into SalesCrew?: Yes, and that is the design. Every action in the app is also an MCP tool, so a voice agent can look up a contact, create a meeting, log the call and add a note using the same tools and scopes a person has. Outbound webhooks push events the other way.

Put the phone in the same database as the pipeline

Fourteen days to try it. Contacts, pipeline, inbox, cadences and outbound calls through Vapi in one instance.