Writing the Knowledge Base for Your Clinic's AI Assistant

Picture a gynaecologist whose vendor has set up an AI assistant for her. Ask it, as a patient would, "Is it safe to travel in the seventh month?" It can reply with a confident paragraph of general advice picked up from somewhere. Not from her. She has never seen it.

That is the danger of an AI assistant without a proper knowledge base. It does not stay quiet when it does not know. It fills the gap with whatever sounds right.

In Rich Doctors Walk Away, building the AI's knowledge carefully is step two of the five-step build, right after mapping the patient journey on paper. It is the step that decides whether your assistant is a safe front desk helper or a liability with your name on it. Here is how to write it.

What is a knowledge base, in simple words?

It is the set of documents your AI assistant is allowed to answer from. Think of it as the training file you would give a new front desk person on day one, written so clearly that someone who has never visited your clinic could answer patients correctly.

The assistant should answer from this, and only this. If the answer is not in the knowledge base, it hands the conversation to a human.

What should go into it?

Here is the structure I use. Write each section in short, plain sentences, the way you would want it said to a patient.

1. Clinic basics. Name, full address, a landmark, parking, the Google Maps link, phone numbers, and which number to use for what.
2. Timings. OPD days and hours, for each doctor if they differ. Holidays. How to reach someone when closed.
3. Doctors. Each doctor's name, qualifications, years in practice and the problems they see most. Facts only, no "best" or "No.1" claims.
4. What the clinic treats. In simple words. "We see women for pregnancy care, periods-related problems, PCOS, menopause and gynaecological surgery." No promises about outcomes.
5. Consultation fee. The exact amount, what it includes, and whether a follow-up visit is charged.
6. Fee ranges. Only what is on your written fee sheet, with the line "the doctor will give the exact plan and fee in writing after the consultation."
7. Payment options. Cards, UPI, and any lending partners for EMI, stated as information, not as a hook.
8. How to book, reschedule and cancel. Exactly how it works.
9. What to bring. Previous reports, scans, medicine list, ID for insurance.
10. Preparation instructions for specific visits or tests, written and approved by the doctor, word for word.
11. Insurance and TPA. Which panels you are on, what the patient needs to bring.
12. The twenty most common questions, each with an approved answer.
13. Handover rules. Exactly when the assistant must hand over to a human, and what it says when it does.

How do you find the twenty most common questions?

Do not guess. Go to the source.

• Export the last three months of WhatsApp chats and read them.
• Ask the front desk to write down every question for one week.
• Listen to ten recorded calls.

You will find the same questions again and again: "kitna lagega?", "doctor kab baithte hain?", "is a lady doctor available?", "can my husband come in?", "do you take my insurance?", "what should I bring for the first visit?". Write one approved answer for each.

What should you leave out?

This list protects your patients and your registration.

Read the current NMC guidelines yourself, and make sure every line in the knowledge base is something you would be comfortable seeing in a screenshot.

How should approved answers be written?

Each one short, warm and in your clinic's voice. It should answer the question, and where it fits, offer a next step.

Example of a weak answer: "Fees vary. Please visit the clinic."

Example of an approved answer: "The consultation with Dr Deshpande is ₹1,000 and includes a full examination and a discussion of your options. If treatment is needed, the doctor will give you the plan and the exact fee in writing. Would you like me to check the next available slots?"

For anything clinical, write the handover line itself, so the assistant says it consistently: "That is a question the doctor should answer after understanding your situation properly. I am connecting you to our team now, and they will help you book a consultation or speak to the doctor on duty if it is urgent."

Why must the doctor sign off every line?

Because every answer goes out in your clinic's name. The doctor does not need to write the knowledge base. The practice manager or front desk lead can draft it. But the doctor reads every line before it goes live, and signs and dates the final version.

Then set a simple review rhythm:

• Every week for the first month, read a sample of real conversations and correct any wrong or vague answer.
• Every time something changes, fees, timings, a new doctor, update the knowledge base the same day.
• Every quarter, a full read-through by the doctor.

Example: say your fee sheet changes on 1 April, the date you fix for your annual price review. If the knowledge base is not updated that day, the assistant will quote last year's fee to every patient who asks. One line of update, the same morning, prevents a week of awkward corrections at the desk.

Our CRM, WhatsApp and AI team writes knowledge bases with clinics and builds the guardrails around them. The full five-step build is in Rich Doctors Walk Away, and the gynaecology page shows how this fits a women's health practice.

The short version

• The knowledge base is what your AI is allowed to say. Nothing outside it.
• Include basics, timings, doctors, fees from the fee sheet, payment options, booking, preparation and twenty approved answers.
• Leave out medical advice, unlisted prices, offers, patient stories and promises.
• Write a clear handover line for anything clinical.
• The doctor signs off every line, and updates happen the same day things change.