The live call handler for every number the platform sells. It rings the forwards and the in-app clients simultaneously, first to answer wins, with an answer-on-bridge so the caller hears real ringing. If nobody picks up it plays the greeting, records, transcribes, threads the voicemail onto the customer's record, texts the caller back if that is switched on, and opens a callback debt.
Also called: call forwarding · ring my cell · call routing · who does the phone ring
Nobody answers, and the caller gets a text from that same number seconds later
A missed call from a homeowner is the most expensive thing that happens in a day, and most of them ring the next builder in the search results rather than trying you twice. The text fires the instant the call is not answered rather than after voicemail, so somebody who hangs up at the beep still hears from you and somebody who leaves a message is not texted twice. It stays off until you switch it on, and the wording is yours to write.
Voicemail arrives in the conversation as words, not as a message to go and check
An unanswered call records, transcribes, and posts both the audio and the text into that customer's thread. You read what they said in three seconds instead of playing six messages to find the one that mattered, and the message never sits in a carrier mailbox nobody checks. The transcript is part of the player, so clicking a word jumps the audio to it.
The call rings every cell you listed and every signed-in screen at the same time
First to answer wins, and the caller hears normal ringing while it happens. A number works from the minute it is bought — voicemail on, a generic greeting — instead of dead-ending on callers until somebody has configured it. If nobody picks up anywhere the caller gets the greeting and the beep, and the callback task and the text back are already going out while they are still deciding whether to leave a message.
A call that rings out to somebody's personal voicemail is reported as missed, not answered
When a forwarded call is taken by the target's carrier voicemail, the carrier reports a completed call — which is how a $30,000 lead ends up in a personal mailbox nobody checks while the reports say everything went fine. Detection catches it and the record says ‘it rang through to a personal voicemail, so no one on the team heard it’. That call then raises a callback task like any other miss.
A rep's own line rings that rep, while the main line still rings the floor
A customer ringing the number their salesperson gave them should not land on a colleague's screen where anyone can pick it up. An assigned line rings its holder; the shop's main number rings every admin, sales and project user who is signed in. Crew and worker screens never ring for sales calls.
Three plain questions per line: who it rings, for how long, and what happens if nobody answers
Forward targets are picked out of your team list, which fills in that person's own number, so you do not have to know a crew lead's cell by heart. Changes take effect on the very next call — nothing to re-provision. Somebody with no number on file is named as such instead of looking identical to everyone else and quietly routing nowhere.
Record the calls that come in, and decide separately about the ones you make
Two switches, because someone who dials your business chose to call it and someone you ring did not — and where both parties must consent, theirs is the consent that matters, so the announcement plays to them. Finished recordings land on the customer's record beside the call itself, which is where anyone looks when there is a disagreement about what was agreed.
- 1The called number's inventory row supplies the routing and configuration
- 2A <Dial> rings all forward targets plus every eligible in-app client at once, for a configurable 5–55 second timeout
- 3?step= re-entry points handle after-dial, voicemail, transcript, AMD, recording and browser-originated calls
- 4Every outcome is written to the calls fact table AND as a sentence in the customer's thread
- 5The route always answers 200 with TwiML — a non-200 makes Twilio read a scary error to the caller
A newly purchased number would text perfectly and hang up on anyone who called it, because nothing had been configured to answer — the first number ever bought here sat in exactly that state. A builder does not find that out from a dashboard; they find out when a customer mentions they tried to ring. Incoming calls now ring every configured cell and every signed-in browser at once and fall through to voicemail, a text back and a callback task, and an unconfigured number still behaves like a working phone rather than a dead end.
- A purchased number with no call handling
- Calls dead-ending with no voicemail and no record
- Missed calls leaving no trace anywhere
See it on your own jobs
Twenty minutes, your numbers, no slide deck. We’ll build one of your real buildings in front of you and send you the estimate link at the end — yours to keep either way.
or keep browsing features →