A full dental practice, running itself from one dashboard.
Esipick Dental is our own practice management system, live at dental.esipick.ai. Intake chat, registration form, appointment booking, patient records, automatic SMS, and full analytics — not six separate tools, one system. It starts with Zara, the AI receptionist, greeting every patient and knowing exactly when to stop asking questions and get a human on the case.
Live at dental.esipick.ai · open the chat and try it yourself
One system, not six tools stitched together.
Every part of the front desk lives in the same product — the same database, the same dashboard, the same login.
AI intake chat
Bilingual, one question at a time, triages for genuine emergencies before it books anything.
Registration form
Full structured intake — complaints, medical history, medications, tooth chart. Contact info pre-filled from the chat.
Appointments
Today, upcoming, and unscheduled requests in one view. Staff confirm or cancel with one click.
Patient directory
Every patient in one record, grouped across visits — visit count, escalation history, and last seen.
Automatic SMS
Requested, confirmed, and cancelled notifications fire on their own — no one has to remember to text back.
Analytics
Booking funnel, AI-vs-human split, complaint types, and daily volume — updated live, no spreadsheet.
Three things a real front desk gets right that most booking tools skip.
Any system can take a booking. Fewer can tell the difference between a routine one and an emergency, keep a real patient record instead of a pile of chats, or meet a patient in whichever language they showed up speaking.
It reads for red flags, not just data
Right after the pain question, the bot checks five triggers: a rating of 7 or higher, facial swelling, fever with pain, a knocked-out or broken tooth, or trouble swallowing or breathing. Trip one and it sets escalate=true immediately, skips the rest of its script, and tells the patient a team member will call urgently.
It replies in Roman Urdu, unprompted
It reads the patient's very first message and picks the language itself. Type "mujhe dard ho raha hai" and it replies in Roman Urdu for the rest of the conversation. English stays English. No language picker, no toggle, no switching mid-chat.
Every visit lands on one record, not a new one
Sessions group by phone number into a single patient directory — visit count, escalation history, and last-seen date, all in one place. A patient who's called three times isn't three unrelated conversations to dig through, they're one row with a timeline.
From first message to a filed patient record, without a human touching most of it.
This is the full path a booking takes through the system — chat, form, staff review, confirmation, and the record it leaves behind.
Patient opens the chat
One open question to start, no form, no clipboard. The bot reads the patient's first message and replies in the same language, English or Roman Urdu, for the rest of the conversation.
The escalation gate
Pain rated 7+, facial swelling, fever with pain, a knocked-out or broken tooth, or trouble breathing — any one flips escalate=true and the bot asks just for name and number. Everyone else continues to name, preferred time, phone, email, and one medical question — never asked twice.
The registration form goes out
A link to the full intake form follows, pre-filled with name, phone, and email so nothing's retyped. The patient fills in the rest — complaints, medical history, medications, tooth chart.
Staff review in Appointments
Requests land in Today, Upcoming, or Unscheduled. Staff confirm or cancel with one click — no calling the patient just to lock in a time.
SMS fires on its own
A request receipt goes out when the patient books, then a confirmation or cancellation notice the moment staff act — three event types, all automatic. 12 SMS went out across the first sessions.
It all rolls up automatically
The patient joins the directory with a visit history. The booking, the escalation (if any), and the outcome all feed straight into Analytics — no one exports a spreadsheet.
The chat is the front door. This is what the staff actually sees.
Every session, form, appointment, and patient lands in one admin dashboard — Dashboard, Sessions, Appointments, Customers, Settings, and Analytics, all in the same login. Clinic name, bot name, and API key live in Settings, so the same product re-skins for a new practice without code changes.
| Patient | Time | Status |
|---|---|---|
| S. Ahmed | Today, 2:30pm | Urgent |
| M. Raza | Tomorrow, 10am | Confirmed |
| A. Khan | Fri, 4pm | Requested |
| Patient | Visits | Last seen |
|---|---|---|
| S. Ahmed | 3 | Today |
| M. Raza | 1 | 2 days ago |
| A. Khan | 2 | 1 week ago |
Live figures from the first sessions on dental.esipick.ai · pilot-scale, not a projection. Patient names in mockups are illustrative, not real records.
The intake, the admin system, and everything between are live today.
Chat, forms, appointments, SMS, patient records, and analytics all run on this stack right now. Deeper EHR/PMS integrations are the natural next step for a real practice deployment.
Live intake & admin system today · EHR/PMS integrations are Phase 2
Your front desk, running as one system.
Esipick Dental is live at dental.esipick.ai — intake, registration, booking, SMS, patient records, and analytics, all in one dashboard. Open the chat yourself: describe a bad toothache or a knocked-out tooth in English or Roman Urdu, and watch it stop collecting details and ask for your number instead.
"Esipick AI pricing is tied to business generated — you only pay for results."
Book a call