---
name: share-link-follow-up
description: Checks engagement on shared Supademo links — who watched, what they lingered on, where they stopped — and drafts follow-up outreach grounded in that behavior. Use before a check-in call or when a deal has gone quiet.
---

# Share Link Follow-up

"Just checking in" is a wasted email. "Saw your team spent time on the SSO section — want 15 minutes with our security lead?" is not.

## Prerequisites

- Supademo MCP connected
- Demos/showcases shared via trackable links

## Workflow

1. **Pull the engagement.** `get_demo_sessions` for shared demos; `get_showcase_sessions` + `get_showcase_session_details` for showcases. Focus on the account in question.
2. **Read the behavior, not just the count:**
   - **Which demos** in the showcase got opened — and which got skipped
   - **Depth** — completed vs bailed at step N (pull `get_demo` to name what step N shows)
   - **Revisits** — a demo watched twice, or forwarded viewers appearing, signals internal championing
   - **Recency** — engagement this week beats engagement last month
3. **Classify the signal:**
   - 🔥 Multiple viewers, deep completion, revisits → buying committee is active; propose next step
   - 🌡️ One viewer, partial → champion exploring; send the thing they didn't finish, shorter
   - 🧊 Link never opened → the email failed, not the demo; new angle, new subject line
4. **Draft the follow-up.** 3–4 sentences referencing what they actually watched — specific but not creepy ("your team explored the reporting section," not "Dana watched step 7 at 9:14pm"). Match the ask to the signal tier.
5. **Deliver the draft.** The rep reviews and sends. Never send outreach directly.

## Guardrails

- Session data is sensitive — summarize behavior at account level in outreach; never name individual viewers unless they identified themselves (e.g., via a lead capture form).
- No engagement data ≠ no interest; links get watched on phones, forwarded, screen-shared. Treat absence of signal as absence of signal.