Stages one to three and five to six are service. Stage four is care, and the CRM plays no part in clinical decisions. That simple division answers most design questions.
Where should booking live?
Most hospitals and clinic groups already run a clinic management or hospital information system that holds the real schedule, the patient's medical record and billing. That system stays the record. The CRM should not hold a second, competing calendar of doctors' time.
What the CRM can do is manage the journey to the booking: capture the enquiry, answer general questions, route the patient to the right clinic and confirm the appointment once the clinical system has it. HubSpot lists an Appointments object among its standard objects (HubSpot Knowledge Base), and its scheduling pages can serve non-clinical bookings such as corporate health enquiries or programme consultations (HubSpot Knowledge Base). For clinical slots, integrate with the system that owns the schedule. See our integration approach.
Where can AI agents help?
The service questions patients ask most are well suited to an agent working from approved content:
- Clinic locations, opening hours, parking and directions.
- Which specialties and services are offered, and at which sites.
- How to book, reschedule or cancel, and what to bring.
- Accepted insurance and corporate panels, from a current list.
- General preparation instructions that the clinical team has written and approved.
HubSpot's Customer Agent can be deployed to WhatsApp, live chat, forms, email and other channels, with working hours and the share of conversations it handles under your control (HubSpot Knowledge Base).
Where must automation stop?
Any message about symptoms, test results, medication, a diagnosis or an emergency must go to a qualified person, or direct the patient to emergency services. So must complaints, and any conversation where the patient is distressed. The agent should never infer a condition or suggest a treatment.
HubSpot's handoff settings let you add custom triggers alongside the defaults, and route conversations live or for later follow-up (HubSpot Knowledge Base). For healthcare we write the trigger list with the clinical team, test it against real historical messages, and review handoff reasons every week. If in doubt, the rule is simple: hand over.
What does the law say about health data?
Health data carries extra protection across the region. Malaysia's Personal Data Protection Act 2010 defines sensitive personal data to include information as to “the physical or mental health or condition of a data subject” (PDPA 2010). The Philippines' Data Privacy Act treats information about an individual's health as sensitive personal information, and its Section 13 prohibits processing it except in listed cases such as consent or medical treatment (National Privacy Commission).
In practice, keep clinical data in clinical systems and keep the CRM to what the service journey needs. Where a provider decides some health related fields must sit in the CRM, HubSpot offers Sensitive Data properties with health and medical categories on Enterprise subscriptions. HubSpot notes that once enabled, the setting cannot be turned off, and that sensitive data is not available in chatbots or personalisation tokens (HubSpot Knowledge Base). HubSpot hosts data in the EU, Canada, Australia and the United States (HubSpot), so document the cross-border transfer. Our data protection answer covers the main laws.
What should a provider measure?
- Response time to new enquiries, by channel and site.
- Enquiry to booking conversion, by source.
- No-show rate, before and after reminders.
- Handoff rate and reasons on agent conversations.
- Patient feedback after visits, and return visits for screenings and programmes.
How should reminders and follow up work?
Reminders are one of the simplest and most valuable automations in healthcare. A message before the visit with the time, the location, what to bring and how to reschedule helps patients keep appointments and frees slots for others. It needs only the booking details, not the reason for the visit.
That last point matters. A reminder that names a specialty or a procedure can reveal health information to anyone who sees the patient's phone. We keep reminders neutral by default: the clinic, the date, the doctor's name only if the patient has agreed, and a link or number to change the booking.
Follow up after the visit should focus on experience, not clinical outcome: how easy it was to book, how long the wait was, whether the patient would return. Feedback goes onto the patient's record, and poor scores create a task for the patient relations team. Screening and wellness programme invitations can follow, but only where the patient has consented to receive them, recorded with the date and channel.
Where to start
Draw the line between service and care with the clinical leadership, in writing. Then bring WhatsApp and web enquiries into one inbox, integrate booking confirmations from the clinical system, and add reminders and feedback. Introduce an agent for general questions last, with the handoff list agreed by clinicians.
