3.5 Patient Communication Infrastructure¶

Patient Communication Intelligence Framework¶

Vendor-Agnostic, Data-Owned, Future-Ready¶

Prepared by: King Ting – IT & Operations Consultant Date: May 2026

1. Executive Summary¶

This framework addresses a fundamental gap in Supreme Dental's current operations: headquarters has no real-time visibility into patient communications across the 20+ clinic network.

Supreme Dental has now confirmed that its current practice management software is Dentally by Henry Schein One. That is important because Dentally may already hold part of the patient, appointment, and recall workflow. This document therefore should not be read as an argument to replace Dentally. It should be read as an argument to:

use Dentally's native capabilities where they are already fit for purpose
identify the communication and reporting gaps Dentally does not solve for headquarters
build only the additional layer needed to unify cross-clinic visibility, non-Dentally channels, and long-term data control

Calls, missed calls, website enquiries, SMS conversations, and walk-in interactions happen daily at each clinic — but this data remains invisible to management. Consequently, opportunities to improve patient experience, optimize marketing spend, and hold clinics accountable are lost.

Key insight from my experience building similar systems:

"Most companies solve today's problem with today's vendor, only to discover they've locked themselves out of tomorrow's opportunities. We can build something different – something that puts Supreme Dental in control of its own patient communication data, forever."

This framework proposes a vendor-aware, vendor-agnostic middleware approach that:

Uses Dentally where it already supports patient and appointment workflows
Collects communication data from the channels Dentally may not fully expose or unify (phone, website, SMS, walk-ins)
Unifies data across all clinics into a single management dashboard
Enriches data with AI (transcription, categorization, sentiment)
Owns all data – not a vendor, not a telco
Enables best-in-class vendors (AI, marketing, CRM) WITHOUT lock-in

This is not a product purchase. This is a capability build.

Relationship to 3.5.1 and 3.5.2: This document provides the infrastructure and data layer. The companion document 3.5.1 Patient Engagement Tactics provides the practical applications (reminders, follow-up, loyalty programs), while 3.5.2 Dentally Capability Reference defines the current Dentally capability baseline and confirmed gaps.

2. The Problem: Invisible Communications¶

What Headquarters Cannot See Today¶

Across 20+ clinics, a vast amount of patient communication happens every day:

Communication Type	Data Captured?	Visible to HQ?
Incoming calls	❌ No	❌ No
Missed calls	❌ No	❌ No
Call outcomes (booked, question, complaint)	❌ No	❌ No
Website enquiries	⚠️ Some	❌ No
SMS conversations	❌ No	❌ No
Walk-in enquiries	❌ No	❌ No

graph TD
    subgraph Clinics["20+ Clinics (Each is a silo)"]
        A1[Clinic 1<br/>Calls, missed, website]
        A2[Clinic 2<br/>Calls, missed, website]
        A3[Clinic 3<br/>Calls, missed, website]
        A4[... 17 more clinics]
    end

    subgraph HQ["Headquarters"]
        B[? ? ?<br/>No unified view]
    end

    A1 --> B
    A2 --> B
    A3 --> B
    A4 --> B

    style B fill:#ffebee,stroke:#c62828

The Consequences of Invisibility¶

Issue	Impact	Business Cost
Missed calls go undetected	Lost patients, no accountability	Est. 10-20% of new patient enquiries
Peak hours unknown	Cannot optimize staff scheduling	Wasted labour or lost calls
Patient sentiment invisible	Frustrated patients escalate	Reputation damage, reviews
Marketing ROI unknown	Which ads drive calls? No data	Wasted ad spend
Clinic comparison impossible	Cannot identify best/worst performers	Unable to scale best practices
Staff performance invisible	Who handles calls well? Who misses?	No accountability
Patient journey fragmented	Call → Visit → Outcome? No tracking	Missed retention opportunities

The Core Insight¶

"You cannot improve what you cannot measure. You cannot measure what you cannot see. Across 20+ clinics, patient communications are effectively invisible to headquarters."

