Common questions.

We do not publish pricing and we will not quote before we understand the work. A chat agent on a website and a voice agent wired into practice software with multi-step automation are different projects with different costs. Pricing is set in the proposal after the strategy call, and it is built around what the system is actually worth to your business.

It depends on scope: how many agents, how many systems we are connecting, and how much of your content already exists in a usable form. Timeline is set in the proposal alongside pricing, once we know what we are building.

Twenty minutes for the strategy call, access to the systems we would connect, and whatever content you already have — service descriptions, policies, FAQs, intake scripts. If that material does not exist yet, creating it is part of the work.

No. We connect to your CRM, practice management software, calendar and communication tools. Replacing systems is expensive and rarely the actual problem — the problem is usually that nothing talks to anything else. If you do not have a CRM, we can provide one as part of the solution.

The agents answer from a knowledge base built out of your own approved material, not from general AI knowledge. Scope is defined during the build, so when a question falls outside it the agent says so and routes to a person rather than guessing. You review test conversations before anything goes live.

The voice agents hold natural conversations and do not use phone menus. The chat agents answer specifically rather than generically. Both are configured to your tone and your terminology, and you hear and read test conversations before launch.

It says so, collects the details, and routes to a person with the context attached. That is a designed behaviour, not a failure mode — an agent that guesses is far more dangerous than one that hands off.

It is configured to recognise what you define as urgent and escalate immediately to the right person. Where safety is involved it instructs the caller to contact emergency services. It does not attempt to handle a medical emergency itself, and it never gives clinical guidance.

That depends on the configuration and is worth raising on the strategy call so we can scope it properly rather than assuming.

That is not what it is for. The agents take the repetitive volume — routine questions, intake, scheduling, the follow-up that never gets done — so your team spends time on the work that needs a person. What most clients gain is coverage: calls answered at nine at night, enquiries answered while everyone is with a client.

Everything lands as a record in your CRM or practice software, with the conversation or call summary attached to the contact. Nothing happens invisibly, and your team can see exactly what was said.

The agent only answers from content you have approved and declines outside it, escalation paths are agreed before launch, and you review test conversations first. Where it still falls short, we monitor and fix it — that is the optimisation stage, and it does not end at launch.

Yes. Handoff to a person is built in, and you can disable or limit the agent at any time. Bring specific scenarios to the strategy call and we will show you how the handoff is configured.

Yours, and your clients’ or patients’. In an engagement you are the controller of that information and we act on your documented instructions as a processor. Our privacy policy explains how we handle our own collection.

Handling health information brings specific legal obligations that depend on your jurisdiction and your practice. Raise it on the strategy call — we will tell you plainly what we can and cannot commit to in writing before you sign anything, rather than after.