Everything people ask before they book.

It has to be, or we don't build it. We sign a BAA before anything starts. Patient information only ever passes through systems covered by one, so nothing gets pasted into a consumer chatbot. Every build comes with a one-page data map: what information goes where, who can see it, how long it is kept. If a vendor will not sign a BAA, we do not use that vendor.

Sometimes you genuinely don't, and the audit will say so. It is the cheapest outcome available to you and you should hear it from us. Software vendors build for their average customer and their features work inside their own product. Your expensive problem usually sits in the gap between four different systems. A gap starts where one vendor stops, so no vendor owns it.

It is built so that it cannot. You write and approve the script before go-live, and it only says things you have signed off. Anything clinical, urgent or unfamiliar goes to a person within seconds. You get a transcript of every conversation. If you dislike a sentence we change it the same day.

They hate it when it lands on them without warning. We bring the front desk in during the build, not on go-live day, and we start with the tasks they already complain about: the retyping, the hold queue, the same five questions forty times a week. What usually happens is the front desk ends up defending it, because the boring half of the job disappears and the half they actually like gets easier.

No, and I would be wary of anyone selling you that. What happens in practice is your existing team stops doing work a computer should have been doing, and the next hire never becomes necessary. It shows up as a hire you did not make. Your payroll this quarter looks the same, and you should know that going in.

That is fine. Healthcare is where we go deepest, because the paperwork is heaviest and the rules are strictest there. The same work applies to law firms, property managers, home services and clinics of every kind. Same audit, same fixed prices.

The audit is refundable if it cannot find three times its cost in recoverable time and revenue. Builds are fixed price, so you know the number before anything starts. Support is month to month on thirty days' notice. There is no long contract anywhere in this.

Two weeks to the plan. Another three to six to get the first thing running properly. Front Desk is usually answering calls within a month of signing, because it does not need access to clinical records before it starts earning.

Open Dental, Dentrix, Eaglesoft, Curve, Denticon and the cloud systems all have a route in. Some have a proper documented API, some go through a supported integration partner, and a few need a workaround that is more fragile than either. The audit tells you which one yours is, what that costs and what it rules out. If your system is genuinely closed we will say so rather than discover it halfway through a build.

Yes, because it tells them. Pretending otherwise is wrong and in several states it is now illegal. What we see in practice is that patients care far more that somebody picked up at seven in the evening than about who picked up. Anyone clinical or upset reaches a person within seconds.

The audit is $2,500, refunded if it cannot find three times that in recoverable value. Front Desk starts at $9,800 to build. Ongoing support runs $1,200 to $3,800 a month depending on your call volume and how many systems we are watching. You see every number before you commit to anything.

Single locations often see the fastest return, because one person owns the decision and there is no committee to convince. A missed new-patient call costs you the same whether you have one chair or nine.

Yes, before any protected health information moves anywhere. So does every vendor in the stack. If one will not sign, we do not use them. Every build ships with a written data map: what goes where, who can see it, how long it is kept and how it gets deleted.

No. Everything we build stays on the administrative side: scheduling, intake, verification, document handling, billing follow-up and patient communication. Anything clinical routes to a licensed person. We write that line into the scope of every engagement and we do not move it.

The major EHRs all expose a route in, through FHIR, a partner programme or a supported integration platform. Which one applies to you, what it costs and how long it adds is something the audit answers in writing before you commit to a build.

A virtual assistant service is people, billed hourly, who need training and who turn over. This is software that runs at two in the morning and costs roughly the same whether it handles ten calls or four hundred. For some tasks a good VA is still the better answer, and the audit will tell you which ones those are.

Usually about a month from signing. Front Desk is the fastest thing we build, because it does not need deep access to clinical records to start earning. It needs your schedule, your script and your escalation rules.

It spots urgency early and hands over. Warm transfer during hours, your on-call path outside them. You define what counts as urgent and we build to that list. We test this path against recordings of real calls, harder than anything else in the build.

Well, and better every quarter, though not perfectly. When it cannot follow something it says so and hands over. During the build we tune it against your own call recordings, so it learns how your patients actually speak.

It takes the phone off them. In most practices that is the difference between a front desk that is underwater and one that can look up and greet the person standing at the counter.

Not with patient information on a consumer account. The business tiers of the major products will sign a BAA and those are usable. The real risk in almost every practice is not the system you bought. It is a well-meaning staff member pasting a history into a free tool because it saves them twenty minutes. That is a tooling and training problem and you can fix it in an afternoon.

Every build ships with a one-page data map. Each piece of information, the systems it passes through, who can see it, how long it is kept, how it gets deleted. If that diagram cannot be drawn simply then the design is too tangled to reason about, and we change the design rather than the diagram.

No more than the system needs to work, and never to train anything. You set retention, it goes in the contract, and it is enforced in the code rather than promised in a PDF.

Several states go further than HIPAA, particularly on recorded calls and consent. The audit checks the rules for your state and your situation. It is also why disclosure that a caller is speaking to AI is standard in everything we ship rather than a setting you can turn off.

Anything with a phone that rings, paperwork that repeats and money that needs chasing. Law firms, property management, home services, veterinary, med spas, agencies and specialty clinics. The audit is the same shape whatever the industry.

If a full-time salary's worth of work is going into tasks a computer could do, you are the right size. If it is not, the audit will say so and we both save time. Below about five people the honest answer is usually to buy an off-the-shelf tool, and we will name the tool for you.

Agencies sell retainers and hours, which pays them to take longer. We sell a fixed-price plan and fixed-price builds. The plan stands on its own, and a fair number of people take it to their own developer.