Free Medical Bill Chatbot Template: Explain Charges

The Medical Bill Explainer is a free Conferbot template that helps patients understand a medical bill they have already received. It simplifies the complexity of medical billing with an AI-powered conversation that decodes charges, walks through insurance claim questions and gives instant answers to the questions billing offices hear every day - enhancing patient trust and reducing billing confusion.

Be precise about scope. This chatbot is an administrative assistant: it informs and routes. It gives no medical advice, diagnoses nothing, decides nothing about what a patient owes, and replaces neither your billing team nor your insurer's determination of benefits. Every explanation is text your staff write into the nodes, so the language matches your own statements.

The problem is familiar. A patient sees a line that says "facility fee" or "adjustment" and cannot tell whether it is a mistake, a discount or something they owe, and their only option is to call and wait on hold. Deployed on your website widget or on WhatsApp, this template gives a structured explanation at 9pm on a Sunday and escalates only when a person is needed. Typical operators are hospital financial services teams, independent practices, dental and specialty groups, revenue cycle vendors and billing advocates. Adjacent tools sit in the healthcare and wellness template library.

This template ships as a real published node graph. Below is the path a patient actually takes, with the real prompts and options. You can rewrite every line in the builder, but this is what runs out of the box.

1. Welcome

The welcome node opens with "Welcome to the Medical Bill Explainer! I'm here to help you understand your medical bills, insurance claims, and charges. Let me guide you through the process." No input is requested yet, keeping the first screen reassuring rather than interrogative.

2. The routing question

A single-choice node asks "How would you like me to help you today?" with four buttons: Explain my medical bill, Understand insurance coverage, Dispute a charge and Payment options. The answer is stored in an assistance-type variable and each button opens its own branch. This node is the spine of the template.

3. Branch A - Explain my medical bill

A file-upload node asks "Please upload a copy of your medical bill for me to analyze," so the patient attaches a photo or PDF. The bot confirms with "Thank you for uploading your bill. I'm analyzing it to break down the charges and explain each item," then asks "Which part of the bill would you like me to explain first?" - Total charges, Insurance adjustments, Patient responsibility or Individual service charges.

• Total charges presents the charge summary and asks whether the patient wants any single charge explained, replying "I'll explain that charge for you."
• Insurance adjustments returns "The insurance adjustments reflect the contracted rates between your healthcare provider and insurance company. This shows the discount applied to your charges."
• Patient responsibility returns "Your patient responsibility includes your deductible, copay, and any non-covered services. Let's break these down."
• Individual service charges opens a second menu - "Which service charge would you like me to explain?" - offering Medical procedures, Laboratory tests, Facility fees and Medications.

4. Branch B - Understand insurance coverage

The bot asks "What is your insurance provider?" as free text, then "Please enter your policy number:", and acknowledges with "Thank you. I'm retrieving your insurance coverage information." The template connects to no payer eligibility system - this branch collects details and hands a pre-qualified enquiry to a human.

5. Branch C - Dispute a charge

"What is the reason for disputing the charge?" offers Incorrect charge, Service not received, Insurance should cover and Duplicate charge, then the bot asks "Please provide specific details about the charge you're disputing:". The result is a structured dispute record - reason code plus narrative - instead of a voicemail someone has to decode.

6. Branch D - Payment options

"Which payment option would you like to learn more about?" offers Payment plan, Financial assistance, Immediate payment and Insurance claim status. This branch is the most worth customising: the answers depend entirely on your own hardship and instalment policies.

7. The loop and the close

Almost every branch converges on one yes/no node: "Would you like help with anything else on your bill?" with Yes, I have more questions and No, I'm done. Yes returns the patient to the main menu; No ends with "Thank you for using the Medical Bill Explainer. If you need help in the future, don't hesitate to ask!"

8. The billing specialist handover

The template includes a human handover node at medium priority with automatic assignment and the tags "billing" and "support". It reads "I'll connect you with a billing specialist who can help with your specific questions," followed by "A billing specialist will be with you shortly." In the shipped graph this node exists but is not yet wired into a branch - connecting it, usually from the dispute branch and the "Yes, I have more questions" path, is the most valuable edit you will make. Handover and the unified inbox are on every plan, including the free plan.

A structured conversation produces structured answers. Every variable the flow writes - assistance type, insurance provider, policy number, dispute reason and details, payment option - appears against the conversation in the inbox and can be exported. Chatbot analytics then show which branch patients pick most, usually the first honest signal about which part of your statement confuses people.

Setup is configuration, not development. The builder is drag-and-drop; no code is required.

Open the template. Create a bot from Medical Bill Explainer and the full node graph loads into the canvas, so you edit a working conversation immediately.

Rewrite the explanation nodes. The adjustments message, the patient-responsibility message, the totals summary and the service-charge menu are where your team's expertise goes. Use the wording your staff use on the phone and the exact labels printed on your statement - if it says "contractual allowance", the bot should say that too.

Fill in the payment options branch. Write your real instalment terms, financial-assistance criteria, payment instructions and how to check claim status. This branch turns confusion into resolved balances.

Wire the handover node. Connect it from the dispute branch, the policy-number branch and the "more questions" path, then set priority and tags so conversations land in the right queue. See live chat and handover.

Add a scope and privacy notice. A message node after the welcome should say plainly what the bot is: an explanation and routing assistant, not a determination of what is owed, not medical advice, not a substitute for your billing office. Patients are asked for a policy number, so be explicit about what is collected.

Connect a channel, test, publish. Put it on your website billing pages and test every branch as a patient would, including the upload. The Free plan covers 600 conversations and one chatbot - enough to validate the flow before paying for anything.

Export every answer. A Google Sheets node at the end of the dispute branch lands each case as a row with the reason code, narrative and timestamp, so your team works a queue instead of an inbox. A Gmail node notifies the billing office immediately, and a webhook node posts the same data into a ticketing system - webhooks and API access require Starter or above, covered on the API and webhook integration page.

Split payment options by balance size. A condition node can send small balances to a pay-now link while larger balances see an instalment plan and financial assistance first, reading variables the flow already captured.

Add insurer-specific branches. The insurance-provider answer is free text today; converting it to a choice node listing the payers you contract with lets you give payer-specific guidance and route to the staff member who knows that payer best.

Tune the handover routing. Replace the generic "billing" and "support" tags with something your team queues on and raise priority for disputes; team management controls who sees which queue. A rating node before the closing message tells you whether the explanation landed - the CSAT dashboard requires Pro.

Localise it. Billing confusion is worse when the statement is not in the patient's first language. Duplicating the branch with translated copy is usually the highest-impact accessibility change a billing team can ship in 2026.

Every channel is on every plan with no gating, so the only question is which suit a billing conversation.

The upload step works best where photographing paper is natural; where it is awkward, a condition can skip it and go straight to the charge-breakdown menu. Omnichannel deployment runs one flow everywhere, and rich media lets you attach a sample annotated statement to the explanation nodes. Worth pairing with the appointment scheduling bot, the pharmacy chatbot and the dental practice chatbot; for clinical rather than financial questions, send people to the telehealth triage system or symptom checker instead.

Being clear about limits is what makes a billing bot trustworthy, so say them in the conversation rather than burying them in a policy page. It gives no medical advice and does not comment on whether care was appropriate; route anyone describing symptoms to a clinical contact. It does not adjudicate - nothing it says changes what an insurer pays or what a patient owes. It explains the categories on a statement and records a dispute; a human decides the outcome.

It connects to no EHR, claims clearinghouse or payer eligibility API; the insurance branch simply collects the provider and policy number so a person can look them up. Conferbot does not present this template as HIPAA-compliant or BAA-covered, so decide with your own compliance team what may be collected in a chat window and trim the flow to match.

It does not replace your billing office either. The goal is a smaller, better-prepared queue: routine explanations handled instantly, and every remaining conversation reaching an agent with the document, the reason code and the patient's own words attached.