This is not a criticism of the clinics. It is a structural reporting and integration problem. Dentally may solve part of the operational workflow inside each clinic, but it does not automatically guarantee headquarters-level visibility across every communication channel.

3. The Common Mistake: Single-Vendor Lock-in¶

What Most Companies Do¶

When faced with a problem like "we need better patient communication," most companies:

graph LR
    A[Identify Problem] --> B[Search for Product]
    B --> C[Choose Vendor]
    C --> D[Implement Vendor]
    D --> E[Locked In]
    E --> F[New Problem: Lock-in]

    style E fill:#ffebee,stroke:#c62828

They buy a product that solves part of the problem today, but:

Hidden Cost	Reality
Vendor owns the data	Your patient communication history is their asset
Vendor controls the roadmap	You adapt to them, not vice versa
Switching means losing history	You are trapped
Adding other tools is difficult	Their ecosystem, your limitation
HQ still has no unified view	Only one silo becomes visible

Examples of the Trap¶

"Solution"	What It Does	What It Doesn't Tell You
DrKing.ai	Front-office automation	Owns your lead data. Switch? Lose history.
AiDial	AI receptionist	Owns your call transcripts. Switch? Start over.
Telstra TIPT	Makes calls	API access uncertain. Missed calls? No dashboard.
Google/Meta Ads	Drives traffic	Attribution data locked in. Export is limited.

Each vendor solves one piece. None gives headquarters a unified view. And each creates lock-in.

"Six months after buying a 'solution,' the company discovers they have traded one set of problems for another. They have more tools, but no more transparency. They have spent money, but gained no control."

4. The Solution: Vendor-Agnostic Middleware¶

What We Propose to Build¶

Instead of buying another product first, we start by auditing what Dentally already provides, then build a lightweight, intelligent middleware layer only for the gaps that remain. In practice, that layer would:

Connect to Dentally data where appropriate and permitted
Collect data from every communication channel not already visible in Dentally (phone, website, SMS, walk-ins)
Unify that data into a single, clinic-level and HQ-level view
Present a dashboard to headquarters showing exactly what is happening across all 20+ clinics
Enable the use of best-in-class vendors (AI, marketing, etc.) WITHOUT lock-in

flowchart TD
    subgraph Communication_Channels["Communication Channels (What exists today)"]
        A1[Phone calls<br/>Telstra TIPT]
        A2[Website<br/>Forms, chat]
        A3[SMS<br/>Current provider]
        A4[Walk-ins<br/>Manual log]
    end

    subgraph Middleware["Intelligent Middleware<br/>(What we build once)"]
        B1[Collect all communication]
        B2[Unify by clinic and patient]
        B3[Enrich with AI and attribution]
        B4[Store in your database]
    end

    subgraph Output["What Headquarters Sees"]
        C1[Single dashboard<br/>All clinics]
        C2[Missed calls per clinic]
        C3[Peak hours analysis]
        C4[Patient sentiment]
        C5[Marketing attribution]
        C6[Clinic comparison]
    end

    Communication_Channels --> Middleware --> Output

    style Middleware fill:#e8f5e9,stroke:#2e7d32
    style Output fill:#e3f2fd,stroke:#1565c0

What This Means in Practice¶

Without Middleware	With Middleware
Dentally and other channels remain partially siloed	All clinics and channels visible to HQ
Data owned by vendors	Data owned by Supreme Dental
Cannot compare clinics	Compare performance instantly
Cannot track marketing ROI	See which ads drive calls
Switching vendors means data loss	Swap vendors, keep all data
Partial patient journey visibility	Call → Visit → Outcome tracked across systems
20+ logins for different tools	One dashboard for everything

How It Works: The Adapter Pattern¶

// One middleware to rule all vendors
// Add a new vendor? Just write one adapter (1-2 days)

class AnyVendorAdapter {
  // Normalize any vendor's data to YOUR standard format
  normalizeCall(rawData) {
    return {
      callId: rawData.id || rawData.call_id,
      from: rawData.caller || rawData.from,
      to: rawData.called || rawData.to,
      duration: rawData.duration || 0,
      timestamp: rawData.time || new Date().toISOString(),
      clinicId: this.extractClinicId(rawData),
    };
  }
}

