ETS Performance / Touchpoint Maps / Mankato
v1.0 · Locked Spec May 2026
Loading touchpoint spec…
00WAVE 2 · LOCKED SPEC

The Mankato touchpoint map.

Every workflow, every node, every piece of content. Two parent avatars, four pipelines, the complete operating system underneath the Go High Level build. Designed for snapshot clone to 80 future ETS locations.

Workflows
CK · ES · Shared
Total Nodes
across all workflows
Content Pieces
reused · new
Pipelines / Tags / Fields
snapshot-portable taxonomy
01The two parents

Two avatars. Distinct funnels. One snapshot.

Every parent who enters the funnel is classified as Covenant Keeper or Evidence Seeker. The classifier runs at intake (quiz fork, form field, or AI Employee SMS). From that moment the journey forks — different copy, different proof currency, different decision triggers.

Avatar A · CK
· 5 stages · 30-day arc
Avatar B · ES
· 5 stages · 42-day arc
02The architectural decisions

Five calls the marketing team should know.

These shaped the architecture. Each is a real fork in the road — alternative paths exist, but the funnel architect picked these and justified each one.

03Build sequencing

What gets built when.

Workflows are tiered by build priority. Tier 1 is required before any traffic. Tier 4 is the last to ship before snapshotting to the next location.

Tier 1
6
Foundation
Required before any lead enters. Intake router, pre-eval, primary funnels, chatbot.
Tier 2
6
Pre-traffic
Post-eval workflows, no-show recovery, stalled-trial recovery, first-class lifecycle.
Tier 3
6
Pre-scaling
Full activation arcs, AI receptionist, quiz nurture, sales-7 sequences.
Tier 4
6
Pre-snapshot
Re-engagement, dunning, voicemail recording, AI knowledge base seeding.
Avatar A · Covenant Keeper
CK8 workflows · awareness → 30-day nurture

The Covenant Keeper workflows.

Avatar B · Evidence Seeker
ES8 workflows · awareness → Day 42 re-test bridge

The Evidence Seeker workflows.

SHARED8 workflows · avatar-agnostic

Shared workflows.

Workflows that don't fork by avatar. The intake router, post-booking confirmation, recovery sequences, the 24/7 AI receptionist, re-engagement sunset, and dunning. These run alongside (and across) every avatar funnel.

04Top-down view

How the 24 workflows fit together.

Read left to right: every lead enters via an entry point, passes through the shared intake router, forks into CK or ES paths, and either books, stalls, recovers, or sunsets. The shaded columns show shared workflows that overlay everything.

Interconnect details
49 handoff edges connect the 24 workflows. The intake router (SHARED-01) is the single entry hub. CK and ES paths run in parallel — same shape, different copy. The pre-eval / post-eval / first-class / 30-day-nurture chains live inside each avatar; the no-show recovery, stalled-trial recovery, AI receptionist, dunning, and re-engagement sunset overlay across both.
05The operating system

GHL taxonomy.

Pipelines, tags, custom fields, lead scoring, and handoff SLA — the layer underneath every workflow. Designed to be snapshotted and cloned to 80 future ETS locations.

Demographic / fit (max 30 points)

SignalPoints

Engagement behaviors (decaying)

SignalPointsDecay

Intent behaviors (high-signal)

SignalPointsDecay

Conversion behaviors (no decay)

SignalPoints

Negative signals

SignalPoints

Thresholds & triggers

Triggers for handoff

SLA response times

Handoff payload elements

When handoff fires, the director sees these elements pinned at the top of the contact view: