Meet us at eCW National · Oct 23-25
2care.ai

Front desk

An AI chatbot for clinic websites that books the visit.

Answers questions from your own content and books real open slots, day and night.

Clinic website with 2care chat

riversidefamilymed.com

Riverside Family Medicine

Ask Riverside

Web visitors who get an answer book. Web visitors who wait leave. Chat turns the traffic you already have into appointments with no extra ad spend.

24/7

answers on your own website

Live

open slots booked from the chat

What lands in your CRM

Every chat becomes a lead record.

The patient's details, the reason for their visit and the outcome of the chat are written to the CRM as the conversation happens, not typed up later.

Source and time attachedEach lead shows it came from website chat and when, alongside the page and campaign that brought the visitor in.
Consent stored with the recordThe consent the patient gave before sharing details is saved on the lead with its timestamp.
Outcome, not just a transcriptBooked, needs a call back or question answered. The status tells your team what to do without reading the whole chat.

New lead from website chat

Name
Elena V.
Phone
(555) 014 2290
Reason
New patient visit
Source
Website chat, 9:47 pm
Booked
Appointment
Fri 11:00, new patient
Deposit
$25 paid
Plan stated
Commercial PPO
Consent
Recorded
Pipeline stage
Booked

Speed to lead follow up skipped, the patient is already booked.

The knowledge base

Answers built from what your practice publishes.

The assistant only knows what you give it. Setting that up takes an afternoon, and the material stays yours to edit.

How the knowledge base is built

  1. 1

    Website import

    Services, hours, providers

  2. 2

    Uploaded documents

    Plans, policies, prep notes

  3. 3

    Topics

    What the widget opens with

  4. 4

    Reviewed answers

    Checked before go live

Update a document and the answers follow it.

Import your website

Your existing pages on services, providers, hours and locations are pulled in as the starting point.

Upload what is not online

Insurance lists, new patient paperwork, fee and cancellation policies, preparation instructions for common visits.

Topics patients pick first

The widget opens with topics you choose, such as booking, insurance or new patients, so visitors start in the right place.

From first message to a booked visit

The flow builder sets the path a patient chat follows. A typical new patient path looks like this.

01

The visitor picks a topic or types a question

Questions are answered from your knowledge base. Booking intent moves the chat into the booking flow.

02

Consent, then details

The patient agrees to share details, then gives name, phone, date of birth and reason for the visit.

03

A real slot is chosen

Open times of the right visit type are read from your schedule. The patient picks one and it is held.

04

Deposit where you require it

A secure payment link collects the deposit inside the chat. No deposit rule, no payment step.

05

Confirmation and handover

The booking is written to your system, the patient gets a text confirmation and the intake form link, and the lead is updated.

One inbox for every chat

Sorted by what the patient wanted.

Chats sit in the same inbox as calls, texts and social messages, tagged by intent so the right person picks up the right ones.

Intent tags on every threadNew patient, pricing, reschedule, insurance. Filter the inbox to the work your role handles.
Take over at any pointA staff member can step into a live chat, and hand it back to the assistant when the question is settled.
Nothing dropped overnightChats that ended without a booking are flagged for a call back the next morning, with the full conversation attached.

Website chats, last 24 hours

PatientStatus
Elena V.Working
Marcus D.Working
Sofia K.Working
Tom H.Working
Grace N.Working

Same inbox as calls, texts and social messages.

Scope

What the chat handles, and what it hands over.

A clinic website chat should be useful without pretending to be a clinician. The line is drawn in the same place every time.

Handles in the chat

  • Hours, locations, parking and directions
  • Which plans the practice accepts, from your list
  • Services offered and which provider sees what
  • New patient booking, rescheduling and cancelling
  • Deposits and cancellation policy
  • Preparation instructions you have published

Hands to your team

  • Symptoms, diagnosis or treatment advice
  • Anything that sounds urgent, which gets your emergency guidance first
  • Billing disputes and balance questions on an account
  • Plans not on your list, or coverage edge cases
  • Any question the knowledge base does not answer

Handovers carry the full conversation, so nobody asks the patient to repeat themselves.

After hours

The evening traffic, counted.

A large share of website visits arrive after the front desk closes. These are the numbers worth watching once the chat is live.

Example: one month of after hours chat

After hours chats

212

Booked in chat

58

Deposits taken

$1,450

Morning call backs

34

Chat outcomes

BookedAnsweredCall backLeft

Illustrative figures for layout only, not customer results.

Chats started after closeHow many conversations began outside staffed hours, the ones that used to become a voicemail or a form.
Bookings made without staffAppointments booked end to end in the chat, with deposits collected where required.
Handed over by morningChats that need a person, queued with context so the first hour of the day is call backs, not detective work.

See it work

Every clinic lead phoned back within five minutes

A web enquiry arriving and being called back before the patient has closed the tab and moved to the next practice.

Before it goes on your site

Questions practices ask about website chat.

From your own knowledge base: pages imported from your website and documents you upload, such as your insurance list, new patient checklist or fee policy. The assistant answers from that material and says so when it does not know, rather than guessing.

It books. The flow builder connects to live open slots in your schedule, so the patient picks a real time and the booking is written straight into your system. Where your policy calls for a deposit, it is collected in the same chat.

The chat answers practice questions: hours, location, insurance, services, booking and preparation. It does not diagnose or give medical advice. Anything that sounds urgent gets your emergency guidance, and clinical questions are handed to your team with the conversation attached.

Consent is required before the chat collects personal details, and the consent is recorded on the lead with a timestamp. Patients who decline can still read answers to general questions.

Yes. Every chat sits in the same conversation inbox as calls and messages. A staff member can take over at any point and hand back to the assistant when they are done.

It is an embeddable widget added with a short snippet. It works on most website builders and custom sites, and you choose the topics patients see when it opens.

It falls back to a short form that captures the patient's name, phone and reason, so the enquiry still reaches your team instead of the visitor leaving.

Built for regulated healthcare, in every market we operate in

HIPAA compliant

HIPAA

United States

BAA available on request

GDPR compliant

GDPR

UK & Europe

DPA available, data hosted in the EU/UK

DPDP compliant

DPDP

India

Data residency in India

See it on your own website. Book Demo.

30 minutes, on your own workflows. No commitment.

  • 95+ integrations and EHRs
  • ·Live in weeks, not months
  • ·HIPAA, GDPR and DPDP