Customer onboarding and training

Extract follow-up items from this training/implementation session.

CRITICAL: Capture ONLY items that require future action or follow-up.

Do NOT log:
- Questions that were fully answered during the session
- Discussion that resolved during the call
- Background context or pleasantries
- Items already covered in earlier sessions (unless they re-surfaced
  as still unresolved)

Be faithful to the conversation — only include items that were
actually raised or committed to. Where ownership is unclear, write
"Unclear — confirm" rather than guessing.

No emojis. Be concise.

Format:

# Training Session: {Customer} — {Session topic} — YYYY-MM-DD
**Trainer/EIC:** {Name}
**Customer attendees:** {Names with roles}
**Session number:** {e.g., 3 of estimated 12}
**Implementation phase:** Kickoff | Configuration | Training | Pre-Go-Live | Go-Live | Post-Launch

## Headline
One sentence: the most important thing about this session and where
the implementation stands after it.

## Items requiring follow-up (the queue)

### Questions needing configuration
- **Item:** {specific question or configuration need}
  **Customer context:** {what the customer is trying to accomplish}
  **Owner:** Trainer | Customer | Both
  **Priority:** Blocker | High | Medium | Low
  **Target resolution:** {date or session}
  **Notes:** {context the resolver needs}

(If no items: "None this session.")

