indigitall Omni AI 
I am indigitall AI, how can I help you today?
Start chat with AI agent
Speak with AI voice agent
Book a Demo
Your AI assistant can now talk to your campaigns
Push Notification Software: The Ultimate Guide
Push Notification Software: The Ultimate Guide
Omnichannel vs Multichannel: Choose the Ideal Strategy
Read article
What is RCS Marketing?: Everything You Need to Know
What is RCS Marketing?: Everything You Need to Know
Push Notifications vs. SMS: What You Need to Know
Read article
The Future of Healthcare Marketing: An Essential Guide to Omnichannel Excellence
The Future of Healthcare Marketing: An Essential Guide to Omnichannel Excellence
Omnichannel Marketing Automation: What You Need to Know
Omnichannel Marketing Automation: What You Need to Know
Resources
eBooksFree ebooks, whitepapers...
BlogStories, insights and advice
indigitall MCP NewConnect Your Platform Stats to Any AI Agent
IntegrationsHubspot, Salesforce & more
DocumentationComplete guide to indigitall
From appointment reminders to lab results: 20+ HIPAA-compliant patient journeys, delivered in real time across encrypted push, SMS, email, and AI chat. Live sync with your EHR and patient portal. No batch lag.
Powering millions of omnichannel interactions every single month.
The only engagement stack in the US that signs a BAA on every channel, encrypts push end-to-end, and keeps patient data on US soil, with the real-time sync and AI your care teams need.
Notifications are encrypted on the device and unreadable on the lockscreen. PHI stays protected even before the patient unlocks their phone.
Resolves patient questions around the clock, in any language.
Live two-way sync with your EHR and practice-management systems.
Patient data stored and processed entirely within the United States.
A signed BAA on every channel, not just some of them.
An easier way for patients to stay connected with their care. Pick a journey to see how it plays out, step by step, across every channel, with PHI delivered only on PHI-safe channels.
Real impact from production deployments: lower cost, higher engagement, fewer no-shows, and a calmer call center.
Source: indigitall production data, 2026.
Some channels simply can't be made compliant, so we never send protected health information on them. Everything clinical flows over BAA-covered, encrypted, auditable channels.
Not a pilot. These are live deployments moving real patient volume across the indigitall platform.
Unified every patient database into one CDP and migrated transactional comms off SMS to richer, encrypted channels.
Appointment management and FAQs over WhatsApp Flows with two AI bots, serving a 7M+ annual patient base.
Deployed the “Sania” AI bot on WhatsApp for proactive, real-time patient communication, with omnichannel reminders coordinated by the CDP.
Source: indigitall production data: Vithas, QuirónSalud & Sanitas, 2026.
With indigitall as the patient communication platform, the reminder that reaches the lock screen is a generic line, such as "You have an upcoming appointment. Open the app for details," and the specifics appear only after the patient signs in to the authenticated app or portal. HHS treats appointment reminders as part of treatment, so they need no patient authorization, and its guidance on phone messages and email advises limiting what a message says. indigitall's guide to HIPAA-compliant push notifications explains why: a patient's name next to a clinic or an appointment can itself be PHI.
| Moment | What the patient sees | Note |
|---|---|---|
| On the lock screen | A generic line, with no clinician, specialty or reason | Lock-screen text can be read by other people |
| After sign-in | Date, time, location, and the confirm or reschedule actions | Behind a password, PIN or biometrics |
| Results and clinical detail | A notice that something is ready | The content stays in the portal, never in the message |
It is not the right fit if you want clinical detail inside the message itself.
Patient data reaches indigitall through the API or SDK in real time, or by CSV upload, and a journey sends data back to your system with a webhook, for example the appointment date. You choose which fields cross, and the patient identifier is stored as an encrypted external code, so send only what a journey needs. The documentation names no native connector with any EHR or practice-management vendor: each connection is built on the API and the webhook.
| Direction | Route | What it does |
|---|---|---|
| Into indigitall | API or SDK in real time, or CSV | Creates and updates patients, fields and lists |
| Out to your system | Journey webhook with POST, GET or PUT | Sends your system the fields you choose, such as the appointment date |
With indigitall, the controls sit in the data and in the channel: a patient's preferred way of being contacted travels as a field, WhatsApp marketing templates carry an opt-out button, and Meta limits marketing templates per user. The documentation sets no frequency cap of its own, so how many reminders a patient receives is a journey design decision.
| Control | What it does | What to know |
|---|---|---|
| Patient preference | HHS requires a provider to honor reasonable requests about how and where a patient is contacted | Keep the preferred channel in your system and send it as a field |
| Opt-out | Marketing templates carry an opt-out quick reply, and marketing stops once the patient opts out | Agree in setup which system records the opt-out |
| Meta's per-user limit | Marketing templates fail to deliver once a user reaches the limit | It covers marketing templates only |
Yes. With indigitall, the reminder can carry confirm and reschedule actions inside the authenticated app, or run as an automated voice call where the patient confirms or reschedules, and a journey webhook can notify your scheduling system. The visit details appear only after the patient signs in.
According to HHS, yes: appointment reminders count as part of treatment, so no authorization is needed. HHS still advises limiting what a message says, which is why indigitall keeps lock-screen text generic and shows visit details only after sign-in. Promotional messages follow other rules, so confirm with your compliance officer.
Yes. indigitall's security documentation says it can sign BAAs with US healthcare organizations, digital health platforms and insurers, and that it completed a HIPAA audit of its Encrypted Push Notification Service. It also lists SOC 2 Type II and ISO/IEC 27001:2022 reports. Confirm the scope of the BAA in your contract.
Not for marketing. As of October 2026, Meta says it does not deliver marketing templates to US (+1) numbers, and WhatsApp's policy restricts health information where regulations bar it. US patient journeys with indigitall therefore rely on encrypted push, the in-app inbox, SMS, email and the patient portal.
CUSTOMER JOURNEY
Optimize your communications and marketing campaigns from a single platform. AI ensures maximum conversion rates through automation and personalized content on each user's favorite channels.
BLOG
Blog
Article
Article
Article
Article
Article
Error: Contact form not found.
Speak to an Expert
