Use cases
DTx, payers, and disease-management platforms, with the stream shape each one runs.
Display mode never touches PHI — no BAA required. Start in 5 minutes.
Assemble your stack
Four buyer profiles, four pre-cut assemblies. Click a profile to see which template(s), which mode, which tier — and which audience pools the buyer's roster typically populates. The detailed recipe sections below carry the rationale.
At-a-glance
Skim the matrix to see which assembly choices differ — then drop into the recipe sections below for the rationale.
DTx vendor
Clinically-validated
Payer
Population-scale
Platform
Custom + white-label
Pharma
Patient-support
§1 · Recipe 1
A digital therapeutic company shipping a clinically-validated program. Their product is the patient relationship; Signal is the message engine inside it. They render every cue in their own app, on their own brand, with their own clinician escalation layer on top.
The shape
Picks 2–3 Live templates that match their FDA indication area (Relapse Prevention + Quit Smoking for an SUD-focused DTx; Diabetes Pharma Init for a glycemic-control DTx; Weight GLP-1 Init for an obesity-care DTx). Display mode end-to-end — patients see the cue inside the DTx app, never an Uphealth-branded send. PMPM tier so cue calls don't meter on volume.
Why the choice
The DTx vendor's regulatory + clinical workflows already exist; they don't want Uphealth in the loop between patient and clinician. Display mode keeps Signal as a content engine + receptivity scorer without inserting a second sender. The receptivity score feeds their existing in-app reminder logic.
What they don't use
No Deliver mode (their app handles delivery). No Reach (their channel mix is locked at the regulatory layer). Signal compose-with-Reach unlocks for the next recipe — DTx vendors typically don't compose this way.
Where DTx cues land
An adult at home, in their daily routine, inside the DTx vendor's app.
§2 · Recipe 2
A health insurance plan or employer-payer running population-scale outreach. Their problem is "we have 50,000 members in our diabetes risk cohort and our member-app open rates are 2%." They want to compose Signal's content + receptivity with Reach's delivery decisions to actually land messages.
The shape
Picks General Wellness + Hypertension + Diabetes Pharma Init templates — covers the bulk of their adult member population. Deliver mode so Uphealth + Reach handle email + push delivery directly. PMPM tier because per-cue billing wouldn't scale at 50,000+ active patients. BAA executed before live keys activate.
Why the choice
The payer's existing member-app channel has 2% open rates; their CRM-managed email blasts have 4%. Signal Deliver mode + Reach's tier-based routing typically outperforms both because anchor-and-jitter timing + receptivity scoring shift sends to receptive moments. The payer never builds delivery infrastructure.
Audience-safety load
Population-scale outreach hits all 4 audience-tag pools (Conditions / Topics / Family / Population). The payer's clinical-record ingestion populates Conditions; member surveys populate Topics; family-history fields populate Family; member demographics populate Population. Every cue runs the filter.
Where payer cues land
A 50,000-member roster spans generations, conditions, and channels.
§3 · Recipe 3
A care-navigation platform, EHR vendor, or clinically-integrated network — embedding Signal into a product their own customers use. They need custom templates beyond the standard catalog, white-label delivery, and the ability to author + version their own templates inside Signal's authoring partnership.
The shape
Starts with Postpartum + Cancer Survivorship templates from the catalog (which carry across many platform-customer contexts), then partners with Uphealth's authoring team to spec 2–3 custom templates for their platform-specific workflows. Display mode rendered inside their platform UI. Enterprise tier unlocks white-label + custom audit retention + custom BAA terms.
Why the choice
Their platform-customers (clinicians, hospitals, care teams) shouldn't know they're using Uphealth — that's the white-label promise. Custom templates let them carry their platform's domain expertise into Signal's message catalog without inheriting the stock catalog's federal-source attribution requirements verbatim (custom templates can carry their own attribution model under contract).
Custom-template authoring
Enterprise-tier authoring is a working partnership: their clinical experts + Uphealth's content team co-author the templates. Audience-safety filter + tone audits + federal-source mapping all happen inside Signal's authoring tooling. Templates ship to the platform's customers only — they don't appear in the public catalog.
Where platform cues land
Inside the platform-customer's UI — clinician, hospital, or care team — never Uphealth-branded.
§4 · Recipe 4
A pharmaceutical manufacturer or life-sciences company funding a patient-support program for a therapy they make. Their problem is first-fill abandonment and early discontinuation — a patient starts a GLP-1, a statin, or a new diabetes medication and falls off in the first 30 days. They fund a federally-sourced onboarding stream that runs inside their hub or patient-support portal, never as a branded promotional channel.
The shape
Picks the suite matched to the therapy area — Diabetes Pharma Init, Weight GLP-1 Init, and Heart Pharma Init — a coherent set of 30-day initiation arcs. Display mode rendered inside the program's patient-support portal or hub-vendor app. Per-Episode tier, because a 30-day initiation episode per enrolled patient maps cleanly to how manufacturers fund support programs; PMPM or Enterprise when a BAA or white-label is required.
Why the choice
Every cue is NIDDK, NHLBI, or ADA guidance — no manufacturer promotional claims, no efficacy statements, no fair-balance exposure. The manufacturer funds adherence without owning the medical content. The b+ pattern keeps medication messaging gated behind the patient's medication opt-in, so the content reaches only patients who have opted into medication-context messaging.
What they don't use
No branded drug messaging, no efficacy or outcomes claims, no crisis pathways. The federal-source attribution is non-negotiable — it is the feature, not a limitation. Off-label and promotional content never enter the stream.
Where pharma cues land
A patient in the first 30 days of a new therapy, inside the manufacturer's support program.
The three profiles above describe how a buyer in that category would assemble Signal. There are no named customers, no quoted usage metrics, no logos. Signal is new; the first production customers are in pilot at the time of this writing. When customers go live, this page will iterate toward de-identified pilot summaries (with explicit consent) — not before.
If your shape doesn't match one of these three, that's expected — most buyers compose differently. The 4-tier × Display/Deliver × 11-template × 4-audience-pool combinatorics cover most assembly patterns. Talk to sales to scope your specific shape; the partial overlap with these recipes usually points you at the right starting template.
Evaluating Signal? Let Claude or ChatGPT do the vendor legwork — paste one prompt.
See how →