Answering missed and after-hours calls with AI

How the bot works

Nine steps. The routing, the hours and the urgent list are ordinary rules and cost almost nothing to run; the model is only in the conversation itself.

1. It answers what would have gone to voicemail. Your phone system forwards on the conditions you set — outside your hours, on a holiday, after the rings you choose, or when nobody picks up. Your line, your number, your greeting. Nothing changes about how the phone works when somebody does answer.

2. It says what it is. In the first breath: an assistant taking a message for the team, plus whatever recording disclosure you configure. No pretending to be a person, no made-up name. A caller who asks to speak to a human is taken straight to the fallback you chose.

3. It asks your intake, in your order. Name, a callback number it reads back, the address, and what is actually happening — the short list you would want on a sticky note. It asks the next question based on the answer it just got, rather than reading a tree at somebody whose kitchen is flooding.

4. It answers only what your records support. Your hours, your service area, whether you cover that equipment or that town, where to park, what to have ready. Anything outside the page it was given gets the honest answer: somebody will confirm that when they call you back.

5. It decides urgent or not, from your list. You write the list — water still running, no heat overnight, a smell of gas, a door that will not lock, a death in the family. The bot matches what the caller said against it and says which rule it matched. It does not invent a new category of emergency at eleven at night.

6. A life-safety call stops being a phone call. If what the caller describes is on your stop list, the bot says the line you wrote — hang up and call 911 — or transfers straight to the number you nominated, and the conversation ends there. There is no path where the bot keeps asking questions through an emergency.

7. It texts the person on call, written out. Who called, the number, the address, what they said in their own words, which rule made it urgent, and the link to the recording or transcript. Your rotation decides who gets it; your escalation decides what happens when nobody acknowledges it.

8. It texts the caller back too. A short confirmation of what was taken down and when somebody will call — in the window you set, not a time it invented. That message is the reason the caller stops working down the search results.

9. It writes one row per call. Timestamp, number, duration, the transcript, the recording if you enabled it, every question it asked, every answer it gave and where that answer came from, the urgent-or-not decision with the rule it cited, who it notified, and whether they acknowledged.

What you configure

It can be configured to run in any business. This is what that actually means — the list of things that are yours, not ours.

Your hours and overflow rules

When it answers at all: after hours, holidays, lunch, a busy signal, or after a number of rings you choose. Per line and per location if you have more than one.

Your intake questions

The exact list, in the exact order, including the ones that only matter to you — gate code, unit number, which building, whether there is a dog.

Your urgent list

The words and situations that make a call urgent, in your trade's language, and the ones that explicitly do not. This is the document the routing is measured against.

Your stop list

What makes the bot stop taking a message and hand the call over or end it — and the exact sentence it says when that happens.

What it may answer

The page of facts it is allowed to read from: hours, service area, what you do and do not cover, parking, what to have ready. If it is not in there, it does not say it.

What it must never say

Prices, diagnoses, arrival times, whether something is covered by a warranty or a policy, or anything that sounds like advice. Written down, not implied.

Your on-call rotation

Who gets the text, in what order, how long they have to acknowledge it, and who it escalates to after that. Different rotation for nights and weekends if you want one.

Recording and disclosure

Whether calls are recorded at all, the disclosure sentence, how long audio is kept, and who can play it back. Your rules and your state's, not our default.

Your voice and your words

The greeting, the pace, how it signs off, and the versioned prompts behind the conversation — yours to read, yours to tune.

Transparent, and configurable by you

The dark band below is what the system will not do. This is what you can see and change — and it is how we build everything, not something invented for this page.

You see what it did, and why

Every call ends in a row you can read: the transcript, each answer it gave with the line of your own fact sheet it came from, and the urgent-or-not call with the rule it matched. You can see why it paged the on-call tech at midnight before you agree with it.

Versioned prompts you can tune yourself

The prompts behind the conversation are yours to read and yours to tune. A change is a reviewable diff, replayed against calls that already happened so you can hear what it would have said differently, and rolled back the same way.

A human in the loop wherever judgment actually matters

The bot takes the message. The call back, the diagnosis, the price and the commitment all belong to a person — that is a property of the system, not a promise about how carefully we'll use it.

Every run logged, along with what it cost

One row per call with the audio or transcript attached, the notification and the acknowledgement — plus token usage and cost for that call.

It can be configured to run in any business. The questions, the urgent list and the words are yours: your hours, your trade, your rotation, your fact sheet. The after-hours wiring on this page is one configuration of it, not the limit of it.

Works with your tools

This sits in front of the phone you already have. We're not selling you a new phone system or a new number.

• RingCentral, Dialpad or 8x8
• Microsoft Teams Phone
• Twilio
• A carrier forward from a mobile
• ServiceTitan, Jobber or Housecall Pro
• HubSpot or Salesforce
• A helpdesk or ticketing tool
• SMS to the on-call phone
• Google Workspace or Microsoft 365
• Slack or Microsoft Teams
• Google or Outlook calendar

Works well for

• Plumbing contractors — A burst pipe at night is a job that goes to whoever answers, and voicemail does not answer.
• Electrical contractors — Half the calls arrive while the crew is on a roof or in a crawl space with the phone in the truck.
• Towing companies — Every call is someone stranded now, and the only question is the location and whether it is safe.
• Funeral homes — The calls that matter most come at three in the morning, and they cannot land in a mailbox.
• Property management companies — After-hours maintenance calls need triage: a leak wakes somebody up, a broken dryer waits.

