CadenceConductor
The next-touch planner for every doctor
A per-doctor cadence engine that decides, turn by turn, what the right next touch is — voice call, WA reminder, quiet gap — from pickup history, prior responses and consent state.
- 1 Private state machine per doctor
- Every Touch is explainable
- 72 h Default silence after a decline
CadenceConductor is the reason MedReach does not feel like a dialer. A call centre thinks in "dial ten times until the contact picks up." CadenceConductor thinks in "what is the respectful, effective next touch for this individual doctor, given everything the system already knows about them?"
Every doctor on a campaign sits in a private state machine. The machine reads signals from the last touch (picked up but busy, declined, agreed, registered, attended), from PickupWindow (best-pickup hours for this doctor), and from ConsentLedger (any opt-outs, any channel ban, any cool-down period), and picks the next move: another voice call at the right hour, a WhatsApp reminder, or a 72-hour silence.
Silence is a first-class action. Most outreach platforms only implement "retry" — CadenceConductor explicitly models "do nothing" as the correct answer when a doctor has asked for space, or when the signal from the last touch is that another touch will hurt more than it helps. This discipline is why allow-lists stay healthy for years, campaign after campaign.
Operators see the conductor's decisions on a per-doctor timeline. Every scheduled touch, every silent window, and every "why this touch, why now" explanation is available. Campaign managers can still override — schedule a one-off wave, exclude a segment — but the default behaviour is respectful and evidence-driven.
Everything CadenceConductor handles for you
-
Per-doctor state machine
Each doctor has a private cadence state — no shared global retry schedule.
-
Silence as first-class
The planner explicitly chooses to do nothing when that is the right answer.
-
Signal-driven transitions
Transitions read PickupWindow, last-touch outcome and ConsentLedger before every decision.
-
Explainable decisions
Every scheduled touch has a reason attached — campaign managers always know why.
-
Manual override
One-off waves and segment exclusions coexist with the default respectful behaviour.
The brain of every campaign
CadenceConductor sits at the centre of the outbound stack — it reads doctor state, writes touch schedules, and hands the actual send off to the channel services.
- PickupWindow supplies the per-doctor best-pickup hours that drive call scheduling.
- ConsentLedger supplies the real-time consent state before any touch is scheduled.
- VoiceDialer receives scheduled voice calls from the planner.
- CareCaster receives scheduled WhatsApp and SMS touches from the planner.
- AIFlow hosts the state-machine runtime the conductor runs on.
Wire CadenceConductor into your product today
Book a consultation with our founders and we'll walk you through the whole microservice stack — not just this one — live on your domain.