// Supported vendors (add any, remove any, swap any)
const adapters = {
  telstra: new TelstraAdapter(),   // Current provider
  maxo: new MaxoAdapter(),         // Backup option (proven)
  aussie: new AussieAdapter(),     // Future option
  drking: new DrKingAdapter(),     // Optional AI tool
  aidial: new AiDialAdapter(),     // Optional AI tool
  // Add any vendor in 1-2 days
};

Key point: Supreme Dental can continue using Dentally, plus DrKing.ai, AiDial, or any other vendor where useful. The middleware makes them work together, and reduces the risk that any one vendor becomes the only place where insight lives.

5. Why We Can Build This Now¶

What Has Changed in Recent Years¶

The ability to build this kind of middleware is only now possible because of three simultaneous shifts:

Shift	What It Enables	Cost
Serverless Computing (Cloudflare Workers)	Run code without servers, scales automatically	Free tier: 100k requests/day
AI APIs (Cloudflare AI, DeepSeek, OpenAI)	Add intelligence without building models	Free tier available
DevOps Tools (GitHub Actions, Supabase)	Automate deployment and data storage	Free tier available

What this means for Supreme Dental:

No large infrastructure investment
No ongoing enterprise software licenses
Start small, scale as needed
Pay only for value-added services (not for lock-in)

My Relevant Experience¶

I have built this exact type of system before for my own company (ozhut.com.au) using:

Maxo Telecom – Configured lines, softphones, Yealink handsets
Call flows – Office hours, IVR, voice response
Webhooks – Captured every incoming call
Odoo integration – Connected VoIP to helpdesk system

This experience means:

I understand the technical requirements deeply
I have proven code and patterns to reuse
I know what can go wrong and how to prevent it
I have existing relationships with vendors

"Unlike consultants who would wait for vendors to provide APIs, I have already built a production VoIP call handler. I know exactly how to make this work – with Telstra, Maxo, or any provider."

6. The Management Dashboard¶

What Headquarters Will See¶

The practical goal is not to duplicate the full practice management function already handled by Dentally. The goal is to give headquarters a management layer that Dentally alone may not provide today: cross-clinic communication visibility, missed opportunity tracking, channel attribution, and comparable performance metrics.