How a rollout works

Nothing answers a real caller on day one. The first milestone is listening to it handle calls that already happened.

1. 01Discovery

   The quote call, then a working session. We go through your hours, your intake, the urgent list in your own words, your rotation, what the bot may and may never say, and how your phone system forwards. You get the call flow written down, the stop list, and a written scope.

2. 02Dry run

   The agent runs against recordings and transcripts of calls you have already taken, plus live test calls from your own team. Nothing reaches a customer. We compare its intake, its answers and its urgent-or-not decisions against what your office actually did, and this is where your own numbers come from — on your own calls.

3. 03Assisted mode

   Live, on one slice first: after hours only, or one line, or one location. Every message goes to a person, the fallback stays wired, and you listen to the first weeks of calls with the transcript beside them. The work gets covered. The control doesn't change.

4. 04Optional wider hours

   Optional. Once you have heard it hold up, the same agent can cover overflow during the day or a second location, with every hard stop in force and the kill switch. Plenty of teams stop at after-hours only, and that's a good place to stop.

What we don't claim

• No numbers we haven't earned. No percentage of calls answered, no revenue-per-missed-call figure, no “never miss a call again”. We haven't run this on your phone. The dry run is where those numbers come from, and they'll be yours.
• No customer claims on this page. No names, no case studies, no logos.
• It is not a receptionist. It takes a message well and triages honestly. It does not build the relationship, read the room, handle an upset regular, or know that the caller is your biggest account. That is the call back, and the call back is a person.
• Speech recognition is imperfect. Accents, bad lines, road noise and a shouting toddler all exist. The design assumes it will mishear sometimes, which is why the number is read back, the recording is kept and no call ends in silence — not because it won't happen.
• Fully autonomous call handling isn't on offer. The design assumes a person calls back. That's deliberate, and it's why the boundary is written down.

Questions people ask

Can AI answer the phone for my business?

Yes - and the honest version is that it answers, takes the message and triages it, then a person calls back. An AI voice agent can pick up what would have gone to voicemail, say plainly that it is an assistant, ask your intake questions in your order, answer the handful of things your own fact sheet covers, work out whether the call is urgent against a list you wrote, and text the person on call with everything already written down. What it does not do is diagnose the problem, quote a price or promise a time - those are the decisions that cost you money when they are wrong, so they belong to whoever calls back.

Will it pretend to be a person?

No. It identifies itself as an assistant taking a message for the team, in the first breath, in words you approved, on every call. There is no configuration in which it claims to be human, and a caller who asks for a person is handed straight to the fallback you chose - a transfer, a page to the on-call phone, or your existing voicemail. A caller who works out halfway through that they are talking to a bot is a worse outcome than one who was told in the first breath.

What happens if somebody has a real emergency?

It stops being a phone call with a bot on it. You write the stop list - a smell of gas, water nobody can shut off, somebody hurt - and when what the caller describes matches it, the bot says the exact sentence you wrote, which usually means hang up and call 911, or it transfers to the number you nominated. The conversation ends there. There is no path where it keeps working through an intake script while something is actually happening, and the notification to your on-call person goes out regardless.

Can it book the job while it has the caller on the phone?

It takes the request, confirms the window you configured for a call back, and hands it to whoever owns the book. Writing into your calendar is a bigger piece of work than it sounds - it needs your availability rules, your travel time, your crew skills and your no-show policy - so if you want that, say so on the call and it gets scoped in your quote rather than assumed. What this bot guarantees is that nobody goes to voicemail and nothing gets lost.

Does it record calls?

Only if you turn recording on, and then only with the disclosure sentence you wrote, the retention period you chose, and access scoped to the people who handle calls. A caller who objects is handled the way you specify. Transcripts and audio are not used to train anything. The rules here are yours and your state's, not our default - and the disclosure is a configuration item we go through on the call, not a footnote.

What if it mishears the caller or does not understand them?

It reads the callback number back, it asks again rather than guessing, and if it still cannot get there it says so and hands the call to your fallback. Every call ends in a message to your team either way: a hang-up, a bad line or a conversation it could not follow still produces a row with the number, the time and whatever was captured, plus a notification. A call the bot handled badly is only a disaster if nobody is told about it.

Will it answer questions about price?

No, and that is written into the configuration rather than left to the model's discretion. Price, coverage under a warranty or a policy, whether a repair is worth doing, and how long a job will take are all on the never-say list. The bot's answer is that somebody will go through that on the call back. If you want it to read a published rate off a sheet you maintain, that is a decision you make deliberately, per fact, and it reads only what is on the sheet.

Does it work with the phone system we already have?

Yes, for almost all of them - we take calls by forwarding from your existing line, so you keep your number and nothing changes when somebody does answer. That covers VoIP platforms like RingCentral, Dialpad or 8x8, Microsoft Teams Phone, a carrier-level forward from a mobile, or a separate after-hours number that rings the same place. Messages go out as SMS, email, a Slack or Teams post, or a job in a field service tool. Naming a system means we can work with it, not that we are partnered with it.

Is there a record of what it said on each call?

Yes, and it is built for the morning after. One row per call records the time, the number, the duration, the full transcript, the recording if you enabled it, every question it asked, every answer it gave with the line of your fact sheet it came from, the urgent-or-not decision with the rule it matched, who was notified and whether they acknowledged it. If a caller says they were told something, you can check what they were actually told.