Healthcare CRM Software: The Appointment and the Record

A healthcare CRM is bought for the appointment and audited for the record. The published seat prices are the easy half of the decision. The half that decides the purchase is the split between two different kinds of conversation: the general questions a website can answer without ever touching a patient record, and the ones that must reach a person because they involve a name, a condition, a date, or a payment.

What "healthcare CRM" actually means

The phrase covers two quite different products. A patient CRM system is built around a clinical record: appointments, encounters, consent, ICD or SNOMED codes, and an audit trail that survives an inspection. A healthcare CRM solution in the general sense is often a sales tool repurposed for a clinic, with a patient record bolted on through integrations.

That distinction matters because the questions each one can answer are different. A patient CRM can answer "when is my next appointment" because it owns the schedule. A sales CRM being used in a clinic usually cannot, because the schedule lives in the practice management system and the CRM only sees what gets pushed into it.

Four products appear most often in shortlists for healthcare CRM solutions. Salesforce and HubSpot both sell versions aimed at healthcare. Zoho CRM and Pipedrive are general tools that clinics pick because the seat price is lower and the workflow is closer to a sales pipeline.

Published ladders, billed annually

What a 12-seat practice pays each year

Bars share one scale. Max scale $14,460.

HubSpot Sales Hub, Professional $90 per seat per month + $1,500 onboarding

$14,460 a year for 12 seats, including the $1,500 onboarding fee.

Salesforce Sales Cloud, Pro Suite $100 per user per month

$14,400 a year for 12 seats.

Pipedrive, Premium $59 per seat per month

Per seat per month, billed annually as $708.

Zoho CRM, Professional $23 per user per month

$3,312 a year for 12 seats.

Asyntai, Standard plan $139 per month, 15,000 messages

Standard is $139 a month for 15,000 messages.

The split that decides the audit

Two halves of a healthcare conversation

A website can answer

General questions

Hours, location, parking, insurance accepted, what to bring to a first visit, prep instructions, after-hours line.

Reads only the clinic's public pages. Never touches the patient record. This is the lane Asyntai sits in.

Must reach a person

Questions about the patient

My lab results, my prescription, my appointment, my referral, my balance, anything tied to a chart.

Routes straight to your team, with the transcript attached.

Published prices, side by side

Salesforce, HubSpot, Zoho and Pipedrive all charge per seat; Asyntai is priced by message volume, so the bill follows the questions rather than the number of staff who need to read the answer. We make Asyntai, so read that row as a disclosure.

The headline numbers mislead. Salesforce at $25 looks cheap next to its $550 top tier; the actual mid-range for a working sales team is $100 (Pro Suite). HubSpot's $7 Starter looks cheaper than anyone until you add the $1,500 onboarding fee on Professional, which is required. Zoho and Pipedrive both publish an annual-bill discount that is real but easy to miss when the monthly figure is the one quoted.

What a 12-seat practice actually pays

Prices per seat look small. The annual bill for a real team is the figure a procurement officer needs. Use a 12-person front-and-back office team as a worked example: two receptionists, four administrators, three care coordinators, two managers, one clinician with read access.

None of these figures include the implementation. A healthcare deployment usually needs an integration into the practice management system (PMS) or electronic health record (EHR), a consent workflow, and at least one round of penetration testing. Those costs are not in the price ladder because they are negotiated separately.

The two halves of a healthcare conversation

The first half is general: opening hours, parking, which insurance you accept, what to bring to a first appointment, how to request a copy of a record. None of that touches a patient. It can be answered from the practice website, with no read access to the EHR, and the answer can be given at 11pm without a person on the other end.

The second half is clinical: anything that names a patient, a condition, a medication, a date of birth or a payment. That conversation must reach a person who is authorised to see that record, and the system holding it must keep an audit entry. A website chatbot is the wrong tool for this half, because the conversation is the record.

The mistake most practices make is choosing one product for both halves. They buy a clinical CRM and route every "what time do you close" question through it, paying a per-seat licence for a member of staff to answer a question the website already had. Or they bolt a chatbot onto the website and discover, after the first complaint, that it is logging patient names into a system that was never audited for that.

What each product is allowed to hold

Salesforce sells Health Cloud as an add-on to Sales Cloud, with HIPAA-eligible infrastructure on its higher tiers and a Business Associate Agreement (BAA) available. The seat price above covers Sales Cloud only; Health Cloud is priced separately and is sold through enterprise contracts.

