OP OperixHealthcare Operations Docs
HR1-style shell Coverage
Unified outbound queue

Communications Hub

Clinic-local reminders, follow-up drafts, billing outreach, templates, and AI-generated copy staged in one outbound hub.

Outbound-firstQueued deliveriesAI handoffAudit trail
Details

Why This Hub Exists

Instead of keeping patient outreach scattered across appointments, billing, and AI buttons, the hub provides one reviewable queue.

  • Manual drafts can be created directly from the hub.
  • Approved or completed AI drafts can be moved into the communications queue.
  • Queued deliveries can be replayed in batches without blocking the clinic shell.
  • Threads remain clinic-local and can be tied back to patient, appointment, invoice, or AI run context.
Communications hub
Outbound drafts, delivery state, and AI handoff now live in one clinic-local queue.
Tenant dashboard
Dashboard cards link directly into the communications backlog when outreach or collections need action.
Details

Communication Templates

Templates are now a first-class clinic-local feature rather than an ad hoc draft shortcut.

  • Staff can list, create, edit, and disable templates from the communications module.
  • Templates support channel-aware variants for email, sms, whatsapp, and call_note.
  • Variable preview and placeholder validation reduce broken buyer-demo content and staff mistakes.
  • Manual outreach and approved AI drafts can prefill from templates without bypassing review or queue state.
Details

Transport Contract And Replay

Communications are now provider-aware without hardcoding every future channel into business flows.

  • Email ships through Laravel mail first, so the app can perform real outbound delivery immediately.
  • sms and whatsapp now use a Twilio-first transport adapter, while call_note remains manual and provider-neutral.
  • Twilio delivery callbacks update communication_deliveries with provider identifiers, provider status, and last-event timestamps without persisting PHI-heavy provider bodies in tenant tables.
  • Replay actions route through the transport contract, persist delivery metadata, and mark failures without blocking the clinic shell.
  • Per-patient, per-channel communication preferences enforce opt-out before queue, send, or replay actions continue.
  • Approved AI drafts can flow into the communications queue, but nothing is auto-sent without staff approval.
  • Hub analytics track queued, sent, delivered, failed, replayed, top-channel, and manual-only state for operator follow-up.
Details

Dashboard And Plan Signals

Communications proof now appears outside the hub as well, so the buyer story is visible before opening the queue.

  • Tenant dashboard cards surface current volume, failed deliveries, top channels, and backlog requiring action.
  • Plan & Limits reuses communications usage and posture so commercial conversations stay grounded in real activity.
  • Source-linked threads can begin from appointments, billing, approved AI drafts, or manual outreach.