— For healthcare
Dental practices, primary care offices, specialty clinics, telehealth and aesthetic providers. A patient hits your website at 9pm wanting a cleaning, a same-week sick visit, or a derm consult — Alma is the conversation that catches them. The bot asks for the visit reason, preferred time, and insurance info, then routes the request to the PMS or EHR your front desk already lives in. The phone keeps ringing for the people who'd rather call; the rest book themselves.
/HEALTHCARE · 10 TEMPLATES · WEB WIDGET LIVE · MESSENGER + IG IN DEV
— Who runs it
Built for the small-to-mid practice that doesn't have an IT team: dental primary care specialty clinics telehealth aesthetic — hospital systems with HIPAA-bound patient data flows are not the buyer here.
/A — A REAL PRACTICE
Robert's a dentist with a four-chair practice, two hygienists, one front-desk lead. The phone rings during cleanings. Voicemail piles up by lunch. He didn't want a live-chat tool that pings staff on Slack — he wanted a chatbot that finishes the conversation, gets the patient to commit to a visit type and a time window, and hands the request to the front desk as a clean intake row.
The bot asks four things: cleaning, checkup, whitening, or something else? · new patient or established? · insurance carrier (or self-pay)? · ASAP or routine, and what time of day? Then it asks for a phone number to confirm. The conversation that landed an hour ago: a patient asked about a cleaning, picked April 30 at 3pm, said she had Delta Dental. The front desk confirms next morning by phone — same path the practice already used, just with the appointment request already written down.
Pick the dental, primary care, or specialty template. Tweak the visit reasons. Paste the widget. The first patient books overnight.
— Three conversations, three specialties
Dental · Smile Studio
Primary care · 3-provider family practice
Dermatology · specialty clinic
/B — 10 HEALTHCARE TEMPLATES
The Healthcare category in Alma ships ten starter graphs written by operators who've actually run a front desk. Pick the one that fits — a dental practice grabs the dental office bot, a primary care office grabs appointment scheduling and patient intake, a telehealth provider grabs the symptom checker. Edit the visit reasons, the intake fields, and the routing destination. The library is on every paid tier — no "healthcare add-on" upcharge.
Most practices are live in under 30 minutes. The dental, primary care, and specialty templates are already wired with the right intake fields.
/C — WHERE THE REQUEST GOES
The bot is a marketing-layer intake form. The chart, the schedule of record, the claim — those still live in your existing tooling. What Alma does is finish the conversation, write a clean lead row, and push that row to the place your front desk already works. Three patterns most practices use:
For the schedule of record, the route is a webhook or Zapier into the PMS / EHR. We do not have native integrations with Dentrix, Eaglesoft, Open Dental, Athenahealth, NextGen, eClinicalWorks, or Epic. Most modern PMS/EHRs accept inbound rows via Zapier or a webhook your IT contact wires up once. If your PMS doesn't have an inbound API, the lead lands in the email + sheet path and your scheduler handles the data entry the same way they do for phone calls.
Channel-wise, the website widget is live. Facebook Messenger and Instagram DMs are in development pending Meta review — when they ship, the same flow runs on every surface, no separate authoring.
— Compliance, plainly stated
The honest answer most chatbot vendors won't give you: a public-facing booking bot is a marketing-layer tool, not a covered entity's data plane. Patients arrive at smilestudio.com and ask about a cleaning. They might mention they've got Delta Dental. They might describe a sore throat. None of that is the same as PHI sitting in your chart system, and treating a website chatbot like it is overstates what we do and confuses your compliance posture.
What Alma does: collects appointment requests and intake answers from a public-facing widget; encrypts data at rest; isolates each workspace's conversations from every other workspace's; gives you data export and deletion on request; routes the lead to where you already keep the chart. What Alma is not, by default: a Business Associate, a chart system, a payer-verified eligibility service, or a substitute for the existing PMS/EHR your practice runs on.
For a practice that needs a Business Associate Agreement on file — most don't, for a marketing-layer bot, but some compliance teams require one — that's an Enterprise-tier conversation. We won't promise specifics on a marketing page; talk to sales and we'll walk through what the regulated setup looks like for your situation. The short version: you configure what questions the bot asks, where the answers route, and how long they're stored. Compliance is a shared responsibility — we make the data plane defensible; you make the operational decisions about what to collect.
Sheets, email, SMS via CampaignCNX+, Zapier into your PMS, your own webhook. The lead lands where the work already happens.
— Healthcare FAQ
Plain answers. Where the answer is "no, but," we say so.
Out of the box, no — Alma is a marketing-layer chatbot for your public-facing website. PHI lives in your PMS/EHR, not in Alma. A Business Associate Agreement is available on the Enterprise tier; talk to sales for the regulated setup. We won't claim "HIPAA compliant" on a marketing page just because we encrypt at rest, because that's not what the term means.
Yes via Zapier or an outbound webhook your IT contact wires up. We don't ship native integrations with Dentrix, Eaglesoft, Open Dental, Athenahealth, NextGen, eClinicalWorks, or Epic today. Most modern systems accept inbound rows through Zapier or a webhook; the practices that don't have an API at all use the email + Sheet path.
The bot asks the questions — carrier, plan type, member ID if you want it. It doesn't verify against payer eligibility databases in real time; that's a different category of tool. What you get is a clean intake row your scheduler can run through your normal verification process.
You configure the flow. The Appointment Reminder template captures reschedule and cancel intent and routes those to staff with the patient's preferred new time. The bot doesn't write directly back to the PMS calendar — your front desk makes the change, same as a phone reschedule.
Same shape as in-person. The bot captures the patient's preferred time, the visit reason, and the platform they expect to use (your portal, Zoom, etc.), then routes the request to the scheduler. The Symptom Checker template is the most common starting point for telehealth-first practices.
Via webhook setup, yes — your IT contact wires the outbound webhook to the EHR's intake endpoint, and the conversation lands as a structured note or task. We can give your team the payload schema. For practices without that integration in place, the conversation lives in Alma's lead inbox and gets re-keyed by the scheduler.
The channels are scaffolded in the codebase and pending Meta's app review. We don't have a date we trust enough to publish, so we don't. The website widget is fully live today; that's the only channel we'll ask you to buy Alma for. When Meta approves, the same flow runs on every surface.
Conversations are isolated per workspace — no other practice's account can see your data. Encrypted at rest, TLS in transit. You get standard data export and deletion on request. You decide retention windows and what fields the bot asks for. The shorter answer: collect only what you need to triage the visit, and route the chart-level data to the system that's actually a chart system.
— Start free
14-day free trial, no card. Pick the dental, primary care, or specialty template. Edit the visit reasons in your voice. Paste the widget on your practice site. The next time the office is closed, the bot is still working.