HubSpot offers a healthcare shape on Enterprise with a BAA available on annual contracts, which is why Enterprise is the tier healthcare buyers end up on rather than Professional. Without the BAA, putting protected health information (PHI) into HubSpot is not a defensible position.

Zoho CRM and Pipedrive do not publish a healthcare-specific tier. Both can hold patient data with the right configuration, but neither signs a BAA in the same way Salesforce and HubSpot do on their enterprise contracts. A clinic that wants one of these as the patient record needs its own data protection agreement and a clear answer to who audits access.

The split that actually works

The first two rows are the half a website chatbot can carry. The other four rows are the half a patient CRM or EHR is paid to hold. A patient CRM software choice that tries to do both halves in one product usually ends up with a chatbot logging patient names into a sales pipeline, which is the failure mode regulators and patients notice first.

Where an automated agent fits

The first two rows above are where a free chat widget for your website earns its place. They share four properties: the answer is published, the answer does not name a patient, the answer does not change between callers, and the answer does not need to be written back to any clinical system.

Asyntai answers those questions against the practice website. It installs as a script tag, holds OIDC single sign-on including Entra and Google, supports per-tab permissions and per-website scoping, and runs an append-only audit log. Configurable PII redaction is a setting, not a prompt instruction. Chat retention is configurable with auto-delete.

The pricing is by conversation volume rather than by seat, which is why it appears in the table next to per-seat CRMs. The same 12-person practice that pays $3,312 to $14,400 a year for a CRM would pay for the website half from a $39 Starter plan or a $139 Standard plan, depending on monthly chat volume, and would keep the clinical CRM only for the rows that genuinely need a patient record.

What an automated agent must not do is take a clinical question and pretend to answer it. The configuration should send anything that names a patient, a condition, a medication, or a payment to a member of staff, by a route that produces an auditable record. That is the line, and crossing it is the failure pattern most regulators eventually see.

What changes the answer

Volume changes the answer. A single-site practice with three receptionists has a very different front-door shape from a 12-clinician group with four sites. The single-site practice can usually run on the lower Salesforce, HubSpot or Zoho tiers; the group practice is usually on Professional or Enterprise before the first renewal because the lower tiers run out of automation or seat allowances.

Integration depth changes the answer. A practice that wants the CRM to hold the schedule needs a PMS or EHR integration, which is implementation work and ongoing maintenance. A practice that only wants the CRM to hold enquiry leads before the first appointment does not, and can run on a general CRM at the published seat price.

BAA availability changes the answer. Salesforce and HubSpot both offer BAAs on their higher tiers; Zoho and Pipedrive do not in the same form. A clinic that needs the CRM to hold PHI needs the BAA, which means the higher tier, which means the per-seat figure is not the headline figure.

Opening hours change the answer. A practice that takes calls 8am to 6pm and routes everything else to voicemail will have a different volume shape from a practice that publishes an out-of-hours number. The first can let the after-hours half of the website answer general questions automatically; the second needs to think about who carries the phone.

The mistake most clinics make

The single most common error is buying a patient CRM system and then routing general questions through it because it is the only system with a chat widget. The cost is paid twice: the seat licence for the staff member who answers, and the audit entry written against a record that should never have held the question.

The second most common error is the reverse: bolting a chatbot onto the website without configuring a hard stop on anything that names a patient. The chatbot then collects names, dates of birth and medication questions into a system that was not designed to hold them, and the failure is discovered during an audit or a complaint rather than during procurement.

Both errors come from the same place: the choice of one product for both halves of the conversation. The fix is to split the conversation by what it contains, not by which inbox it lands in.

How to choose

1. Write down which questions must reach a person. Anything that names a patient, a condition, a medication, a date of birth or a payment goes on this list. It is usually shorter than people expect.
2. For the rest, measure what the website already has. Most practices have the answer to "what time do you open" in three places on the website already. An automated agent reads those pages; it does not need a new content project.
3. For the clinical half, decide which system holds the record. Salesforce Health Cloud, HubSpot Enterprise with a BAA, or the practice management system itself. The CRM only enters if it is the system of record or is integrated tightly enough that the audit survives.
4. Price the two halves separately. The website half is priced by conversation volume; the clinical half is priced per seat with an onboarding and integration line. The combined bill is what procurement needs, not the headline seat figure.
5. Configure the boundary. The website agent must route anything on the clinical list to a person, by a route that produces an auditable record. The route is configured; it is not left to the model.

That is the shape of a healthcare CRM purchase that survives the audit. The seat prices are the easy half. The split between what the website can answer and what must reach a person is the half the regulator sees.