What happens the moment a call goes unanswered. A high-priority task, due now, assigned to whoever holds that line — or to the shop if nobody does. It is worded for what actually happened: they left a voicemail, it rang out to a personal voicemail, nobody picked up. It names the person, not a ten-digit number. The caller is sent an automatic text back — the wording is set per phone line — the voicemail joins their conversation, and, when you switch it on, the line's owner is texted that a call was missed. Built only for post-frame and barndominium builders, where the call that rang out can be a sixty-thousand-dollar shop.
Also called: missed call follow up · nobody called them back · lost lead from a missed call · missed call text back · text back when we miss a call · missed call alert
A missed call becomes a task somebody owns, due now
The moment a call goes unanswered it becomes a high-priority task, due immediately, assigned to whoever holds that line. Not a badge, not an unread count — a job on somebody's list with a name against it.
The call is missed at 7:40, the little red dot is cleared at 7:41 while someone is looking for something else, and nobody rings that number back at all.
A notification is a thing you can miss twice. A task is a thing that stays on a list until somebody closes it, and the task list already has the follow-up, the snooze and the reassignment built around it — so the callback inherits all of that for free.
It knows what the call actually did
Rang out, went to a personal voicemail, hit the shop machine, or was answered and dropped — these are four different problems, and the task is worded for the one that happened rather than a generic “missed call”.
Every miss reads the same, so the one who left a two-minute message describing a 60x120 gets rung back with “sorry, did you call?”
The disposition comes from the carrier leg, not a guess, so answering-machine detection can tell a voicemail greeting from a person saying hello. Someone who left a message wants a different call back from someone whose phone rang out. Knowing what happened lets the rep open the callback with the right sentence, which makes him sound prepared rather than caught out.
Three calls in ten minutes is one job, not three
A person who rings, rings again, then tries the other line is one problem. The episode collapses to a single task that carries all three attempts — and the urgency goes up, because trying three times is what someone does when they mean it.
The queue shows nine callbacks and there are four actual people in it, so the crew starts clearing rows instead of ringing them.
Episodes are keyed on the caller and a time window rather than on the call, so the second attempt joins the first instead of racing it. Three separate tasks is the failure mode that trains people to close them without reading. A short, honest list is one people actually work; a padded one teaches them to stop reading.
The caller gets a text back, in your words
Each phone line has a Missed-call text-back switch and its own message — who you are and when you will ring. When a call to that line goes unanswered, the text is sent from the number they dialled, and it sits in the same thread you will ring them from.
They rang three builders in one sitting; the one who answered second got the job because he was the first to say anything at all.
It is sent from the number they dialled, so a reply comes back to a line you actually watch, and it lands in the one conversation rather than a separate inbox. The point is to buy the twenty minutes it takes you to get off a roof — a caller who hears something back feels taken seriously, and is far less likely to keep dialling down the list of builders.
The rep finds out on his own phone
A forwarded call that rings out leaves nothing in the rep's own call log. So, when the account switches it on, the line's owner is sent a text the moment a call is missed: Missed call — Curtis Hoover, the number on its own line so a tap rings it back, the time, and whether they left a voicemail. It goes to the line's owner alone; a line nobody owns is the business's, so everyone who takes those alerts hears.
You step away from your phone for thirty seconds, miss a call, and there is no sign of it anywhere except inside an app you have no reason to open.
The lock screen is where a busy builder actually looks. Finding out there means no constant checking of the app, and none of the low hum of worry that you missed something — and a lead that is rung back in ten minutes instead of at the end of the day.
The voicemail is in the thread, not a separate inbox
Message, recording and transcript sit on the contact, next to the texts and emails. You hear what they wanted before you ring, so the callback opens with their answer instead of your question.
The message with the dimensions and the county in it is on a handset in somebody's truck, and the man who takes the callback has none of it.
Voicemail lives in the same place as everything else that person ever said, so it survives the phone being handed to somebody else. A separate voicemail box is a place where things go to be forgotten by exactly one person. Hearing it first means the callback starts with I heard you want a 40×60 — the customer feels listened to before you say a word.
The task names the person, not a ten-digit number
If the number is anyone you have ever spoken to, the task says their name, their company and the job it is about. A stranger stays a number — and that is itself the useful signal that this is a new lead.
A queue of bare phone numbers tells you nothing about which one is the customer waiting on a change order and which one is a supplier.
The lookup runs against the contact record before the task is written, so the person picking it up knows in one glance whether they are chasing a live quote or meeting somebody new. A name makes it a person you owe a call, not a chore — people call people back; they ignore numbers.
Who it lands on when nobody owns the line
A line with an owner routes to the owner. A shared or after-hours line routes to whoever is actually on, and if nobody is, it lands on the shop rather than nowhere. There is no state where a miss belongs to no one.
The call came in on the general line at ten past five, so it belonged to everybody, which meant nobody rang it back.
Ownership is resolved at the moment of the miss from the same rules inbound routing already uses, so the two can never disagree. Unassigned is the state every dropped lead was in. When a miss always belongs to someone, nobody has to feel guilty about a call they assumed somebody else took.
The task is the plan; the alert is only a bonus
The push, the email and the badge are all best-effort. The task is not. If every notification fails — phone off, no signal, notifications declined — the callback still exists and is still owed.
Notifications were switched off months ago after a noisy week, and nobody realised the callbacks had been going with them.
The task is written first and the alerts fire afterwards, deliberately in that order. Anything built the other way round quietly depends on a delivery you do not control, and the day it fails you never find out. Knowing the callback cannot vanish lets the owner stop worrying about what slipped through while he was on site.
Nothing here depends on somebody having noticed
Every step runs off the phone carrier's own signal that the call ended, not off anyone opening the app. The task exists, the text back is sent and the thread is written before the first person even looks at a screen.
It only worked when somebody had the tab open, which is to say it worked least well on the days everybody was on site.
The whole chain is server-side and idempotent, so a repeated signal from the carrier cannot produce a duplicate callback and a browser nobody has open cannot skip one. Who gets told is a per-person setting; whether it happened is not.
The clock that shows whether it worked
Time-to-callback is measured on every miss and reported per person and per line. A rescue you cannot measure is a policy, not a system — and callback latency is the number that says which one you have.
Everybody agrees callbacks are important and nobody can say whether yesterday's took four minutes or four hours.
The clock starts at the missed leg and stops at the first outbound contact, so it measures the thing the customer felt rather than the moment a row was ticked. It is per line as well as per person, because one bad number can hide inside a good average. What gets timed gets faster — reps compete with their own number without being told to.
- 1A call goes unanswered.
- 2A task is created immediately, due now, high priority.
- 3It goes to whoever owns that line — or to the shop if the line has no owner.
- 4It names the caller and says what happened, not just 'missed call'.
- 5Three calls from one person in ten minutes makes one task, and the clock on them keeps running.
- 6Then the thread entry, then the alerts, then the text back to the caller — in the words you set for that line.
- 7Switched on, the line's owner is also texted that a call was missed: who, their number, when, and whether they left a voicemail.
A missed inbound call is the most expensive event this platform handles. One post-frame lead is worth thirty to two hundred and fifty thousand dollars, and the call that just failed is often the only signal that lead ever existed. A miss used to produce one sentence in a thread and nothing that would ever chase anybody — no task, no reminder, nothing with a name on it. Now what was going to be forgotten sits in the same list as the calls somebody planned on purpose.
- Missed calls producing no actionable work
- Follow-up depending on someone remembering
- Repeat calls generating a pile of duplicate tasks
- A rep not knowing he missed a call until he opens the app
