WhatsApp Business API for Saudi clinics, hospitals, and CCHI-licensed networks. Arabic + English appointment confirmations, prescription pickup alerts, PDPL + NHIC-aligned consent flows, post-visit feedback collection.
HyperPay / Moyasar / Tap Payments payment links · mada + cards · STC Pay for popular retail · Tabby / Tamara BNPL — and SMSA Express / Aramex KSA / Naqel tracking pushed live to WhatsApp. Every integration is a real connector, not a Zapier bridge with per-task fees.
Arabic-first customer base (~85%). Our Arabic ↔ English auto-translate and native Arabic RTL inbox are the core offer. Customer writes in English, your agent sees Arabic. Agent replies in Arabic, customer gets their language — both sides see their own.
Coverage cities: Riyadh · Jeddah · Dammam · Khobar · Mecca · Medina · Taif · Tabuk.
SDAIA-aware data handling, SAR-denominated billing available, Arabic-first onboarding, Vision 2030-aligned digital commerce.
Pricing: SAR billing available (≈ AED 499 equivalent) — SDAIA-aware data handling at PRO and Enterprise tiers. Meta conversation fees are passed through at Meta's public rate card — we do not mark them up.
BSP onboarding: Serving KSA from our Dubai office. Direct Meta Business Partner — BSP transfer coordinated with your Saudi BSP if needed.
Go4whatsup does NOT sign HIPAA BAAs and is not a US-regulated PHI processor — US healthcare entities should route PHI through their EMR or an explicitly HIPAA-covered channel, not WhatsApp. Outside the US, compliance is a function of local law (India DPDP, UAE PDPL, GDPR for EU patients) — we publish a DPA, support EU/India/UAE data residency, and recommend keeping clinical detail (diagnosis, medication lists, lab values with interpretation) inside the EMR. WhatsApp also cannot replace ePrescribe, structured clinical notes, or insurance claim flows. Treat it as the patient-facing communication layer, not the clinical system.
We are a Meta Business Partner, not a law firm — our platform supports your compliance posture but cannot substitute for local data-protection counsel on contract language, retention policies, or specific regulator filings.
No — Go4whatsup does not sign HIPAA Business Associate Agreements (BAAs). We are not a covered entity for US-regulated PHI. Hospitals and clinics in the US that handle PHI should route clinical data through their HIPAA-covered EMR and use WhatsApp only for non-PHI communication (generic reminders, logistics, directions). Outside the US, we publish a DPA and support regional compliance (India DPDP, UAE PDPL, GDPR).
Yes in most jurisdictions outside the US, provided the patient has consented and the report is addressed to the registered patient. We recommend encrypting the PDF with a patient-known password (DOB or phone last-4) for defense-in-depth. In the US, route lab reports through a HIPAA-covered portal instead.
Three-layer stack: 24h-before reminder with confirm/reschedule buttons, 2h-before reminder with directions and parking info, and a front-desk escalation if the confirm button isn't tapped by T-4h. Combined, this takes no-shows from 25–35% down to 10–15%.
Yes. A CTWA ad or a "Book now" QR on your reception desk opens a thread; the bot collects specialty, date preference, insurance panel; shows available slots; confirms. Works against Calendly, Cal.com, Practo, or a custom EMR via API.
Set up an auto-reply with a clear message: "For medical emergencies, call [ambulance number]. This channel is monitored during clinic hours only." Plus keyword-trigger escalation so words like "chest pain" or "bleeding" alert a clinical team member regardless of time.
WhatsApp messages are end-to-end encrypted in transit between devices. Meta, however, is the platform operator — it processes metadata. For clinical data, combine WhatsApp with sensible patterns: avoid sending full diagnosis in clear text, use IDs rather than names for sensitive topics, password-protect PDF reports, and keep the EMR as the source of truth.
Yes — either via native HL7 FHIR (for modern EMRs) or REST API. Go4whatsup subscribes to appointment-booked, lab-ready, discharge-complete events from your EMR and fires WhatsApp flows in response. Common EMRs wire up in 1–3 integration calls.
We follow SDAIA guidance on consent, purpose limitation, and data minimisation. We operate data-residency options and help you meet cross-border transfer requirements. Formal SDAIA audit documentation is available to enterprise customers under NDA.
Yes — native Arabic RTL inbox, Arabic UI, Arabic auto-translate in both directions across 100+ languages. Our team includes Arabic speakers for onboarding and enterprise support.
Yes, SAR-denominated invoicing is available at PRO and Enterprise. Default invoice currency is AED (via our Dubai entity), with SAR on request.
7 business days from first call to live WhatsApp number. SAR 499/mo. SAR invoicing. KSA-aware.