Core outcomes
3
Commercial and operational outcomes already mapped to the bundle.
Workflow templates
4
Workflow blueprints that operationalize the bundle once dependencies are ready.
Connector lanes
9
Provider and connector categories that need to be available for the bundle.
Tracked KPIs
4
Operational or commercial scorecards the bundle is already designed to surface.
Operating model
The service families and workflows inside this bundle
Vertical packages turn the public service families into one more opinionated rollout path, with onboarding, dashboards, and KPI expectations already aligned.
Flagship service
AI Operations & Automation
Replace manual friction with a managed operations program that hardens intake, automation coverage, and change visibility.
Service family
AI Customer Support OS
Support teams get a calmer queue, better routing, and clearer context across channels.
Service family
AI Communications OS
Coordinate customer, prospect, and operator communications across every important channel.
Service family
AI Compliance OS
Make operational AI safer with explicit review steps, policy visibility, and audit-ready workflows.
Service family
AI Knowledge OS
Keep every AI surface grounded in approved sources instead of stale or improvised answers.
Service family
Voice & Missed-Call Recovery
A voice coverage layer for missed calls, overflow, and after-hours demand that still needs a clean next step.
Service-to-vertical map
How this vertical is assembled from shared modules
Healthcare admin uses the shared support, communications, knowledge, compliance, and operations modules, but it stays explicit about the checklist-only connectors that still need governed setup.
Service roles
AI Operations & Automation
Coordinates escalations, queue ownership, and exception handling across patient-admin workflows.
AI Customer Support OS
Handles inbound questions and queue routing with grounded support context instead of ad hoc inbox rules.
AI Communications OS
Supports reminders, callbacks, and channel continuity across patient-admin touchpoints.
AI Compliance OS
Keeps review-required actions and retention-sensitive workflows visible before anything claims to be fully automated.
AI Knowledge OS
Holds approved scripts, SOPs, and policy references so support and reminder flows stay grounded.
Voice & Missed-Call Recovery
Protects after-hours or overflow patient-admin demand without creating a separate healthcare-only voice stack.
Assembly sequence
Triage patient-admin demand safely
Support and operations modules share triage and escalation flows while keeping queue ownership explicit.
Services
Support OS · AI Operations
Workflows
Support Triage · Compliance Review
Agent packs
Support Desk Pack · Compliance Ops Pack
Ground reminders and answers in approved knowledge
Knowledge import and refresh stay reusable platform modules rather than bespoke healthcare logic.
Services
Knowledge OS · Communications OS
Workflows
Knowledge Refresh · Appointment Setter
Agent packs
Knowledge Curation Pack
Escalate overflow and review-sensitive work
Voice recovery and compliance review keep exceptions visible when the shared automation lane should stop and hand off.
Services
Voice Recovery · Compliance OS
Workflows
Compliance Review
Agent packs
Compliance Ops Pack
Blueprint map
What the bundle maps to inside NEXA OS
The same package record now maps to workflow templates, agent packs, onboarding modules, dashboard modules, and reporting without splitting public and operational definitions.
Workflows
Automation templates
Support Triage
Classifies support requests and routes them into the right escalation path.
Appointment Setter
Books meetings or site visits with reminders and handoff context.
Knowledge Refresh
Keeps source material current so AI assistants stay grounded.
Compliance Review
Injects policy-aware approvals and retention checks into risky workflows.
Agent packs
AI workforce coverage
Support Desk Pack
Support agents for triage, response drafting, and escalation prep.
Knowledge Curation Pack
Agents that organize, refresh, and validate grounded source material.
Compliance Ops Pack
Policy-aware agents that stage reviews and retention-sensitive actions.
Onboarding
Launch checklist
Workspace Baseline
Define owners, source systems, and the first service boundaries.
Connector Readiness
Confirm every required connector before workflows are activated.
Knowledge Import
Load and validate source material for grounded automation.
Compliance Guardrails
Document retention, suppression, and audit expectations before go-live.
Dashboard and reporting
Where teams track the rollout
Conversation Coverage
Channel visibility for chat, messaging, and support interactions.
Knowledge Readiness
Source health, refresh cadence, and grounding posture.
Compliance Desk
Approval posture, retention actions, and compliance watchpoints.
Analytics Scorecards
Service and package KPI scorecards tied to real workflows.
Response SLA
Measures response-speed posture across support and revenue lanes.
Support Quality
Highlights queue health, answer quality, and escalation pressure.
Compliance Audit
Surfaces approval posture, export readiness, and retention-sensitive actions.
Launch notes
Vertical onboarding notes and KPI mapping
These notes annotate the shared onboarding and reporting modules for this vertical without introducing a separate implementation path.
Onboarding notes
Separate admin queues from clinical work
Define the non-clinical intake, reminder, and support scopes up front so the package stays honest about what it automates.
Stage only the connectors the platform already knows
Twilio, n8n, OpenAI, and CRM can use the shared connection seams, while ticketing, knowledge-base, document-store, and agent-orchestration stay checklist-owned.
Load approved scripts and SOPs first
Only approved patient-admin guidance should enter retrieval before support or reminder drafting goes live.
Document retention and review boundaries
Confirm retention windows, escalation approvals, and export posture before the compliance layer is considered launch-ready.
Reporting and KPI map
Response SLA
Measures whether reminders, callbacks, and support queues are meeting the promised response window.
Support Quality
Tracks triage quality and whether escalations are being completed with the right context.
Compliance Audit
Keeps the package honest about approvals, retention posture, and sensitive workflow oversight.
Readiness and compliance
Dependencies that keep the bundle trustworthy
These bundles deliberately call out operational dependencies and compliance considerations so public storytelling does not pretend the rollout is push-button.
Deployment dependencies
Escalation matrix signed off
Approved knowledge sources loaded
Retention windows reviewed with operators
Provider mapping
Apideck CRM
This bundle already maps to the shared workspace connection seam for Apideck CRM.
Twilio
This bundle already maps to the shared workspace connection seam for Twilio.
n8n
This bundle already maps to the shared workspace connection seam for n8n.
OpenAI
This bundle already maps to the shared workspace connection seam for OpenAI.
Compliance watchpoints
Minimize PHI-adjacent data captured in messaging and support notes
Require documented approval for retention and export workflows
Connector requirements
CRM sync
Workspace connectionCRM connectivity remains the shared patient-admin record seam for intake, follow-up, and escalation context.
Messaging transport
Workspace connectionTwilio-backed messaging supports reminders and callback coverage inside the shared communications layer.
Voice transport
Workspace connectionVoice transport is still required for call recovery and admin queue continuity.
Workflow engine
Workspace connectionn8n remains the shared workflow engine for triage, reminder, knowledge-refresh, and compliance review lanes.
OpenAI runtime
Workspace connectionOpenAI runtime powers grounded drafting and knowledge-backed support where live retrieval is enabled safely.
Ticketing
Onboarding checklistTicketing still enters as a governed checklist item until a first-class provider-connection family exists.
Knowledge base
Onboarding checklistKnowledge-base readiness is still staged through onboarding and review-owned imports, not a dedicated provider row.
Document store
Onboarding checklistRetention-sensitive documents stay in the checklist-only posture so operators can approve scope before sync.
Agent orchestration
Onboarding checklistAgent launch governance is still modeled as rollout truth and operator checks rather than a standalone provider connection.
Expansion path
The next lanes this bundle usually unlocks
Vertical packages can start with a narrow industry problem, then expand into adjacent service families once the core lane is stable.
Trust posture
Why the bundle page does not over-claim delivery maturity
The public bundle story is intentionally tied back to the same shared records that power dashboards, forms, onboarding, and later activation work.
Shared catalog, not page-local copy
Services, bundles, pricing posture, workflow links, and form deep links resolve from the same typed service catalog.
Lead capture stays durable-first
Contact and audit requests still flow through one shared capture service with hashing, rate limits, and downstream dispatch tracking.
Delivery state stays honest
Public pages describe scope and rollout inputs, while real workspace activation and readiness remain in dashboard and admin service ledgers.