Respond consistently
Bring WhatsApp and website conversations into one governed Message Centre with context, routing, cases, and collaboration.
From inbound WhatsApp or web chat into Message Centre—AI Concierge drafts a response from approved hospital knowledge so staff can review, refine, or send with confidence.
Fire a WhatsApp campaign to thousands of patients, watch every reply land on one live screen, and let AI resolve 9 in 10 — turning conversations into booked appointments.
Live simulation · All patients, numbers & conversations are fictional demonstration data · Qmed Engage v0.4
Built for mid-to-large hospitals that need service quality and growth in one engagement layer.
Qmed Engage connects the complete non-clinical relationship—from the first question to human service, lead follow-up, campaign engagement, and future hospital-system actions.
Bring WhatsApp and website conversations into one governed Message Centre with context, routing, cases, and collaboration.
Answer administrative questions from hospital-approved sources, in multiple languages, with source traceability and safe escalation.
Capture service enquiries as owned leads, assign follow-up tasks, and connect campaigns to tracked or reconciled outcomes.
Apply consent, suppression, quiet hours, frequency controls, safety boundaries, knowledge approval, and auditability.
Each module can be introduced in stages, while sharing the same patient context, consent rules, knowledge, and event history.
WhatsApp and web chat, persistent conversations, cases, routing, internal notes, escalations, and AI reply assistance.
Qmed Engage ServiceMultilingual hospital information, safe service navigation, lead capture, approved next actions, and full-context human handoff.
Qmed Engage ServiceNon-clinical identity, consent, conversations, leads, campaigns, ownership, and engagement history.
Qmed Engage ServiceCapture, qualification, ownership, tasks, callbacks, service interest, attribution evidence, and manually reconciled outcomes.
Qmed Engage GrowthPermitted segments, approvals, personalisation, A/B testing, budgets, volume controls, emergency stop, and outcome reporting.
Qmed Engage GrowthHealth-screening and wellness playbooks now, with appointment, no-show, post-visit, and visual workflow automation later.
Qmed Engage GrowthDraft, review, approve, publish, expire, trace sources, detect gaps, and regression-test AI answers before release.
Qmed Engage ServiceCustomer service, AI quality, campaign, lead, safety, executive outcome, and technical-health visibility.
Qmed Engage ServiceVendor-neutral appointment, identity, CRM, HIS, billing, data, and optional Qmed Journey connectors as the hospital expands.
Qmed Engage AutomationTenant administration, consent, policy controls, AI boundaries, auditability, and an enterprise security roadmap.
Qmed Engage ServiceThe first release works without deep hospital integration. Each stage is designed to accept live appointment, queue, billing, and Qmed Journey events later.
A patient asks about a doctor, service, package, preparation, facility, or process.
AI Concierge answers from approved knowledge or hands over with full context.
The system captures a lead, shares an approved link, or creates a callback task.
Consent-aware campaigns and fixed playbooks continue the patient relationship.
Track replies, clicks, forms, lead stages, callbacks, and reconciled hospital outcomes.
AI Concierge is positioned inside Qmed Engage—not as a clinical diagnosis tool. It helps with hospital information and safe service navigation, then escalates clinical, sensitive, uncertain, or emergency situations.
The first commercial proposal does not depend on an existing Qmed deployment. Future connectors can expand from engagement into the physical and operational patient journey.
Launch with hospital-owned knowledge, WhatsApp Business, website chat, staff workflows, tracked links, web forms, callbacks, and authorised outcome reconciliation.
Add vendor-neutral hospital connectors and optional Qmed integrations when the hospital is ready for live actions, event-driven automation, and deeper attribution.
Three tiers create a clear entry point for different hospital priorities while keeping one product identity and upgrade path.
For customer service, patient experience, and contact-centre teams that need one governed digital workspace.
For private hospitals that want customer service, lead conversion, consent-aware campaigns, and measurable commercial outcomes.
For hospital groups ready to connect engagement with appointment, CRM, HIS, billing, analytics, and Qmed Journey workflows.
Placeholder subscription pricing is shown per hospital or agreed facility bundle. Channel usage, AI usage, implementation, training, knowledge preparation, data migration, custom workflows, integrations, private connectivity, enterprise deployment, taxes, and third-party charges may be priced separately or governed by fair-use limits.
Choose Engage Service for governed digital service and AI assistance. Choose Engage Growth when lead conversion, campaigns and follow-up playbooks are also priorities. Engage Automation is for hospitals ready to scope connected operational journeys.
No. Patient Engagement Centre is positioned as a standalone product for hospitals that are not current Qmed customers. Qmed Appointment, Queue, Kiosk, Portal, Navigation, Payment, and other modules become optional future connectors.
No. Engage Service and Engage Growth can begin with hospital-approved knowledge, website chat, WhatsApp, staff workflows, tracked links and callback handling. Hospital-system integrations are introduced only when they are ready and approved.
The displayed amount is the platform subscription per hospital per month. Implementation, onboarding, data preparation, custom integrations, premium support, taxes and third-party usage may be scoped separately.
The first release is administrative and service-navigation focused. It does not independently diagnose, recommend treatment, prescribe, provide dosage guidance, or interpret laboratory or medical-image results. Clinical or emergency intent follows hospital-approved escalation paths.
Yes. The tiers are one product with a clear Service → Growth → Automation path. Upgrading does not require moving patient context, consent history, knowledge or engagement records into a different product.
Purpose- and channel-specific consent, opt-out, suppression, quiet hours, frequency caps, complaint and safety suppression, approval workflows, high-risk exclusions, and audit records are evaluated before outbound promotional communication.
Channel, cloud, AI-model and other third-party usage charges depend on volume and provider terms. They are reviewed during commercial scoping so the hospital can see the platform subscription and variable costs separately.
The standalone plans can share an approved hospital destination or create a human request. Direct booking, rescheduling or cancellation requires a separately delivered and validated scheduler connector.
Tenant isolation, role-based access, consent and suppression controls, audit evidence, approved knowledge and human takeover are built into the platform. Deployment-specific security, retention and data-residency requirements are confirmed with each hospital.
We start with service and safety discovery, approved content, channel setup, staff roles, routing and a fictional-data sandbox. The hospital validates workflows before any production channel or live patient traffic is enabled.
The Phase-1 experience supports English, Bahasa Malaysia and Simplified Chinese for approved content and assisted service workflows, with coverage governed through Knowledge Studio.
Start with a standalone Qmed Engage deployment, then connect the hospital journey as priorities and integrations mature.