
Parvessh Agarwal
Founder and Chief Executive
An entrepreneur at heart. He links business analysis, strategy, clear goals and ROI to practical technology.
LinkedIn →A website chatbot for your practice or provider group. It answers the general questions your front desk repeats, from content you approve, and hands everything else to your staff. It gives no medical advice, handles no patient health information and books nothing.
Set up and run for you monthly · Reply within four business hours (typical)
Brands our teams have delivered for
A healthcare chatbot answers general questions about your practice from content you approve. It covers services, opening hours, directions, how to book and insurance questions, then hands anything else to your staff. It gives no medical advice and handles no patient health information. We set it up and run it on a monthly plan.
We test it on your own work before you commit. These are facts about our company, not AI results.
Product names and marks are trademarks of their owners. Naming a technology means our teams build with it. It does not mean a partnership, certification or endorsement.
The assistant answers the questions your front desk gets every day, from content you approve. Anything clinical, such as symptoms, results or medicines, goes straight to your staff. It says so when it does not know.
A visitor who wants an appointment is told how to book, or is sent to your staff. The assistant does not connect to your booking, practice or records systems, so it cannot book, change or cancel an appointment.
If a visitor describes something that sounds urgent, the assistant does not discuss it. It tells them to call your practice, or emergency services if they cannot wait, and shows your phone number. You set the wording and the number.
The assistant answers general questions only and collects no patient health information, such as symptoms, conditions or medical history. Before any patient uses it, we agree in writing where conversations are stored, who can open the logs and how long they are kept.
Set rules decide when the assistant stops and hands over: clinical questions, complaints, urgent requests and anything it is unsure of. Your staff receive the conversation, so the patient does not repeat themselves.
We build tests from the questions your practice really receives, including the ones the assistant must refuse. You see the results and sign off before launch. Every conversation is logged to your retention policy, and each quarter we review handovers, logs and access with you. Your content and data stay yours. The setup, prompts and workflows stay with us.
We list the general questions your front desk answers, and the ones the assistant must never touch.
You approve the content it may answer from: services, opening hours, directions, how to book and insurance information.
Your team tries it, including the refusals. We fix what is wrong and you approve the launch.
We review conversations, fix errors, update the content when your practice changes and review handovers, logs and access with you each quarter.
This page is the practice and provider version of our healthcare chatbot. The pages below cover the service in full, the content it answers from and the price.

Founder and Chief Executive
An entrepreneur at heart. He links business analysis, strategy, clear goals and ROI to practical technology.
LinkedIn →
VP, Technology
Brings technical work, client updates and project management together, so work moves smoothly from brief to launch.
LinkedIn →Every engagement
Know who coordinates your engagement, who owns the work and how to escalate an issue.
All engagements. Roles may be combined and vary with your engagement.
Each one says where it applies and links to its full terms.
We typically respond within four business hours. Eligible engagements can typically start within two to three business days after scope, payment and required access are confirmed.
Business hours are Monday to Friday, 9:00 am to 6:00 pm IST, excluding published company holidays. Typical expectations, not guaranteed service levels.
Full termsYour materials remain yours. Bespoke deliverable rights, licences and handover are agreed before work starts.
All engagements.
Full termsKnow who coordinates your engagement, who owns the work and how to escalate an issue.
All engagements. Roles may be combined and vary with your engagement.
Full termsEvery delivery is reviewed before release by QA, your Project or Account Manager and a senior delivery lead, and you then review it against the acceptance criteria agreed at the start. Our specialists use AI to support delivery, with people responsible for reviewing the work. Applicable development work includes 30 days of corrective maintenance after production launch.
Your materials, data and accounts remain yours, and we prefer to work in advertising and analytics accounts you own, with access delegated to our team. Agreed ownership rights in bespoke deliverables transfer under the engagement terms and applicable payment; third-party software and assets keep their licences. We do not withhold customer-owned data or accounts over a payment dispute.
Cancellation, notice and any renewal terms are written into your proposal or statement of work before you accept it. If an engagement ends early, we hand over completed, paid-for work and list any unfinished work separately. For an eligible specialist trial, you can stop within the trial window and pay nothing for eligible trial hours.
Before work starts we agree how often you get updates, what the reports cover and who sends them. You know who coordinates your engagement, who owns the work and how to escalate an issue. For hourly and retainer work, time is recorded in Workstatus, so you can see the time records behind your invoice.
How we handle claims, credentials and your data: group credentials, dated ratings, how case figures are signed off, client permissions and data handling.
Every question falls into one of three groups. This table shows each group with an invented Example question and what the assistant does. The groups and the wording are agreed with your practice before launch.
| Example: a visitor asks | The assistant | What it does |
|---|---|---|
| What are your opening hours on Saturday? | Answers | Gives the hours you approved and your phone number. |
| Where are you, and where can I park? | Answers | Gives the directions and parking text you approved. |
| How do I book an appointment? | Answers | Explains how to book and sends the visitor to your booking page or your staff. It does not book. |
| Do you accept my insurance? | Hands over | Says which insurance plans you accept, from the list you approved. Coverage, eligibility, claims and costs go to your staff. |
| I have a complaint about my last visit. | Hands over | Passes the conversation to your staff. |
| I have had chest pain since this morning. What should I do? | Never does | Gives no advice. Says to call your practice, or emergency services if it cannot wait. |
| Can you tell me what my test results mean? | Never does | Gives no medical advice and cannot open records. Passes the question to your staff. |
These rows are an Example of the format, written for this page. Your questions, answers and handover wording are set with you.
This page states no AI figures. We add a case here only when the client approves it and the outcome is verified.
We publish a case only with the client’s written consent, and only with results that are verified.
It answers general questions on your website, such as services, opening hours, directions, how to book and insurance questions. It uses only content you approve and hands anything else to your staff.
No. Questions about symptoms, results or medicines go to your staff, with the conversation attached.
No. It is built to collect no patient health information. It does not ask about symptoms, conditions or medical history, and it does not open or show records. A visitor who starts to describe a problem is sent to your staff.
No. It explains how to book and sends patients to your booking page or your staff. It does not connect to your booking, practice or records systems.
Where conversations are stored, who can open the logs and how long they are kept are agreed in writing before any patient uses it, and reviewed with you each quarter. Logs are kept to your retention policy.
Ask five things. Does it collect any patient health information? Can it connect to booking or records, and what happens if it is asked to? What does it say to someone with an urgent problem? Who can open the logs, and for how long are they kept? Who owns the prompts and the setup if you leave? Our answers are on this page.
It is priced on the healthcare assistant rows of our rate card: a one-time build and a monthly plan. The rate card is linked on this page, and the proposal itemises both. More locations or languages are quoted from your brief.
We have not published an AI client result for healthcare yet, so we do not show one here. We will add one when a client approves it. Ask us about a similar project and we will explain how it would run.
Priced as a build for one support queue, answering from your own documents. A monthly support retainer keeps its answers accurate as your documents change.
Indicative: every figure is refined into an itemised proposal.INR figures shown excl. GST.
Tell us which general questions your practice answers most. We reply with a scope, what the assistant will and will not do, and a plan for the monthly run.
Reply within four business hours (typical) · NDA standard · Clear IP & Ownership Terms
Last updated