CUI // PRVCY — Demonstration environment · notional data only
Readiness Factory ← Admin tasks Campaign editor Factory Floor All Forms
Admin · Tasker

The outreach engine — it picks the channel, you see the trail.

Every service member with an open task gets followed up automatically. The Tasker learns which channel each person actually answers — and walks the ladder from email to text to a conversational AI that finishes the task with them. Quiet hours honored. No health details in any message. Every touch logged.

Urgency from Doppler · trail rendered by CareSignals.ai — see the commercial platform live ↗
Reach rate · 30 d
94%
members who responded on some channel
Completed via conversational AI
31%
of late completions — the nudge finishes the task
Avg touches to completion
2.3
down from 5.1 with blast email alone
Quiet-hours holds today
12
sends waiting for the member’s morning

Default progression — escalate the medium, not the tone

Population default per App A 2.2 / 3.1. Doppler urgency compresses it: a score ≥ 85 moves a member to the next stage after one day, not three.

Day 0–1 · stage 1
✉ Email
gov, then personal · 58% complete here
Day 3 · stage 2
✉‍ Text (SMS)
+21% · opens in minutes, not days
Day 7 · stage 3
💬 Conversational AI
+12% · doesn’t remind — completes the task with them
Day 10 · stage 4
🎙 Voice — VIDA
+2% · broadband-free · unit notified
Day 14 · exhausted
Human takes over
admin task opens (3.1.4)

Members with a learned channel preference skip straight to what works for them — the ladder is the default, not a rule. Tracker flags at day 7 and unit notification at day 10 fire on schedule regardless of channel.

It chooses the right way to reach each person

Learned from response history — every outcome updates the choice. Tap a row for the full outreach trail.

AB SGT Ba, Amadou · A Co
PHA due 08 Jul · day 8 · not started
Learned: text-first — answers SMS in ~40 min; 0 of 6 emails ever opened Next: Conversational AI · today 17:30
after duty hours · his usual response window
  • Day 0 · 30 Jun 07:00Gov email not opened
  • Day 1 · 01 Jul 07:00Gov email repeat not opened
  • Day 3 · 03 Jul 07:05Personal email not opened — 6th consecutive unopened email
  • Day 6 · 06 Jul 17:31Text (SMS) read in 38 min — replied “this weekend” · no completion
  • Day 8 · today 17:30Conversational AI check-in scheduled — timed to his response window
⚙ What the Tasker learned: email is dead for this member — future campaigns start him at SMS. Evening sends outperform morning 4:1 for him. Doppler 69 — standard ladder pace.
CW SrA Whitfield, Corey · 23 MXS
PHA past due 18 d · escalation day 12
Opens personal email, never clicks — message isn’t the problem, the link is Next: Voice — VIDA · tomorrow 09:00
press-2 completes by phone · unit already notified (day 10)
  • Day 0–3Gov email ×2, personal email ×1 opened ×2 no click
  • Day 7 · 27 JunText (SMS) delivered · no reply · tracker flagged
  • Day 9 · 29 Jun 18:02Conversational AI check-in opened · abandoned at sign-in — possible CAC issue
  • Day 10 · 30 JunUnit notified (23 MXS) unit notified
  • Day 12 · todayDoppler 89 — ladder compressed; voice stage pulled forward
⚙ What the Tasker learned: engagement isn’t the barrier — access is. Abandoned at sign-in → voice channel (no sign-in needed to start) chosen next; help-desk hint attached to the call script.
LP SGT Pham, Linh · HHC 3-7 IN
PHA complete ✓ — finished via conversational AI
Success story — 2 ignored emails, then done in one conversation No outreach needed
completed 11 Jun 21:05 · 11 minutes
  • Day 0–1Gov email ×2 not opened
  • Day 3 · 21:00Text (SMS) read in 4 min — tapped the link, didn’t start
  • Day 4 · 21:05Conversational AI check-in completed the PHA — 11 min, 31 answers pre-confirmed, 5 deltas settled in-conversation, signed by DoD ID
  • Day 4 · 21:16Status → SM Submitted · reviewer task created done
⚙ What the Tasker learned: 21:00–22:00 is her window; conversational beats forms for her. Next year she starts at conversational AI, day 0, 21:00.
AG SPC Gallo, Anthony · B Co
PHA past due 12 d · ladder exhausted day 14
No response on any digital channel — automation stops, a human starts Human outreach — admin task open
phone log shows he’s on leave through 05 Jul
Open admin task →
  • Days 0–10Email ×3, text ×1, conversational ×1, unit notified no response
  • Day 14 · 01 JulLadder exhausted — admin task 3.1.4 · human review
  • 02 JulAdmin call: on leave through 05 Jul — snooze set, outreach resumes 06 Jul at text stage
⚙ What the Tasker learned: leave status now checked before sends — a data signal the module requested from the Paratus Data Service for the whole population.
PO PVT Okonkwo, Chidi · HHC 3-7 IN
First PHA · tracker opened yesterday
No history yet — default ladder, learning starts with send #1 Next: Gov email · tomorrow 07:00
stage 1 · personalized welcome (2.1.1.4.1)
  • No outreach yet. Every outcome from here trains his channel profile.

How it decides

Channel choice = learned responsiveness (opens, replies, completions per channel) × time-of-day window × Doppler urgency × policy rules (quiet hours, opt-outs, leave status). High urgency compresses the ladder; a learned preference skips it. Every decision is logged with its reasoning — auditable, explainable, adjustable in the campaign editor.

© 2026 Life365, Inc. All rights reserved.  ·  PATENT PENDING  ·  Build v19.2-VA-WCAG22 · 02 Jul 2026  ·  CONFIDENTIAL