Skip to content

Targeted Outreach Campaign

Proactive outreach process — instantiates Endpoint Fan-Out Fulfillment

Goes out and finds the specific endpoints that are stuck — missing information, blocked by an access barrier — and proactively removes the blocker so they can complete, instead of waiting for them to come to the system.

Some endpoints will never complete on their own: a renewal letter went to a stale address, a required document was never uploaded, a language barrier stopped someone at step two. A standard fan-out serves whoever shows up and reports the rest as "notified." Targeted Outreach Campaign inverts that flow — it identifies the specific non-completers, works out why each is stuck, and pushes the missing piece to them. Its defining move is being proactive and endpoint-specific: not a broadcast reminder, but a campaign that goes to the named endpoints below the line and removes each one's actual blocker. It is the instrument that lifts the worst-served segments up to a guaranteed floor of coverage, closing the residual gap that upstream "success" hides.

Example

A regional health-coverage program looks healthy on paper — renewals "processed," notices "sent" — yet a large number of families lapse each cycle. The dashboards stop at dispatch, so the real cause is invisible: a renewal went to an old address, a pay stub was never uploaded, a form arrived only in English. A Targeted Outreach Campaign works the non-completers directly. It pulls the endpoints sitting below the coverage floor (families whose renewal is incomplete), segments them by blocker — bad address, missing document, language — and reaches each through the channel most likely to land: a phone call, a text with a one-tap upload link, a trusted community org for the hardest cases. For a family blocked only by a missing pay stub, one call closes the gap. The outcome measured is completion, not "notice sent," and the coverage floor for the previously-invisible segments actually rises.

How it works

What distinguishes it from a mass reminder is targeting on the completion gap and matching help to the blocker:

  • Target the non-completers, not everyone. The campaign list is drawn from who is below the floor, so effort concentrates on endpoints an ordinary flow leaves behind.
  • Diagnose the blocker per endpoint. Each target is segmented by why it's stuck, because a bad address, a missing document, and a trust gap need different fixes.
  • Deliver the specific missing piece. The contact carries the exact thing the endpoint needs to satisfy the success contract — the document link, the eligibility fix, the translated form — not a generic nudge.

Tuning parameters

  • Targeting precision — broad blast versus tightly filtered to true non-completers. Precision saves cost and avoids nagging the already-served, but risks missing people the data doesn't flag as stuck.
  • Channel mix — call, text, mail, in-person, or a trusted intermediary. Higher-touch channels convert the hardest endpoints but cost far more each.
  • Persistence — how many attempts, spaced how far apart, before stopping. More attempts lift completion but tip into harassment past a point.
  • Blocker specificity — a generic reminder versus blocker-specific help ("upload this one document here"). Specific help converts far better but requires knowing each endpoint's exact obstacle.
  • Trusted-messenger use — whether low-trust segments are reached through community intermediaries rather than the provider directly.

When it helps, and when it misleads

Its strength is that it actively closes the residual gap for endpoints that will never self-serve — precisely the ones a dispatch-level dashboard renders invisible because the upstream step "succeeded." It turns "we notified them" into "they completed." Its failure mode is that outreach can quietly subsidize a needlessly hard upstream design: if everyone needs a phone call to finish, the fix is the form, not a bigger call center — and untargeted outreach degrades into spam that erodes trust and depresses response to the next campaign. The classic misuse is running outreach against a contact quota ("we reached 10,000 people") rather than a completion outcome — activity theater that books effort as impact. The discipline is to measure completions caused, not contacts made, and to route recurring blockers back into fixing the standard flow.[1]

How it implements the components

Targeted Outreach Campaign realizes the reach-and-completion side of the archetype — the components an active outreach effort fills, not the standing-place or measurement machinery:

  • coverage_floor — the campaign is the instrument that lifts the worst-served segments to a guaranteed minimum: it targets exactly the endpoints below the floor and works them until they clear it.
  • endpoint_success_contract — it operates on the gap between an endpoint and "done," supplying the missing information, eligibility, or consent the success contract requires so an endpoint that couldn't complete now can.

It does not run a standing local place where people get assisted help (local_capacity_and_knowledge_pool, handoff_boundary) — that is Community Access Point; nor does it verify prerequisites before dispatch (endpoint_privacy_and_safety_guardrail), which is Address or Endpoint Validation.

References

[1] Active case finding is the public-health practice of proactively seeking out individuals who need a service instead of waiting for them to present; its discipline — and its ethical line — is that it must be paired with the capacity to actually help those it finds, or it merely surfaces need it cannot meet. ↩