Phase 8.5 — In-product education for Lead Pools: which form-factor(s)?

Goal: admins understand pools, the jargon, and what's possible — without reading code or asking. These aren't mutually exclusive; pick the mix. Mockups are rough — judging the approach, not pixels.

A · Inline help — tooltips + glossary + legends

/admin/pools/[id] · Members tab
State ?ACTIVE
Source type ?BLAST_RESPONDERS ?
next_callable_at ?in 2h 14m
BLAST_RESPONDERS — pool auto-fills with leads who replied to one or more SMS blasts. Membership grows over time as new responders arrive. Refresh pulls the latest.
Legend (always-visible on Members tab)
ACTIVEdialable / textable now (subject to cooldown)
COOLDOWNrecently contacted — waiting out the disposition window
next_callable_atearliest this agent can be dialed again
Pros: low-risk, no new dep, lives exactly where confusion happens. Cons: doesn't teach "the big picture" — you learn one term at a time. no new libsmallest scope

B · Guided walkthrough — step-through product tour

/admin/pools — first visit (or "Take the tour" button)
📊 Pool list · 39 pools · member counts + status breakdown

Step 2 of 7 — What a pool is

A pool is one shared bucket of leads keyed by a recipe (a filter preset, a manual list, or "everyone who replied to a blast"). Campaigns that share a recipe share the pool — so the same person never gets dialed twice across sibling campaigns.

● ● ○ ○ ○ ○ ○SkipNext ›
Pros: teaches the model end-to-end; great for onboarding new admins; "Take the tour" is re-runnable. Cons: needs a tour lib (driver.js, ~5KB) + step config per page; tours rot when UI changes. new lib: driver.jsmost effort

C · Dedicated guide page — /admin/pools/guide

ConceptsSource typesStatesCooldownsActionsFAQ

What is a Lead Pool?

One shared set of leads keyed by a recipe. Tracks voice + SMS recency per agent so siblings don't double-contact…

The 3 source types

FILTER_PRESET — leads matching a saved filter. MANUAL — a hand-curated list. BLAST_RESPONDERS — auto-grows with blast repliers.

Member states

ACTIVE · COOLDOWN · TERMINAL · DNC — and how each is set…

Pros: one canonical place for "all the possibilities"; easy to maintain; deep-linkable (/guide#cooldowns). Cons: separate from the work — admins must choose to go read it. no new libmedium scope
My lean: A + C — inline tooltips/legends everywhere confusion bites, plus one canonical /admin/pools/guide page that the inline "?" popovers deep-link into ("…learn more about source types ↗"). Skip the full guided tour (B) for now — highest effort, rots fastest; can add later as Phase 8.6 if onboarding new admins becomes a real need.

→ Question on screen: A only · C only · A + C (recommended) · A + B + C (the works) · something else?
Reply in the terminal.