Recovering a missed call

A missed call becomes a record, the caller gets a text back, and the reply lands in the same inbox your team already works.

An admin approves every new account by hand. Nothing is created until then. We reply by email; no newsletter, no sequence.

Want to see it first? Book a demo

  • Text-back on every missed call
  • Consent and STOP built in
  • One thread per caller
app.salescrew.io/today
The daily working view

The short answer

  • In SalesCrew, an unanswered call on your business number creates a call record, and the caller gets a text offering to book or to answer a question.
  • SalesCrew phone numbers route by your business hours, transcribe voicemail and put the call, the text and any reply in one thread beside your email.
  • Every text runs through consent and STOP handling, and every action is written to the audit log with the actor named.

Trigger to logged

What happens from the moment a call goes unanswered.

  1. 1

    Trigger: an unanswered call

    A call arrives on a number held in your SalesCrew instance and nobody picks up. Your routing rules decide who rings first and when the call counts as missed.

  2. 2

    A call record is written

    The number, the time and the outcome land on a contact. If the number is new, SalesCrew creates the contact for you.

  3. 3

    The text-back sends

    The caller gets your short message from the same number they dialled. Consent handling and STOP processing run first, so nothing goes out blindly.

  4. 4

    Your team sees one thread

    The missed call, the voicemail transcript, the outgoing text and any reply sit in the same thread list as your email.

  5. 5

    A reply becomes a booking or a task

    If the caller writes back, your team picks up the conversation in the inbox. Reminders and no-show recovery run from the same thread once a time is booked.

  6. 6

    What gets logged

    The call, the message, the consent state and every later touch, with the actor named in the audit log.

What gets configured

What you set for each object in your SalesCrew instance.

ObjectWhat you set
Phone numberA number on your instance with routing rules
Business hours and after-hours behaviourWhen a person answers and what happens otherwise
Text-back messageThe wording sent to a missed caller
Consent and STOP handlingOpt-out processing on every message
10DLC registrationCarrier registration for business texting in the United States
Voicemail transcriptionVoicemails readable in the thread list
Outbound callsVapi as the provider, with call_start and call_log
Audit logThe actor recorded on every action

Where it stops and a human starts

The text-back does one job. It acknowledges the call and offers a booking link, and anything past that goes to a person on your team.

Consent is part of the mechanism, not an afterthought. Texting a consumer mobile in the United States brings the TCPA into it, business texting needs carrier registration, and STOP has to work every time. SalesCrew runs that machinery on every message, while the consent itself is yours to hold. This page is not legal advice.

You'll want the history in one place from day one. Every call outcome is logged with call_log, so a caller who rang twice last month shows up with both calls on the record.

Questions

What does the caller get after a missed call?
A short text from your business number offering to book a time or answer a question. You write the wording once in SalesCrew. Consent and STOP handling run on every message, so a caller who opts out is never texted again.
Can I connect my own texting tool?
Yes. Outbound webhooks push a SalesCrew event to the tool you already use, and the contact record keeps the history of every touch.
Which plan includes phone numbers and SMS?
The Outbound plan at $699 a month includes the phone and SMS pack, with unlimited seats. The pricing page lists every plan and what each one includes.