Solutions by problem · lead intake
A missed-call notification tells you a number. A request tells you a job. The receptionist asks the questions you chose, in the order you chose, and leaves your team a structured record with the call beside it, in the inbox and on your webhooks the moment the call ends.
From $49/month with 250 AI minutes and one US local number included. See full pricing
A fence, a roof, a repipe, a deep clean. The caller wants a number and you cannot give one without the address, the size, the material and a day you can look. A receptionist that asks for all five turns a callback into an estimate visit.
Intake calls are won by whoever took the details down and called back first. The record the receptionist leaves is the head start, and it is waiting before the caller has hung up.
A caller leaves a number, you return the call at the next gap, they are at work, you trade voicemails for two days. Asking when they are free, on the first call, ends the loop.
During setup you pick the fields a request should hold for your kind of business: the problem in the caller’s words, the address, the urgency, the preferred days and times, how they found you. The industry pages show typical sets for each trade.
It works the questions into the conversation rather than reading a form, skips the ones the caller already answered, and marks the ones they decline as unknown instead of guessing.
Addresses, names and numbers are read back before the call ends, so the record your team sees is the one the caller approved.
In the team inbox and on your signed webhooks when the call ends, with the call record beside it. CSV export and the API carry the same record into the tools you already use.
The estimate visit, the consultation, the callback: your team confirms the time with the caller. The receptionist captured the request; it writes no calendar.
Illustrative example A Thursday afternoon call to a roofing company from a homeowner comparing three quotes. The business, the caller and the policy are invented; the receptionist opens every real call with its AI disclosure.
Thanks for calling Summit Roofing. I am an AI receptionist for the team. How can I help?
I have a leak near the chimney and I am getting quotes for a repair, maybe a full replacement. Can someone come look?
Yes, Summit does free on-site estimates for repairs and replacements. Can I get the address?
305 Ridgeview Drive in Alder Creek.
Alder Creek is in the service area. Is the leak active right now, or does it only show up in heavy rain?
Only in heavy rain, but the ceiling stain is growing.
Understood: an intermittent leak near the chimney with a growing stain. Do you know roughly how old the roof is, and whether it is asphalt shingle?
Asphalt, about twenty years.
Thank you. When would an estimator find you at home?
Any weekday after four, or Saturday.
Noted. Can I get your name and the best number to confirm the visit?
Elena Marsh, this number is fine.
Thank you, Elena. Your estimate request for 305 Ridgeview Drive is with the team, and someone will call to confirm a time. Is there anything else?
That is everything.
Synthetic example record The inbox shows a new estimate request: intermittent leak near the chimney with a growing ceiling stain, asphalt shingle roof about twenty years old, 305 Ridgeview Drive in Alder Creek, home weekdays after four or Saturday, caller Elena Marsh at the number she called from, interested in repair or replacement. The estimator calls to confirm a visit.
The same table on every receptionist page, because the limits matter as much as the features when you are choosing.
| On a call | Today | What that means |
|---|---|---|
| Questions about hours, services, areas and prices | Handled on the call | Answered from the business information you approve. A question you have not covered gets a plain "I do not have that" and a message for your team, never a guess. |
| Reaching a person on your team | Handled on the call | A transfer to one eligible US destination, with the teammates you list tried in turn when the first does not pick up. |
| Closed hours, a busy line and holidays | Handled on the call | Your closed-hours message, a bounded waiting queue with position announcements, and the fallback path you configure when every AI line is busy. |
| Messages and callback requests | Captured for your team | Name, number, the request in the caller’s words and the details you ask for, in your inbox and on your webhooks the moment the call ends. |
| Appointment and estimate requests | Captured for your team | The request, the address and the caller’s preferred times. Your team confirms the time from the record; the receptionist writes no calendar. |
| Emergencies and safety | Captured for your team | Only the safety wording you approve, such as where a shutoff valve is, then the on-call transfer and an urgent request. It gives no medical, legal or electrical advice of its own. |
| Dispatching a crew or promising an arrival time | Not part of the receptionist | Not the receptionist’s job: your dispatcher assigns the work and your team confirms the visit from the record it leaves. |
| Texting the caller afterwards | Not part of the receptionist | It sends no text messages. Requests reach you in the inbox, on your signed webhooks and through the API. |
| Writing to a calendar, a CRM or a dispatch system | Not part of the receptionist | No named connector exists. Results reach other systems through signed webhooks, CSV export and the API. |
| Recording the whole call | Not part of the receptionist | Full-call recording is not part of the receptionist offer. Every call leaves a record of what was asked and what was answered. |
| Languages other than English | Not part of the receptionist | English today. |
| Guaranteed answer rates, response times or outcomes | Not part of the receptionist | Capacity is per plan on shared fleet, not reserved hardware. When every AI line is busy, callers follow the fallback path you chose. |
Start from the set on your industry page and remove what you never use. Fewer, better questions beat a long form read aloud, and callers finish the call.
A request marked urgent tries your transfer first; the rest go straight to the inbox. Define urgent in your own words during setup, and change it whenever your season does.
Read it in the inbox or on your phone, receive it on a signed webhook, or export it as CSV. The record is the same everywhere, so nobody re-types a request.
Setup starts from your website: the receptionist drafts its answers from your public pages and you review every one before paying. How setup works, step by step.
No. It captures the request and the caller’s preferred times; your team confirms the time and tells the caller. It writes no calendar and promises no time.
Any you choose during setup: name and callback number, the problem in the caller’s words, address, urgency, preferred days and times, how they found you, and questions specific to your trade such as roof type or the number of bedrooms. Declined questions are marked unknown.
The team inbox and the mobile app, your signed webhooks the moment the call ends, CSV export and the API. No named CRM connector exists; the webhook and the CSV carry the record into other tools.
It asks the qualifying questions you approve and records the answers; it scores nothing and decides nothing. Your team reads the record and decides who to call first.
It takes what the caller is willing to give, marks the rest unknown and still leaves a callback request. A name and a number are enough for your team to follow up.
The fields a plumbing request holds, and an example call.
The record a call leaves, and where it goes.
The questions callers in your kind of business get asked.
The calls that never became a request, and what they cost.
Most small businesses miss calls for one reason: the person who should answer is doing the work.
Nights, weekends and holidays are when the emergency calls come and when the office is empty.
A busy line is a good problem until the third caller gives up.
Plumbing calls arrive while you are under a sink.
HVAC phones follow the weather.
An electrician’s phone mixes real danger with routine estimates.
Choose the questions once; every call after that leaves a request your team can act on.
