Missed-Call Text-Back: How It Works with Landlines, VoIP & Any Carrier
Key takeaways
Missed-call text-back is an automation: when a call to a business goes unanswered, a text is sent to the caller within seconds, and the caller is recorded as a new lead — without anyone on staff doing anything.
Whether the text is delivered depends on the caller's number, not on the business's phone carrier. Mobile numbers receive it. Standard landlines never do. VoIP numbers are split — app-style ones (Google Voice and similar) usually work; the ones wired into an office phone system usually don't.
A number's type cannot be told by looking at it. Because of number portability, the area code and prefix say nothing about whether a number is a mobile, a landline, or VoIP. A real-time carrier lookup is the only reliable check.
Sending automated texts to US numbers also requires A2P 10DLC registration — a carrier-mandated approval of the business and the message program behind the sending number. Until it is in place, the rest of the workflow still functions: the missed call is still captured and recorded as a lead; only the outbound text waits.
Setup routes a business's inbound calls through a number the messaging platform can see. That is done by porting the existing number, adding a new tracking number, or forwarding unanswered calls. The full process is at the bottom of this page.
What missed-call text-back is
Missed-call text-back is an automated workflow that runs when an inbound call to a business is not answered. In its complete form it does four things, in order, within a few seconds:
Detects the missed call. The phone system reports that a call rang and was not answered.
Identifies the caller. It reads the caller's phone number and matches it to an existing customer record, or creates a new one.
Texts the caller back. It sends a short SMS in the business's name — for example, "Sorry we missed your call, reply here and we'll get right back to you" — sometimes with a link the caller can tap to book a time.
Records the lead. It opens an entry in the business's CRM or pipeline at a "new" stage, so the missed call appears alongside other work in progress rather than in a call log nobody reads.
Steps 1, 2, and 4 are carrier-independent and consistent. They happen the moment call data reaches the software. Step 3 — the text — is the part with conditions, and those conditions are the subject of this article.
Businesses adopt missed-call text-back because, in fields where the phone is still the main way work comes in, a meaningful share of calls go unanswered during working hours, and published call-data studies find that most callers who don't reach a business do not leave a voicemail and do not call back. An automatic reply gives those callers a way back into the conversation. That is the goal; the rest of this article is about what has to be true for the text to actually arrive.
The trigger depends on the number, not on tapping the phone line
A common misunderstanding is that missed-call text-back "connects to your phone" the way an app connects to a calendar. It does not. No missed-call system reads calls off an arbitrary phone line. There is no integration that monitors calls on a random number's existing carrier — a cell plan, a cable-company business line, an old copper landline — and reports missed calls to software. That capability does not exist for a number the platform does not control.
For any missed-call system to work, the business's inbound calls have to flow through a phone number on a programmable telephony platform (Twilio is the common one; there are others). That number rings the business's real phone. When a call is not answered, the platform reports the missed call to the software over a webhook. That report is the trigger.
There are three ways to route calls through such a number:
Conditional call forwarding: The carrier forwards calls to the new number only when the line is busy or unanswered. The platform catches the forwarded calls. Keeping the existing number and avoiding a port. Forward-on-no-answer behaves slightly differently on each carrier, and the number the reply is sent from needs checking.
Port the existing number: The business's published number is moved onto the telephony platform. Callers dial the same number; every call is now visible to the system. Businesses whose number is on vehicles, signage, and years of reviews. Takes several business days and a formal port request. After porting, the platform is the carrier for that number.
Add a new tracking number: A new number is provisioned and published on the website, Google Business Profile, and ads. It rings the real phone.New campaigns, or a low-commitment trial without touching the main line.The old number still works but is not tracked. Listings have to be updated.
None of this is blocked by any carrier. Conditional call forwarding is a standard feature on essentially every US mobile and landline plan. But it is a configuration step, and in two of the three options it involves a decision about the phone number. "Plug in your existing phone and it works" is not how the technology functions.
Line types: why the same feature works for one caller and silently fails for another
Once a call is captured, the deciding factor for the text is what kind of number the caller dialed from. There are three broad categories and several edge cases.
Mobile numbers — the text arrives
A caller on any US mobile carrier — AT&T, T-Mobile (including Metro, Mint, and other T-Mobile resellers), Verizon, UScellular, and regional carriers — will receive the text once the sending number's registration is complete. This is the common case and the one the feature is designed around. The caller's specific carrier needs no setup; national A2P registration covers all of them at once.
Landlines — the text is never delivered, and it fails quietly
A standard landline cannot receive SMS. SMS — Short Message Service — is a mobile-network protocol. A copper or fiber landline terminating in a desk phone has no inbox for a text. When a system sends an SMS to a landline, the message is either rejected by the network or accepted and then dropped. Either way, no one sees it, and nothing on the sending side looks broken. This is the failure mode that makes a naive implementation quietly disappointing: the dashboard says "sent," the caller got nothing, and there is no signal that anything went wrong.
Two nuances people raise:
"Text-enabled landline" services exist. Some providers can attach SMS to a business's own landline number. That is something the receiving business sets up for its own number. It does nothing for a person who dialed in from an ordinary landline.
Some carriers "read" a text to a landline aloud. A few landline carriers convert an inbound SMS into an automated voice call that reads the message to whoever answers. It is uncommon, disruptive, and not something to depend on.
The correct handling for a landline caller is: do not send the text, still record the lead, and log the reason — so staff know to return the call rather than wait for a reply that will not come.
VoIP numbers — it depends, and the distinction is technical
VoIP — Voice over Internet Protocol — means the call travels over the internet rather than a traditional phone line. VoIP numbers split into two kinds that behave differently for SMS:
Non-fixed VoIP — numbers not tied to a physical address: Google Voice, TextNow, app-based lines, softphones. These are usually SMS-capable, so a caller using one will typically get the text.
Fixed VoIP — numbers tied to a location and provisioned through a business phone system or a cable company's telephony service. These are often not SMS-capable at the endpoint and behave like a landline for messaging.
A single business VoIP deployment can include both, and the number itself does not reveal which.
Toll-free, short codes, and international
Toll-free numbers (800, 888, 877, 866, 855, 844, 833) can be text-enabled, but through a separate approval path — toll-free verification, not A2P 10DLC. This is relevant only if the sending number is toll-free; a caller almost never dials in from one.
Short codes (5–6 digit numbers) are a different product used for high-volume one-to-many messaging, and are not part of missed-call text-back.
International numbers — A2P 10DLC is a United States framework. A caller with a non-US number is outside it. Canada has its own rules; other countries vary. For a local business this is a small share of calls, but it is a real gap.
Line type cannot be inferred from the number
Before number portability, a number's type could be roughly guessed from its area code and three-digit prefix (the "NPA-NXX"). That has not been reliable since the early 2000s. Local Number Portability lets a person carry the same number from a landline to a mobile to a VoIP app and back. Blocks of numbers that were "landline" prefixes now hold ported mobiles, and the reverse. The only trustworthy way to know a number's current type is a carrier lookup — a real-time query against the number's serving carrier that returns its line type and carrier name.
How a robust implementation handles each case
Regardless of vendor, a well-built missed-call system should:
Run a line-type lookup on the caller's number before sending anything. The result routes the workflow:
Landline → suppress the text. Still create the contact and the lead, and log the reason (for example, "Landline — no text") so it is visible and staff call back.
Fixed VoIP → treat like a landline: lead created, text suppressed, logged.
Non-fixed VoIP or mobile → send the text.
Unknown (the lookup is unavailable, the number is malformed, or lookups are not enabled) → err toward sending. A missed text is worse than a skipped one.
Listen for delivery-status callbacks from the carrier network. If a message that was sent comes back "undelivered" or "failed" — because a number changed hands, or the caller had blocked texts from that number — that outcome should be written to the same log, so an after-the-fact failure is visible rather than silently assumed successful.
A line-type lookup costs a fraction of a cent per number. In a managed service it is handled by the provider and is not something the business configures or pays for separately.
The other requirement: A2P 10DLC registration
Even for a mobile caller, one more thing has to be true before an automated text will deliver in the United States: the sending number has to be registered under A2P 10DLC.
A2P 10DLC stands for Application-to-Person messaging over 10-Digit Long Codes. In plain terms: it is the system the US mobile carriers created to approve automated business texting that comes from an ordinary 10-digit phone number. It has two parts:
A brand — the company doing the sending, verified against public business records (legal name, tax ID, address).
A campaign — a description of what is sent and why: the message category (here, customer care), sample messages, how people opt in, and the STOP/HELP language.
Once a brand and campaign are approved and the sending number is attached, texts route across all major US carriers. Unregistered automated texts from a 10-digit number are heavily filtered — AT&T and T-Mobile in particular block most of it — which is why an unregistered missed-call text-back "silently does nothing." Registration is not optional; it is the cost of using the channel.
Practical points:
Registration can be handled for the business or by the business. In a managed service the provider operates the brand and campaign the number sends under, and the business files nothing. In a self-serve setup the business registers its own brand and campaign through the messaging platform.
Approval takes time and is not fully controllable. Carrier vetting can take days to weeks, and campaigns are sometimes returned for wording changes. This is a known industry friction, not specific to any one vendor.
Throughput is metered by a trust score. Each carrier sets a daily message limit for a campaign based on how thoroughly the brand was vetted. For a single business sending a handful of text-backs a day, the default limits are far more than enough; it only matters at large scale.
There are carrier fees. US carriers charge small per-message surcharges and campaign fees for A2P traffic. In a subscription product these are typically absorbed into the flat price.
If capture works but texts do not send: the sending number's A2P registration is most likely still in carrier review. This is common. It resolves once approval lands, with no change needed on the business's side, and it does not affect call capture — the missed call is still recorded and still becomes a lead in the meantime.
Compliance: consent, STOP, and message frequency
This section is general information, not legal advice. A business should consult its own counsel about its situation.
The reply is a response, not a broadcast. A person who just called a business has initiated contact. Replying to that person by text is a customer-care response — a different category from unsolicited marketing texts to a purchased list.
Every message should carry opt-out language. Standard practice is to append "Reply STOP to opt out," with STOP / HELP / START keywords handled at the carrier level. Once someone replies STOP, the network itself blocks further messages from that number to them.
Consent settings vary by product. Some systems can require captured SMS consent before any customer text, with a documented exception for the inbound caller because they just called. Whether that exception is active is a setting.
Do not stack messages. A repeat caller who already received a text-back for an open lead should not get another for the same lead. A good implementation de-duplicates: one text per caller per open opportunity, not one per ring.
Consider the hour. Automated texts late at night invite complaints and opt-outs. If calls come in around the clock, a send window is worth configuring.
Other real-world limitations and edge cases
A complete picture includes what happens at the margins:
Withheld or blocked caller ID. If a caller hides their number, there is nothing to match and nowhere to reply. The call can be logged; no text and no contact are created.
Spoofed numbers. Robocallers spoof caller ID. A text-back to a spoofed number reaches an uninvolved stranger. Volume limits and consent settings reduce this, but some noise is inherent to any automated reply.
The caller replies — where does it go? A reply comes back to the number that sent the text. That inbound reply needs a destination: a shared inbox, a forward to a cell phone, or a conversation view in the CRM. This should be decided before the feature is switched on.
Latency is "seconds," not "instant." The text is handed to the carrier network within a second or two; final delivery depends on the carrier's queue and the handset. Usually it is a few seconds; under congestion it can be longer.
Number reputation. Even a registered number can see delivery dip if its traffic looks spammy — long identical messages, high volume in short bursts. Short, varied, low-volume text-back traffic is the pattern carriers prefer, so this is rarely an issue for a small business, but it is why "blast everyone" is a poor approach.
Caller ID name (CNAM). The text arrives from a phone number, not a business name, unless additional branded-sender features are configured. Putting the business name in the first line of the message tells the caller who it is.
Ported-away numbers. A number that was a mobile last month can be a landline this month. The pre-send lookup catches most of this; the delivery-status callback catches the rest.
After-hours calls. These are often the highest-intent leads. The message wording should set the right expectation for the time of day rather than implying an immediate call back.
A note on booking links
Some implementations can include a scheduling link in the text-back. When the business has a connected calendar, the message can carry a link the caller taps to see open times and book directly, so a missed call can become a scheduled appointment without a return call. This is optional and depends on the calendar being connected; without it, the message still sends, just without the link. How self-scheduling itself works — availability, buffers, reschedules — is covered on the scheduling page.
Step by step: how the setup works
The setup routes a business's inbound calls through a number the messaging platform can see, gets that number registered for A2P, and verifies the whole path with a test call. In a managed service the provider does the provisioning and registration; in a self-serve setup the business does those steps in the platform's console. The sequence is the same either way.
Step 0 — Decide how calls will reach the system
Pick one of the three routing strategies from the table above:
Port the existing number if that number is the business's identity — on vehicles, signage, and reviews. Callers notice nothing; every call is captured.
Add a new tracking number to start quickly, or to track a specific campaign's calls separately. Plan to update the website, Google Business Profile, and ad call extensions.
Use conditional call forwarding to keep the existing number, skip a port, and set one forwarding rule on the carrier account.
Most established businesses port; most brand-new or campaign-specific setups use a new number.
Step 1 — Provide the routing choice and the ring-to number
Whoever configures the system needs:
The routing strategy chosen.
The ring-to number — the actual phone that should ring on a customer call (a cell, an office line, an answering service).
Service area and business hours, so the text-back wording and any booking link reflect them.
The text-back message wording, or the default. A {{bookingLink}} placeholder can be used to control where a booking link sits; otherwise it is appended automatically when a calendar is connected.
Step 2 — Provision and register the number
Managed service: the provider provisions the number (or begins the port), configures it to ring the ring-to number and to report unanswered calls, and submits the A2P 10DLC brand and campaign registration using the business's legal name, tax ID, and address.
Self-serve: the business does the same steps in the messaging platform's console — buy a number, set its voice status callback to the missed-call webhook, and register its own A2P brand and campaign.
Either way: call capture works as soon as the number is live. Text delivery begins when A2P approval lands. Porting a number takes several business days, and the old service keeps working until the port completes.
Step 3 — Set conditional call forwarding (forwarding path only)
If conditional call forwarding was chosen, set the carrier to forward busy and unanswered calls — not all calls — to the new number.
On most mobile carriers: Phone app settings under Call Forwarding → When Busy and When Unanswered, or carrier short codes (the carrier's support page lists the exact codes for "forward if no answer" and "forward if busy").
On a VoIP or PBX system (RingCentral, Ooma, Nextiva, 8x8, and similar): usually under Call Handling or Call Forwarding rules for the extension or main line — set the "no answer after N rings" and "busy" destinations to the new number.
Set the "forward after" ring count to something realistic — about 4 rings / 20 seconds — so a call that could have been answered is not pulled away too early.
Skip this step if the number was ported or a new tracking number was taken.
Step 4 — Confirm the message and connect a calendar (optional)
Review the text-back message. Lead with the business name so the caller knows who it is from.
Connect a Google or Outlook calendar if the text-back should carry a live booking link, and set booking hours and any per-day limits. Without a calendar connected, the message still sends; it just will not include a "pick a time" link.
Step 5 — Place a test call
From a mobile phone that can be checked — not the business line — call the published business number and let it ring out without answering.
Confirm:
The ring-to phone actually rang.
Within a few seconds, the test phone received the text (once text delivery is active; during the A2P wait this confirms capture only).
A new lead appeared in the pipeline at the "new" stage, and a row appeared in the missed-calls log with the expected status.
Repeat the test from a landline if one is handy, and confirm it logs as "Landline — no text" with the lead still created.
Step 6 — Update the published number (new-number path only)
If a new tracking number was taken, put it everywhere the old one appears that should be tracked: website header and contact page, Google Business Profile, Facebook, Yelp, ad call extensions, email signatures, invoices. Anywhere still showing the old number keeps working but will not trigger text-back.
What to expect while A2P is in review
Every missed call is captured, matched, and recorded as a lead.
Staff get email and dashboard alerts.
The customer-facing text is held until carrier approval lands, then begins automatically. No action is needed when it starts.
Troubleshooting
SymptomLikely causeResolutionCall rang out but no lead appearedThe number is not routing to the system yet, or forwarding is not set for "no answer"Confirm provisioning is complete; re-check the forwarding rule targets the new number and covers busy + unansweredLead appeared, status is "Landline — no text"The caller was on a landline or fixed VoIP numberExpected. Return the call — the text cannot reach themLead appeared, status indicates the plan doesn't include text-backText-back is a higher-tier feature on that productCheck whether outbound text-back is included in the current planText never arrives from a mobile testA2P approval has not landed, or the test number previously replied STOPCheck A2P status; test STOP status by replying START from the test phoneCaller replied to the text and no one saw itNo destination set for inbound repliesConfigure where replies go before relying on the featureText arrived very lateCarrier network congestionUsually transient; if persistent, check the sending number's reputation
Frequently asked questions
Does missed-call text-back work with any phone carrier?
On the receiving side, yes. Once outbound texting is active, the text reaches callers on every major US mobile carrier with no per-carrier setup. The business's own carrier does not matter either, because calls are routed through a dedicated number on a messaging platform.
Can missed-call text-back send a text to a landline?
No. Standard landlines have no way to receive SMS. A well-built system checks the caller's line type before sending; a landline caller is logged (for example, "Landline — no text"), the lead is still created, and the business is expected to call them back.
What about VoIP numbers like Google Voice?
It depends on the kind of VoIP. App-style, non-fixed VoIP numbers (Google Voice, TextNow, softphones) can usually receive SMS and will get the text. Fixed VoIP numbers wired into an office phone system often cannot, and are treated like a landline.
Does a business have to change its phone number to use this?
No, but there is a choice: port the existing number onto the platform (callers dial the same number), add a new tracking number, or keep the number and forward unanswered calls. Only the new-number option requires updating listings.
Does a business need its own Twilio account?
Not in a managed service — the provider handles the number and the A2P registration. In a self-serve setup, the business uses its own messaging-platform account.
How fast does the text go out?
It is handed to the carrier network within a second or two of the missed call. Delivery to the caller's phone is usually a few seconds; carrier congestion can occasionally make it longer.
Is automated text-back legal?
Not legal advice. The general principle is that replying by text to someone who just called a business is a customer-care response, which is different from unsolicited marketing texts. Standard practice includes STOP opt-out language and carrier-level opt-out enforcement. A business should consult its own counsel.
What happens if the caller replies to the text?
The reply comes back to the number that sent it. That destination — a forward to a phone, a shared inbox, or a conversation view — should be set up before relying on the feature so replies are not missed.
Does it work after business hours?
Yes, and after-hours calls are often the highest-intent leads. The message should set the right expectation for the time of day rather than implying an immediate call back.
Why isn't the text-back sending yet?
If capture is working (leads appear, alerts fire) but no text is delivered, the sending number's outbound texting is most likely waiting on A2P 10DLC carrier approval. It starts automatically once approval lands. Nothing is lost in the meantime — every missed call is still captured.
Does the missed call still get recorded if no text is sent?
Yes. Whatever the outcome — texted, "landline — no text," "no consent," "auto-reply off" — the call is logged, and for a real callable number a contact and a lead are created, so "how many calls are we missing" stays answerable in every state.
JSON-LD (paste into a Squarespace code block on the published page)
<script type="application/ld+json">{
"@context": "https://schema.org",
"@type": "FAQPage",
"mainEntity": [
{
"@type": "Question",
"name": "Does missed-call text-back work with any phone carrier?",
"acceptedAnswer": {
"@type": "Answer",
"text": "On the receiving side, yes. Once outbound texting is active, the text reaches callers on every major US mobile carrier with no per-carrier setup. The business's own carrier does not matter either, because calls are routed through a dedicated number on a messaging platform."
}
},
{
"@type": "Question",
"name": "Can missed-call text-back send a text to a landline?",
"acceptedAnswer": {
"@type": "Answer",
"text": "No. Standard landlines cannot receive SMS. A well-built system checks the caller's line type before sending; a landline caller is logged, the lead is still created, and the business is expected to call them back."
}
},
{
"@type": "Question",
"name": "What about VoIP numbers like Google Voice?",
"acceptedAnswer": {
"@type": "Answer",
"text": "It depends on the type of VoIP. App-style non-fixed VoIP numbers such as Google Voice can usually receive SMS and will get the text. Fixed VoIP numbers wired into an office phone system often cannot, and are treated like a landline."
}
},
{
"@type": "Question",
"name": "Does a business have to change its phone number to use missed-call text-back?",
"acceptedAnswer": {
"@type": "Answer",
"text": "No, but there is a choice: port the existing number, add a new tracking number, or keep the number and forward unanswered calls. Only the new-number option requires updating listings."
}
},
{
"@type": "Question",
"name": "How fast does the missed-call text go out?",
"acceptedAnswer": {
"@type": "Answer",
"text": "It is handed to the carrier network within a second or two of the missed call. Delivery to the caller's phone is usually a few seconds; carrier congestion can occasionally make it longer."
}
},
{
"@type": "Question",
"name": "Why isn't missed-call text-back sending texts yet?",
"acceptedAnswer": {
"@type": "Answer",
"text": "If missed calls are being captured but no text is delivered, the sending number's outbound texting is most likely waiting on A2P 10DLC carrier approval. It begins automatically once approval lands, and call capture is unaffected in the meantime."
}
},
{
"@type": "Question",
"name": "Does the missed call still get recorded if no text is sent?",
"acceptedAnswer": {
"@type": "Answer",
"text": "Yes. Whatever the outcome, the call is logged, and for a real callable number a contact and a lead are created, so how many calls are being missed stays answerable in every state."
}
}
]
}
</script>
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "HowTo",
"name": "How to set up missed-call text-back for a business",
"description": "Route inbound calls through a number the messaging platform can see, register that number for A2P, set one forwarding rule if needed, and verify with a test call.",
"step": [
{
"@type": "HowToStep",
"name": "Choose how calls reach the system",
"text": "Decide between porting the existing number, adding a new tracking number, or forwarding unanswered calls from the current line."
},
{
"@type": "HowToStep",
"name": "Provide the routing choice and ring-to number",
"text": "Supply the chosen strategy, the phone that should ring on a customer call, hours and service area, and the preferred text-back wording."
},
{
"@type": "HowToStep",
"name": "Provision and register the number",
"text": "Provision the number (or begin the port), configure it to ring the real phone and report missed calls, and register the A2P 10DLC brand and campaign for it."
},
{
"@type": "HowToStep",
"name": "Set conditional call forwarding (forwarding path only)",
"text": "Forward busy and unanswered calls only from the carrier or phone system to the new number, after about four rings."
},
{
"@type": "HowToStep",
"name": "Confirm the message and connect a calendar",
"text": "Review the text-back wording and, optionally, connect a calendar so the message can carry a live booking link."
},
{
"@type": "HowToStep",
"name": "Place a test call",
"text": "Call the business number from a mobile that can be checked, let it ring out, and confirm the real phone rang, the text arrived once delivery is active, and a lead appeared in the pipeline and the missed-calls log."
},
{
"@type": "HowToStep",
"name": "Update the published number",
"text": "If a new tracking number was taken, update the website, Google Business Profile, social profiles, ad call extensions, and email signatures."
}
]
}
</script>
