By Sagar Shankaran, Founder of CallSphere
What unanswered calls cost a design firm, what a real-time voice agent can look up mid-sentence, and the calls that must always reach a licensed engineer.
Key takeaways
The superintendent on the third-floor deck has a pump truck scheduled for eight and a question about the rebar at a column-to-slab joint that does not look like detail 7/S-402. He calls your office at 6:50 on a Tuesday in June. The office manager comes in at 8:30, the principal is driving to another site, and the project engineer who knows this job is on I-40 with his phone in the cupholder. So the superintendent leaves a voicemail, tries the principal's cell, gets nothing, and makes the call himself at 7:20 because the pour is not moving.
That is not a customer service problem. That is a rebar decision made by somebody who is not licensed to make it, on your job, with your seal on the drawings. And the reason it happened is a phone that rang for ninety minutes into an empty room.
Small A/E offices are chronically bad at the phone, and it is not laziness. The people who can answer a real question are billable, and billable people are in the field, in a code review meeting with the AHJ, or heads-down on a set that goes out Friday. The line rings through to a shared voicemail box checked at ten and again at four.
Three kinds of caller matter. The field caller — the superintendent above, or a foreman wanting to know if RFI 218 got answered before the inspector shows up. The plan reviewer from the building department, who calls once, from a blocked number, about a comment on your permit set, and if you miss them your resubmittal sits another two weeks in a queue while the owner asks why the schedule slipped. And the new-work caller — a developer, a facilities director, a general contractor's preconstruction manager — who is calling three firms on a Tuesday morning and is going to talk to whoever picks up.
A real-time voice agent is a phone answerer that talks back in about a fifth of a second, understands the caller in normal speech, and can look something up or book something on a calendar in the middle of the conversation instead of taking a message about it. That last part is what makes it useful in a design office rather than an expensive answering machine.
Older phone robots worked in a relay: speech to text, text to a model, reply back as text, then something read it aloud. Every handoff added a beat. You have heard the result — the dead pause, the interruption that gets ignored, the "I'm sorry, I didn't catch that" that makes a superintendent hang up.
Hear it before you finish reading
Talk to a live CallSphere AI voice agent in your browser — 60 seconds, no signup.
In 2026 the speech-to-speech models answer in roughly 200 milliseconds — faster than the average human reaction time — in one loop, and they can call a tool while they are talking. Google's Gemini 3.1 Flash Live arrived in March 2026 with audio-to-audio across more than 90 languages and strong tool handling; OpenAI's realtime line moved the same way, and both now connect into ordinary business phone systems over standard telephone plumbing. Practically, that means the agent can say "let me check the RFI log" and actually check it, mid-sentence, without the caller wondering whether the line dropped.
For a firm whose crews and contractors include Spanish-speaking foremen, the multi-language side is not a novelty either. A foreman who calls at 6:50 and gets an answer in Spanish about whether a submittal was approved is a foreman who does not stop work.
flowchart TD
A["Call rings the office line at 6:50 a.m."] --> B{"What does the caller need?"}
B -->|Superintendent in the field| C["Agent reads back RFI 218 status and the ASI number from the log"]
B -->|Plan reviewer at the building department| D["Agent captures the comment number and pages the project architect"]
B -->|Developer with a new site| E["Agent takes parcel, use and square footage, books the principal"]
B -->|Anything about rebar, egress or a stop-work| F["Agent warm-transfers to the engineer of record on call"]
C --> G["Transcript filed to the project record before 7:00 a.m."]
D --> G
E --> G
F --> G
The temptation is to let it answer everything. Do not. In a design firm the line between information and instruction is a liability line, and it should be drawn in the setup, not in the moment.
Information it can give: whether an RFI has been answered and what number the response carries; whether a submittal is approved, approved as noted, or revise-and-resubmit; the date the permit set was uploaded; who the project architect is; the next available slot on a principal's calendar. All of that is a lookup against a log, and all of it is verifiable after the fact from the transcript.
Instructions it must never give: how to build something, whether to proceed, whether a deviation is acceptable, whether a field condition is okay. When those words come up the call goes to a person immediately — warm transfer to whoever is on the on-call rotation that week, and if nobody answers, a text with the caller's number and the words they used. Set that rotation the way you set the after-hours structural distress line: named people, named weeks.
Assumptions to replace with your own phone records: a 16-person firm receives 240 inbound calls a month; 18% go unanswered or are abandoned before a person picks up, which is 43 calls. Of those, roughly 6% are new-work inquiries. Average net fee on the small work that comes from a cold inbound call — a tenant fit-out, a small addition, a due-diligence report — is $28,000, and the firm converts one in four of those inquiries when it actually talks to them.
| Line | Now | With instant answer |
|---|---|---|
| Inbound calls per month | 240 | 240 |
| Unanswered or abandoned | 43 | 4 |
| New-work inquiries in that group (6%) | 2.6 | 0.2 |
| Lost inquiries per year | 31 | 3 |
| Conversions lost at 25% | 7.8 | 0.7 |
| Fee at $28,000 per project | $218,000 not captured | $20,000 not captured |
Halve the conversion rate and halve the fee and you are still looking at roughly $50,000 a year walking to a competitor because a phone rang at 7:10 a.m. That ignores the field-call side, which is harder to price and easier to feel: one avoided bad decision at a pour, one plan-review comment answered the same day instead of two weeks later.
Prove it the cheap way. Before you change anything, pull one month of call detail from your phone provider and count calls under fifteen seconds outside 8:30 to 5:00. That is your abandoned number, and no vendor gets to tell you what it is.
Still reading? Stop comparing — try CallSphere live.
CallSphere ships complete AI voice agents per industry — 14 tools for healthcare, 10 agents for real estate, 4 specialists for salons. See how it actually handles a call before you book a demo.
An angry client does not get an agent. When an owner calls because a change order surprised them or a project is late, that call belongs to a principal, and the agent's only job is to find one fast and say so plainly. Same for anything from an attorney, a claims adjuster or an insurance carrier — those go to the principal-in-charge, unrecorded by the agent beyond the fact of the call, and your professional liability carrier will thank you.
Emergencies are their own category. A call reporting cracking, deflection, water intrusion or a partial collapse is not a message to be taken; it is a chain that has to reach a licensed engineer immediately. Configure that path first and test it monthly by calling it yourself at nine on a Saturday night.
And be honest about accuracy limits. The agent is reading a log; if your team has not updated the RFI status in Procore, it will confidently tell a superintendent that RFI 218 is open when the response went out yesterday. The phone does not fix a stale record. It exposes one.
Some will mention it the first week. What actually annoys a superintendent is voicemail while a pump truck idles at $200 an hour. If the agent answers on the first ring, knows what job he is on, gives him the status of his RFI, and gets a human on the line within a minute when the question is real, he stops caring by the second call. Tell callers plainly they are on the firm's automated line — the disclosure costs nothing and several states now expect it.
It can look things up while it talks, which is the whole point of the 2026 change. In a design office that usually means read-only access to the RFI and submittal logs and to the principals' calendars. Keep it read-only. There is no reason a phone agent should be able to change an RFI status or issue anything.
This is the single best argument for instant answer in an A/E office. Plan reviewers call once, in the morning, and if they get voicemail they move on to the next application in the queue. An agent that picks up on the first ring, captures the jurisdiction, the permit number and the comment number, and pages the project architect right then will pay for itself on permit turnaround alone.
An answering service takes a message. It cannot tell a foreman that submittal 03300-2 came back approved-as-noted on Thursday, because it has no access to your logs and no idea what those words mean. The difference is not politeness or speed of pickup — it is whether the caller gets an answer or a promise of one.
Three weeks, in stages. Week one: put the agent on the after-hours and overflow path only — calls that go to voicemail today — doing nothing but taking a proper message and booking call-backs. Read every transcript on Friday. Week two: connect the RFI and submittal log, read-only, and let it answer status questions on two active jobs. Week three: add calendar booking for new-work inquiries and set the warm-transfer rotation. Do not put it on the main line during business hours until three weeks of transcripts stop surprising you.
CallSphere builds AI voice and chat agents that answer a firm's phone line and website chat 24/7, look up the status of a job or a request while the caller is still on the line, book the call-back or the intro meeting on the right person's calendar, and capture the lead with a full transcript. For a design firm the fit is narrow and specific: the 6:50 a.m. field call, the plan reviewer who calls once, and the developer who is calling three firms this morning. The engineering judgment stays exactly where your license says it has to.
Written by
Sagar Shankaran· Founder, CallSphere
LinkedInSagar Shankaran is the founder of CallSphere, where he builds production AI voice and chat agents deployed across healthcare, hospitality, real estate, and home services. He writes about agentic AI, LLM engineering, and shipping voice agents that handle real calls in production.
See how AI voice agents work for your industry. Live demo available -- no signup required.
Sports physical therapy and student health clinics in Pullman, Washington lose patients to missed calls every semester surge. How to answer every single one.
Bilingual family medicine clinics in Yakima, Washington field English and Spanish calls from harvest crews at all hours. An AI receptionist answers them all.
Physical therapy clinics in Astoria, Oregon juggle fishing-fleet injuries and summer tourism surges. How an AI answering service catches every missed call.
Dental practices in Salem, Oregon miss calls when state workers phone at lunch. A 24/7 AI receptionist books cleanings and triages toothaches every day.
Optometry practices in Newport, Oregon serve retirees, tourists, and the fishing fleet. An AI answering service books exams and triages urgent eye calls 24/7.
Therapy practices in Corvallis, Oregon lose new clients to voicemail and long waitlists. An AI intake line answers every call and fills openings automatically.
© 2026 CallSphere Inc. All rights reserved.
Made within San Francisco
Watch how CallSphere handles real customer calls, schedules appointments, and processes payments — live.
Try Live DemoBook a DemoCalculate Your ROI