### Feature requests
- **Request:** {what the customer is asking for}
  **Underlying job:** {what they're actually trying to accomplish}
  **Stated urgency:** {from the customer's framing}
  **Owner:** Product (with trainer to log)
  **Quote (if useful):** "{verbatim from session}"

### Documentation gaps
- **Gap:** {topic that lacked documentation}
  **What the customer needed:** {specific information}
  **Owner:** Documentation team
  **Workaround:** {what the trainer provided}

### Bug reports
- **Symptom:** {what's broken}
  **Customer environment:** {relevant context}
  **Repro steps:** {if discussed}
  **Owner:** Engineering (with trainer to file)
  **Workaround:** {if any}

### Follow-ups by trainer / EIC
- **Action:** {what the trainer committed to do}
  **By when:** {committed date or next session}
  **Notes:** {context}

### Follow-ups by customer
- **Action:** {what the customer committed to do}
  **Who specifically on customer side:** {if multiple stakeholders}
  **By when:** {committed date or next session}
  **What it unblocks:** {why this matters to the implementation}

### Follow-ups by other team
- **Action:** {what's needed}
  **Owner:** {team — engineering, support, product, billing}
  **By when:** {target}
  **Notes:** {context the other team needs}

## Risks and concerns
Things raised that signal implementation or relationship risk. Be
honest; flag what would normally be tempting to soft-pedal.
- {Risk} — {what to monitor}

## Wins and positive signals
- {Signal} — {context, quote if useful}

## What was resolved in this session
A brief reminder of what NOT to log — items that came up and were
fully handled during the session. This section is for the trainer's
mental confirmation; it doesn't need to go to the customer.
- {Resolved item — one line each, no detail needed}

## Next session
- **Planned date:** {date or "TBD"}
- **Planned topic:** {agenda}
- **Customer prep needed:** {what the customer should do before next}
- **Trainer prep needed:** {what the trainer should do before next}

## Customer-facing follow-up email (paste-ready)
A 150–250 word email I can send to the customer same-day:
- Brief recap of what we covered
- Items the customer needs to follow up on (their queue, their language)
- Items the trainer/EIC is following up on (set expectations)
- Next session details
- One warm closing sentence

{Email content drafted here, ready to be pasted into the trainer's email client}

Based on this training session transcript, draft a follow-up email
to the customer. Warm but professional; references what was discussed;
includes the customer's specific follow-ups; sets expectations for
what the trainer is doing.

Constraints:
- Under 250 words
- Address the customer by name (extract from transcript)
- Open with a sentence specific to what was discussed, not generic thanks
- Use the customer's language where it appeared in the session
- No emojis
- Sign-off placeholder for trainer to fill

Format:

Subject: {Concrete subject — e.g., "Follow-up from today's training on {topic}"}

Hi {Customer name},

{One to two sentences specific to what was discussed. Reference a
topic or a moment, not generic thanks.}

Quick recap of what we covered:
- {Topic 1 — one line in customer language}
- {Topic 2 — one line}
- {Topic 3 if applicable}

A few things on your side to follow up on:
- {Customer action} — {why it matters or when needed}
- {Customer action}

What I'll be following up on for you:
- {Trainer action} — {by when}
- {Trainer action} — {by when}

{If escalating: "I've also flagged {topic} to our {team} — I'll loop
back when I hear back."}

{If there are unresolved questions:} A couple of questions I want to
confirm before our next session — I'll follow up with answers by {date}.

Our next session is {date/time} and we'll cover {topic}.

{One warm closing sentence — references a customer goal, a positive
moment from the session, or forward momentum.}

—
{Sign-off placeholder}

Synthesize across the training session artifacts provided for this
customer. Produce an implementation snapshot showing where the
customer stands now: what's been resolved, what's still open, what's
at risk, what's coming next.

Format:

# Implementation Snapshot: {Customer} — As of YYYY-MM-DD
**Implementation start date:** {date}
**Current phase:** {phase}
**Target go-live date:** {date}
**Sessions completed:** {N of estimated total}
**Primary trainer/EIC:** {Name}
**Customer key contacts:** {list with roles}

## Implementation health
**Overall status:** On track | At risk | Behind | Churn risk
**Reasoning:** Two to three sentences grounded in observed signals.

## Items still open across the implementation

### Questions needing configuration
Aggregate across sessions; show which session each item came from.
- {Item} — opened in {session N} — owner — target resolution

### Feature requests
Aggregate; flag if any have been pending unusually long.
- {Request} — opened in {session N} — current status with product

### Documentation gaps
Aggregate.
- {Gap} — opened in {session N} — status

### Bug reports
Aggregate; flag any blocking customer's progression.
- {Bug} — opened in {session N} — status

### Customer-side actions still pending
- {Action} — committed in {session N} — current status

### Trainer/internal actions still pending
- {Action} — committed in {session N} — current status

## Items resolved across the implementation
A summary count and key resolutions:
- {N} configuration items resolved
- {N} feature requests logged to product
- {N} documentation items routed to docs team
- Key resolutions worth noting: {list}

## Risks
Items raised across sessions that signal implementation or renewal
risk. Be honest.
- {Risk} — {evidence from sessions where it appeared}

## Wins and positive signals
- {Signal} — {session where it surfaced, quote if useful}

## Customer's stated goals (tracked across sessions)
What has the customer said they want to achieve? Has it shifted?
- {Goal} — first stated in {session N} — current status

## Stakeholder map
- **{Name}:** {role} — {engagement read: Engaged | Periodic | Absent}

## Recommendation
Given the state of the implementation, what's the recommended next
action?

## Cross-team escalations needed
Items requiring escalation outside the implementation team.

Synthesize across the training session artifacts provided (multiple
customers, specified period). Identify patterns worth acting on at
the team or product level.

Format:

# Cross-Customer Pattern Report — Period: {date range}
**Customers covered:** {count}
**Sessions analyzed:** {count}
**Trainers/EICs involved:** {list}

## Configuration questions that recurred
Questions or configuration needs that appeared across multiple
customers. For each:
- **Pattern:** the recurring question/need
- **Customers affected:** count and segment characteristics
- **Currently handled by:** whoever resolves it now
- **Recommendation:** Document it | Train all trainers | Build self-serve | Address in product

## Feature requests that recurred
- **Request:** the capability requested
- **Customers requesting:** count and segment
- **Stated urgency:** pattern in how urgently it was requested
- **Current status with product:** filed | not yet filed | in development

## Documentation gaps recurring
- **Gap:** topic that lacked documentation
- **Customers affected:** count
- **Recommendation:** specific documentation to create or update

## Bug patterns
- **Bug:** description
- **Customers reporting:** count
- **Engineering status:** open | in progress | fixed | not yet filed

## Customer-side friction patterns
Common places customers struggle:
- **Friction point:** what customers find difficult
- **Customers affected:** count
- **Recommendation:** training adjustment | UX improvement | docs | onboarding flow change

## Trainer behavior patterns
- **Pattern:** trainer behavior
- **Observed in:** how widely
- **Recommendation:** enablement | template update | training

## Implementation timing patterns
- Average session count per implementation: {number}
- Common stuck points: {list}
- Customers with implementations dragging beyond expected timeline: {count}

## Risk patterns across customers
- {Risk pattern} — {count of customers} — {recommendation}

## Recommendations for next period
- **Product team:** {list}
- **Documentation team:** {list}
- **Training enablement:** {list}
- **Implementation process:** {list}

## Customers worth special attention
- **At-risk:** customers showing concerning signals
- **Champions:** customers with strong positive signal worth amplifying