graph TD
    subgraph Dashboard["Central Dashboard (One Login)"]
        D1[Total calls today: 847<br/>across 22 clinics]
        D2[Missed calls: 43<br/>↓12% from last week]
        D3[Top clinic: Box Hill<br/>127 calls, 3 missed]
        D4[Bottom clinic: Glen Waverley<br/>89 calls, 12 missed ⚠️]
        D5[Sentiment: 82% positive<br/>4% angry flagged]
        D6[Marketing ROI: Facebook $32/lead<br/>Google $28/lead]
    end

    subgraph DrillDown["Drill Down to Any Clinic"]
        E1[Clinic 470 Blackburn Rd]
        E2[Today's calls: 63]
        E3[Missed: 4]
        E4[Peak: 2-4pm]
        E5[Staff: Michael 23 calls, Sarah 40 calls]
        E6[Recent angry caller: +61412345678]
    end

    Dashboard --> DrillDown

    style Dashboard fill:#e8f5e9,stroke:#2e7d32

Reports Management Receives¶

Report	What It Answers	Frequency
Daily Call Summary	How many calls, missed, handled per clinic	Daily
Weekly Sentiment Trend	Are patients getting more frustrated?	Weekly
Marketing Attribution	Which ads drove how many calls?	Weekly
Staff Performance	Who handles most calls? Who misses most?	Weekly
Clinic Comparison	Which clinics need help? Which excel?	Weekly
Patient Journey	Call → Appointment → Outcome?	Monthly

7. The Long-Term Strategic Value¶

What Headquarters Gains Over Time¶

Year	Value Delivered
Year 1	Complete visibility into all patient communications across all clinics. Know exactly what is being missed, where, and when.
Year 2	Historical data on call volume, sentiment, and outcomes. Compare clinics. Identify best practices.
Year 3	Freedom to add or replace AI vendors, VoIP providers, marketing tools – without losing a single record of patient interaction.
Year 5	A proprietary asset: five years of patient communication intelligence. Data that belongs to Supreme Dental, not any vendor.

The Strategic Asset¶

"Most companies have no idea what five years of patient communication data is worth – because no vendor has ever offered it to them. It belongs to the vendors, not the company."

With this middleware, Supreme Dental builds a proprietary asset:

Asset	Description
Every patient call	Transcribed, categorized, searchable
Every missed call	Tracked, recovered, trended
Every marketing source	Attributed to calls and visits
Every clinic	Compared on key metrics
Every sentiment trend	Charted over time
Every staff member	Performance measured

No vendor can offer this because no vendor wants you to own your data. We are building it so you do.

8. Comparison: Middleware-First vs. Vendor-First¶

Factor	Dentally-Only / Vendor-Only	Dentally + Middleware (Proposed)
Time to first value	Days if native features are already enabled	Days for Dentally quick wins, weeks for HQ layer
Upfront cost	Lower	Higher (build only the missing layer)
Long-term flexibility	Medium-Low	Very high
Data ownership	Primarily vendor-controlled system of record	Supreme Dental gains an owned reporting and insight layer
Switching cost	High	Lower
Single dashboard for all vendors	Uncertain / limited	Yes
Marketing attribution	Limited	Yes
Clinic comparison	Uncertain / configuration-dependent	Yes
Vendor negotiation power	Weaker	Stronger
Clinic sale value	Lower	Higher (owns data asset)

The Deciding Question¶

"Do you want to buy a product that solves today's problem but locks you in? Or do you want to build a platform that gives you control forever?"

9. Relationship to Patient Engagement Tactics (3.5.1)¶

This framework provides the foundation for patient engagement tactics:

Engagement Tactic	How Middleware Enables It
Appointment reminders	Middleware complements Dentally where reminders need cross-channel orchestration or HQ reporting
Post-visit follow-up	Middleware tracks visit history and communication outcomes beyond the PMS workflow
Loyalty programs	Middleware tracks patient activity across clinics
Reputation management	Middleware captures sentiment and triggers review requests
Personalised campaigns	Middleware has unified patient communication history

Crucially: Engagement tactics can be delivered through Dentally first, then extended through middleware (data-owned) or standalone tools where needed. The choice should be driven by capability gaps, not by assumption.

For detailed tactical implementation, see: 3.5.1 Patient Engagement Tactics

10. What We Are Not Doing¶

To be clear about what this proposal is and is not:

We Are NOT...	We ARE...
Selling you DrKing.ai	Proposing a vendor-agnostic platform
Locking you into any vendor	Building your data ownership
Replacing your phone system	Making your phone system transparent
Selling you a product	Building you a capability
Solving for today only	Building for long-term flexibility
Working alone	Orchestrating best-of-breed tools

11. Next Steps (Discussion)¶

This framework is intended to align on problem and principle before discussing specifics.

For discussion with the General Manager:

Alignment Questions¶

Do we agree that headquarters currently lacks visibility into patient communications across all clinics?
Do we agree that buying a single-vendor solution risks creating lock-in without solving the visibility problem?
Do we agree that a vendor-agnostic middleware layer – giving Supreme Dental control and transparency – is the right long-term approach?
Do we agree to proceed to a more detailed discussion of how this would work for Supreme Dental?

If Agreement Is Reached¶

The next phase would address:

Which Dentally modules, workflows, and reports are currently enabled
Which communication channels to connect first (phone, website, SMS)
Which clinics to pilot with (1-2 clinics)
What the management dashboard should show
Timeline and approach (not yet cost)
How to integrate Dentally and existing vendors (Telstra TIPT)

If Preference Is to Start With Existing Systems First¶

If Supreme Dental prefers to start with Dentally's current capabilities before committing to the middleware approach, that is sensible. However, I would recommend:

Audit Dentally first to identify what is already available, what is enabled, and what is missing
Pilot with explicit success criteria so any gap between clinic operations and HQ reporting becomes visible
Document all integration points to ensure future middleware or vendor migration remains possible
Build minimal middleware only for the gaps that Dentally and current vendors do not solve independently

If Supreme Dental instead prefers to pilot a single external vendor solution (e.g., DrKing.ai), that is also possible. In that case, I would still recommend:

Pilot with explicit understanding that data export and vendor switching will be tested
Document all integration points to ensure future migration is possible
Build minimal middleware alongside the pilot to capture data independently

This preserves the option to adopt the full middleware framework later without losing pilot data.

12. Summary: The Core Message¶

"Most companies solve today's problem with today's vendor. They gain a tool but lose control.

I am proposing something different: use Dentally where it already serves the clinics well, then add a lightweight, intelligent middleware layer that gives Supreme Dental complete visibility into patient communications across all 20+ clinics – and the freedom to use any vendor, anytime, without losing data or flexibility.

No single vendor can offer this, because no vendor wants you to own your data. But with modern DevOps, serverless computing, and AI – and my experience building similar systems – we can build it for you.

The result is not just a solution for today. It is a proprietary asset for the next five years: a complete history of how patients interact with Supreme Dental.

Let's discuss whether this aligns with your vision for the network."

Appendix A: Technical Architecture Overview¶

flowchart TD
    subgraph Data_Sources["Data Sources (Any Vendor)"]
        A1[VoIP: Telstra/Maxo/ABB]
        A2[Website: Forms/Chat/GA]
        A3[SMS: Twilio/MessageMedia]
        A4[AI: DrKing.ai/AiDial]
    end

    subgraph Middleware["Your Middleware (Cloudflare Workers)"]
        B1[Unified Adapter Layer]
        B2[Event Bus - Real-time]
        B3[Enrichment: AI/Source/Clinic]
        B4[Storage: Supabase + R2]
    end

    subgraph Output["Value Layer"]
        C1[Management Dashboard]
        C2[Marketing ROI Reports]
        C3[Patient Journey Analytics]
        C4[Missed Call Alerts]
        C5[Clinic Comparison]
    end

    Data_Sources --> Middleware --> Output

    style Middleware fill:#e8f5e9,stroke:#2e7d32

Key Technical Decisions¶

Component	Choice	Why
Compute	Cloudflare Workers	Free tier, edge deployment, JavaScript
Database	Supabase	Free tier, PostgreSQL, real-time
Storage	Cloudflare R2	Free tier, S3-compatible
AI	Cloudflare AI → DeepSeek	Start free, pay only if needed
CI/CD	GitHub Actions	Free tier, integrated
Dashboard	Retool or Supabase	Build quickly, iterate

Appendix B: Comparison of Patient Communication Vendors¶

Vendor	Core Strength	Lock-in Risk	Data Ownership	Best For
DrKing.ai	Front-office automation, lead capture	High	Vendor	Marketing-focused clinics
AiDial	AI receptionist, appointment booking	Medium-High	Vendor	Call-heavy clinics
Voxworks	Australian AI voice, sovereignty	Medium	Vendor	Compliance-focused
Twilio	Programmable communications	Low (API-based)	You (if you build)	Custom development
Cloudflare AI	Edge inference, free tier	None	You	DIY AI categorization

Note: Any of these can be used WITH the middleware framework. The choice is not "which vendor" but "do we own our data?"

References¶

The following vendor reference documents inform this architecture. They compile publicly available information distilled for our middleware integration project.

Document	Purpose	Status
Dentally Platform Reference	Dentally capabilities, API endpoints, integration points	Living document — updated as vendor info confirmed
TIPT Platform Reference	Telstra TIPT capabilities, API, call data integration	Living document — updated as vendor info confirmed

These references are maintained alongside the project issues: - Issue #1 — Dentally Discovery - Issue #2 — TIPT Phone System Discovery

Document Version: 1.3 (Patient Communication Intelligence Framework) Related Document: 3.5.1 Patient Engagement Tactics Prepared for: Supreme Dental Network Prepared by: King Ting – IT & Operations Consultant

This document is confidential and prepared for internal discussion at Supreme Dental Network.