It's 11pm and a rowhome in a neighborhood where the lateral lines are still original cast iron just found out the hard way what "original" means. Water's coming up through a floor drain, the homeowner's standing in it with a phone in one hand, and your number is the second one they've tried tonight. The first plumber's line rang out. Yours picks up. Not you. Something else.
That "something else" is what people mean when they say "virtual receptionist for plumbers," and it's a term that gets thrown around a lot more than it gets explained. I want to walk through what one is actually built to do on a call like that: what the category as a whole advertises, sourced to the products actually selling it, and then, separately, exactly what Dialkeep does today. Those two things are not the same claim, and I don't want you leaving this post confusing them.
What "virtual receptionist" means, mechanically
Strip the marketing off it and a virtual receptionist for plumbers is software that answers your business line when you can't, has a real back-and-forth with the caller instead of playing a recording, and produces something out the other end: a booked slot, a text, a note, a routed call, depending on which product you bought.
The category, as it's actually sold right now, advertises three things worth knowing about before you shop it. Dialzara's pricing page lists bilingual voice support, English and Spanish, on its receptionist tiers. Trillet's plans page lists calendar integrations, Google Calendar and Cal.com, built into every tier, meaning some products in this category do write straight to a real calendar. And Trillet's own electricians page describes urgency screening as a first-class feature: the software screens every caller for urgency, decides the call is an emergency, and sends the owner an SMS and a call about it. I'm citing named products because "virtual receptionists generally do X" is a claim I can't source. Specific companies publishing specific features is a claim I can.
The 11pm call, step by step
Here's the part that's actually about your rowhome caller, not about the category in the abstract.
The phone rings once, maybe twice, and something answers with your business's name, not a generic greeting. It asks what's going on before anything else: not name, not address, the problem first, because that's the order a good dispatcher uses too. The caller says water's coming up through the floor. It asks where and gets the address. It asks for a callback number, though it usually already has one, since caller ID came in with the call. Somewhere in there, if the caller asks straight out whether they're talking to a person, the honest answer is "no," said plainly, not dodged and not volunteered unprompted either.
If the caller asks what this is going to cost, a real system in this category reads back a number it was configured with in advance, not one it invents on the spot, and it should flatly decline to guess at a repair total, because nobody, human or otherwise, knows what a cast-iron lateral actually needs until someone's got eyes on it. If the address is outside your service area, the honest move is to say so on the call, not book something you'll have to cancel by phone tomorrow. And however the call reached your line in the first place, what happened on it gets written down as a structured record, not just held in the audio.
That's the shape of the call. What happens to that record, and whether "answered" turns into "you actually find out," is where the products in this category stop being interchangeable, and it's where I need to stop talking about the category and start talking about the one I'm building.
What Dialkeep specifically does today
Here's the part where I hold my own product to the same sourcing standard I just held the category to. Everything in this section is live in the code right now, not on a roadmap. One thing it is not: available. You cannot put this on your line today — there is no signup, and the phone number is switched off while the demo is still a chat window. Where I say "your" fee or "your" service area below, I mean the values an operator sets up on a line, not something you can go configure.
It answers with the business's own greeting. It discloses honestly that it's AI if the caller asks, and never brings it up first. It takes the burst-pipe call in the order I described above (problem, then name, then address, then callback number), and if you've configured a flat service-call fee, it reads that number back through a tool that pulls it straight from your pricing, not from whatever the model happens to remember. It refuses, on principle, to quote a repair total. It checks the address against the service area you've set. It sorts the call into one of a few pre-written scheduling windows based on the words the caller used: that's a scheduling mechanism, not a safety judgment, and I want to be precise about the difference. It isn't deciding anything is dangerous. It's picking which pre-written response fits. It picks the caller's number off caller ID and writes it into the record, so the number is in there and not just in the audio. It hangs up cleanly instead of trailing off.
What it does not do, today, is anything from the category list above. No bilingual support: the string doesn't exist anywhere in the phone stack, and the voice it speaks with is English only. No real calendar write: the "scheduling" it offers is a fixed sentence pulled from a small set you wrote in advance, not a check against an actual open slot. And here's the one that matters most, so I'm not going to soften it. And no urgency screening in the sense Trillet's page means it: what I described above is a pre-written scheduling window picked from a small list, not software deciding a call is an emergency. It never makes that call — and even if it did, there is nothing built to tell you about it. Nothing tells you that call happened. Not a text, not an email, not a push notification — nothing reaches out to you at all. There is an owner-facing calls list built, and every finished call is written into its index on purpose, so the surface is real. What is missing is the way in: self-serve signup isn't live, so there is no account for you to log into and look at it. Compare that honestly to your own voicemail box, which at least has a red light on it.
Where that leaves the homework
I keep coming back to this because it's the real gap, not a footnote. A surviving voicemail is annoying, but it's information: a recording, a callback number, proof somebody called. Right now, a call that reaches Dialkeep and goes perfectly, address confirmed, fee quoted correctly, record written cleanly, still ends with you not knowing it happened. The ninety seconds the caller experiences got better. The part where you find out and call them back didn't move at all. I don't have a tidy way to end that sentence, because there isn't a shipped fix for it yet. That's a real hole in the product, and I'd rather say so here than let you discover it on your own.
Try the actual call, not my description of it
I'm not asking you to take my word for any of the Dialkeep half above. The demo runs a live text-chat version grounded in your own business: type your business name in, then ask it the things a 2am caller would ask, and judge the answers. It is a chat, not a phone call — it does not run the intake order I just described, and I would rather say that here than have you find it out ten seconds after clicking. It won't quote a repair price in the chat, on purpose, same as it wouldn't on a real call. That's the part you can check today; the phone version and the rest of this post's category claims are for you to weigh against what you actually need.
Invoca's home-services benchmark headlines 52% of callers reaching a person. The kinder cut of the same data — counting only calls that last past thirty seconds, so misdials and instant hangups drop out — lands nearer three in four answered. I am quoting you the number that flatters us least badly and telling you it is call-tracking data from a vendor selling into this market, not an independent study. If you want to see what that's actually worth for a shop your size instead of trusting an industry average, run your own numbers through the missed-call calculator — it's a model to check your week against, not a verdict.

Built for plumbers
Burst pipe at 2am doesn't care that you're asleep. Neither does this. It answers, asks what's happening and where, and gets the details while they're still on the line — instead of a beep they hang up on before dialing the next plumber.
Catch the 2am burst-pipe call (it picks up so you don't have to) →