Lead Workflow Designer

Inbound triage

by LeadMagic · MIT license · ★ 62 on GitHub

Inbound triage cover

Design inbound lead triage workflows — demo form qualification, MQL to SQL routing, automated enrichment on form fill, speed-to-lead SLAs. Use when the user wants to handle inbound leads, route demo requests, qualify form fills, or…

---
name: inbound-triage
description: >-
  Design inbound lead triage workflows — demo form qualification, MQL to SQL
  routing, automated enrichment on form fill, speed-to-lead SLAs. Use when the
  user wants to handle inbound leads, route demo requests, qualify form fills,
  or build an inbound pipeline. Triggers on: "inbound triage", "demo request",
  "lead routing", "MQL", "SQL", "speed to lead", "form qualification", "inbound
  process", "qualify inbound leads", or any request about handling incoming leads.
license: MIT
compatibility: Claude Code, Codex, GitHub Copilot, Cursor, Gemini CLI, OpenCode, Goose, Hermes, Windsurf, Zed
metadata:
  version: "1.0.0"
  author: LeadMagic
  category: inbound
  tags: [inbound, triage, routing, qualification, lead-management]
  related_skills:
    [

Overview

Speed kills in inbound. A lead contacted within 5 minutes is 100x more likely to convert than one contacted after 30 minutes. Yet most teams route leads manually, respond in hours, and wonder why inbound doesn't convert.

Manual install (npx, ZIP)
Claude Codenpx skills add LeadMagic/gtm-skills --skill inbound-triage -g -a claude-code
Claude Code (degit)npx degit LeadMagic/gtm-skills/skills/inbound/inbound-triage#main ~/.claude/skills/inbound-triage
Claude.ai / desktopZip the folder and upload it under Settings → Capabilities → Skills.
Codex, Cursor, other agentsPoint them at SKILL.md. The other files are plain text.

Connects with Agent Alley MCP · agentalley.io/mcp

Files included

  • SKILL.md8.1 KB
Read SKILL.md here
LeadMagic/main1 file shown
SKILL.md
Show the full text195 lines

Inbound Triage

Overview

Speed kills in inbound. A lead contacted within 5 minutes is 100x more likely to convert than one contacted after 30 minutes. Yet most teams route leads manually, respond in hours, and wonder why inbound doesn't convert.

This skill designs an automated inbound triage system: enrichment on form fill, ICP qualification in seconds, routing to the right rep, and SLAs enforced from moment one. The output is a complete inbound workflow that captures every lead and routes it faster than any human team.

When to Use

  • "Set up inbound lead routing"
  • "How should we handle demo requests?"
  • "Qualify our inbound leads automatically"
  • "Build an MQL to SQL handoff process"
  • "Speed up our lead response time"
  • "Design an inbound qualification workflow"

Authoritative Foundations

Inbound triage follows Winning by Design's SPICED lifecycle model, which maps the full customer journey from first contact through expansion. The inbound stage sits at the critical handoff between marketing (MQLs) and sales (SQLs).

SiriusDecisions' Demand Waterfall framework establishes that clear MQL/SQL definitions with automated routing correlate with 20%+ higher conversion rates and 30%+ faster sales cycles.

Dharmesh Shah (HubSpot) — Engage stage. Inbound triage is the operational Engage leg of the flywheel: speed-to-lead, enrichment on form fill, and fit-based routing (not volume-based MQL inflation). Canonical playbook → references/dharmesh-shah-hubspot-inbound.md · Pattern 27 step 4.

Prerequisites

  • ICP defined (what makes a lead qualified)
  • CRM system (HubSpot, Salesforce, or Attio)
  • Enrichment provider for real-time lead enrichment on form fill
  • Lead scoring model (see lead-scoring skill)

Step-by-Step Process

Phase 1: Define Lead Stages
Stage Definition Qualification Criteria Owner
Lead Any identified contact Has email, some interest signal Marketing
MQL Fits ICP + engaged Firmographic fit + behavior threshold Marketing → SDR
SQL Ready for sales conversation MQL + explicit buying signal or demo request Sales
PQL (if PLG) Used product, upgrade potential Trial/freemium + usage threshold Product + Sales
SAL SQL accepted by rep Sales confirms qualification Sales
Phase 2: Build the Triage Workflow

Website visitor intent (company ID): Anonymous visits identified via reverse-IP (website-visitor-identification) feed account-level intent scores. Route to MQL only when ICP + engagement thresholds pass — not on every visit. Person-level visitor alerts use separate guardrails; default path is company ID → SDR research queue. Playbook: website-visitor-identification/references/visitor-identification-playbook.md.

  1. Form fill triggers enrichment. Webhook from form (HubSpot, Typeform, custom) fires enrichment on submit. Within 15 seconds, the lead is enriched with firmographic and contact data.

  2. ICP filter runs. Enriched data feeds into ICP scoring. Leads that don't fit the ICP get an automated nurture email and are routed to the marketing nurture track.

  3. MQL scoring. Leads passing ICP filter are scored on engagement signals: pages visited, content downloaded, demo requested.

  4. Routing. MQLs above threshold route to SDR within 15 minutes. Demo requests route directly to AE with calendar hold.

  5. SLA enforcement. Track response time, 2nd touch time, 3rd touch time. Alert manager when SLAs are breached.

Phase 3: Speed-to-Lead SLAs
Touch Target Time Action
1st touch <5 minutes Auto-response with calendar link + qualifying question
2nd touch <15 minutes Value drop + booking link
3rd touch <2 hours Nudge + social proof
4th touch Same day Call + personalized email
5th touch 24 hours Final attempt before nurture
Phase 4: Exceptions and Escalation
  • Enterprise leads (>target ACV): immediate AE assignment, skip SDR
  • Partner referrals: warm intro process, founder or AE handles
  • Support disguised as sales: route to support, don't waste SDR time
  • Competitors/spam: auto-archive, suppress from future routing

Output Format

Inbound triage workflow diagram + SLA document:

# Inbound Triage Workflow

Form Fill → Enrich (15s) → ICP Filter → Score → Route → SLA Enforcement

Routing rules:
- Demo request + ICP fit → AE calendar hold (5 min)
- MQL + score >60 → SDR (15 min)
- MQL + score 40-60 → Nurture track
- Non-ICP → Marketing nurture
- No enrichment data → Manual review queue

SLA dashboard:
- Response time by rep
- MQL→SQL conversion rate
- SQL→Opportunity conversion rate
- Lead leakage (where leads drop out)

Quality Check

  • Lead stages defined with clear qualification criteria
  • Enrichment completes within 15 seconds of form fill
  • SLAs defined and tracked for every touch
  • Routing rules documented and automated
  • Escalation paths for exceptions
  • Weekly SLA review cadence established

Common Pitfalls

  1. Manual routing. Every minute of manual routing is a minute the lead waits. A lead contacted in 5 minutes is 100x more likely to convert than one contacted in 30 minutes. Automate routing end-to-end.

  2. No enrichment before routing. Routing an unenriched lead means the SDR wastes time researching basic info. Enrich on form fill automatically.

  3. Vague stage definitions. When MQL means different things to marketing and sales, leads bounce between teams. Define stages with hard criteria.

  4. SLA theater. Defining SLAs without tracking and enforcement means they're aspirational. Automate alerting when SLAs are missed.

  5. Over-qualifying inbound. An inbound lead who took the time to fill a form has already self-qualified to some degree. Don't make them jump through more hoops — get them to a human.

Execution Artifacts

  • references/framework-notes.md — Named frameworks and reference tables
  • templates/output-template.md — Deliverable shell for agent output
  • scripts/check-output.py — Lightweight deliverable validator
  • website-visitor-identification: Company/person visitor ID → MQL routing
  • lead-scoring: Build the scoring model that powers triage decisions
  • pipeline-management: Manage leads after they enter the pipeline
  • crm-integration: CRM setup for automated routing and enrichment
1---
2name: inbound-triage
3description: >-
4 Design inbound lead triage workflows — demo form qualification, MQL to SQL
5 routing, automated enrichment on form fill, speed-to-lead SLAs. Use when the
6 user wants to handle inbound leads, route demo requests, qualify form fills,
7 or build an inbound pipeline. Triggers on: "inbound triage", "demo request",
8 "lead routing", "MQL", "SQL", "speed to lead", "form qualification", "inbound
9 process", "qualify inbound leads", or any request about handling incoming leads.
10license: MIT
11compatibility: Claude Code, Codex, GitHub Copilot, Cursor, Gemini CLI, OpenCode, Goose, Hermes, Windsurf, Zed
12metadata:
13 version: "1.0.0"
14 author: LeadMagic
15 category: inbound
16 tags: [inbound, triage, routing, qualification, lead-management]
17 related_skills:
18 [
19 signal-scoring,
20 pipeline-management,
21 crm-integration,
22 sales-enablement,
23 website-visitor-identification,
24 icp-scoring,
25 ]
26 frameworks:
27 - "Winning by Design SPICED Lifecycle"
28 - "SiriusDecisions Demand Waterfall"
29 - "Dharmesh Shah (HubSpot) — Inbound Engage & Flywheel Handoff"
30 - "HubSpot Academy — Inbound Methodology"
31---
32 
33# Inbound Triage
34 
35## Overview
36 
37Speed kills in inbound. A lead contacted within 5 minutes is 100x more likely
38to convert than one contacted after 30 minutes. Yet most teams route leads
39manually, respond in hours, and wonder why inbound doesn't convert.
40 
41This skill designs an automated inbound triage system: enrichment on form fill,
42ICP qualification in seconds, routing to the right rep, and SLAs enforced from
43moment one. The output is a complete inbound workflow that captures every lead
44and routes it faster than any human team.
45 
46## When to Use
47 
48- "Set up inbound lead routing"
49- "How should we handle demo requests?"
50- "Qualify our inbound leads automatically"
51- "Build an MQL to SQL handoff process"
52- "Speed up our lead response time"
53- "Design an inbound qualification workflow"
54 
55## Authoritative Foundations
56 
57Inbound triage follows Winning by Design's SPICED lifecycle model, which maps
58the full customer journey from first contact through expansion. The inbound stage
59sits at the critical handoff between marketing (MQLs) and sales (SQLs).
60 
61SiriusDecisions' Demand Waterfall framework establishes that clear MQL/SQL
62definitions with automated routing correlate with 20%+ higher conversion rates
63and 30%+ faster sales cycles.
64 
65**Dharmesh Shah (HubSpot) — Engage stage.** Inbound triage is the operational
66**Engage** leg of the flywheel: speed-to-lead, enrichment on form fill, and
67fit-based routing (not volume-based MQL inflation). Canonical playbook →
68`references/dharmesh-shah-hubspot-inbound.md` · Pattern 27 step 4.
69 
70## Prerequisites
71 
72- ICP defined (what makes a lead qualified)
73- CRM system (HubSpot, Salesforce, or Attio)
74- Enrichment provider for real-time lead enrichment on form fill
75- Lead scoring model (see lead-scoring skill)
76 
77## Step-by-Step Process
78 
79### Phase 1: Define Lead Stages
80 
81| Stage | Definition | Qualification Criteria | Owner |
82| ------------ | ------------------------------- | -------------------------------------------- | --------------- |
83| Lead | Any identified contact | Has email, some interest signal | Marketing |
84| MQL | Fits ICP + engaged | Firmographic fit + behavior threshold | Marketing → SDR |
85| SQL | Ready for sales conversation | MQL + explicit buying signal or demo request | Sales |
86| PQL (if PLG) | Used product, upgrade potential | Trial/freemium + usage threshold | Product + Sales |
87| SAL | SQL accepted by rep | Sales confirms qualification | Sales |
88 
89### Phase 2: Build the Triage Workflow
90 
91**Website visitor intent (company ID):** Anonymous visits identified via
92reverse-IP (`website-visitor-identification`) feed account-level intent scores.
93Route to MQL only when ICP + engagement thresholds pass — not on every visit.
94Person-level visitor alerts use separate guardrails; default path is company ID
95→ SDR research queue. Playbook:
96`website-visitor-identification/references/visitor-identification-playbook.md`.
97 
981. **Form fill triggers enrichment.** Webhook from form (HubSpot, Typeform,
99 custom) fires enrichment on submit. Within 15 seconds, the lead is
100 enriched with firmographic and contact data.
101 
1022. **ICP filter runs.** Enriched data feeds into ICP scoring. Leads that
103 don't fit the ICP get an automated nurture email and are routed to the
104 marketing nurture track.
105 
1063. **MQL scoring.** Leads passing ICP filter are scored on engagement
107 signals: pages visited, content downloaded, demo requested.
108 
1094. **Routing.** MQLs above threshold route to SDR within 15 minutes.
110 Demo requests route directly to AE with calendar hold.
111 
1125. **SLA enforcement.** Track response time, 2nd touch time, 3rd touch
113 time. Alert manager when SLAs are breached.
114 
115### Phase 3: Speed-to-Lead SLAs
116 
117| Touch | Target Time | Action |
118| --------- | ----------- | ------------------------------------------------------ |
119| 1st touch | <5 minutes | Auto-response with calendar link + qualifying question |
120| 2nd touch | <15 minutes | Value drop + booking link |
121| 3rd touch | <2 hours | Nudge + social proof |
122| 4th touch | Same day | Call + personalized email |
123| 5th touch | 24 hours | Final attempt before nurture |
124 
125### Phase 4: Exceptions and Escalation
126 
127- **Enterprise leads** (>target ACV): immediate AE assignment, skip SDR
128- **Partner referrals**: warm intro process, founder or AE handles
129- **Support disguised as sales**: route to support, don't waste SDR time
130- **Competitors/spam**: auto-archive, suppress from future routing
131 
132## Output Format
133 
134Inbound triage workflow diagram + SLA document:
135 
136```
137# Inbound Triage Workflow
138 
139Form Fill → Enrich (15s) → ICP Filter → Score → Route → SLA Enforcement
140 
141Routing rules:
142- Demo request + ICP fit → AE calendar hold (5 min)
143- MQL + score >60 → SDR (15 min)
144- MQL + score 40-60 → Nurture track
145- Non-ICP → Marketing nurture
146- No enrichment data → Manual review queue
147 
148SLA dashboard:
149- Response time by rep
150- MQL→SQL conversion rate
151- SQL→Opportunity conversion rate
152- Lead leakage (where leads drop out)
153```
154 
155## Quality Check
156 
157- [ ] Lead stages defined with clear qualification criteria
158- [ ] Enrichment completes within 15 seconds of form fill
159- [ ] SLAs defined and tracked for every touch
160- [ ] Routing rules documented and automated
161- [ ] Escalation paths for exceptions
162- [ ] Weekly SLA review cadence established
163 
164## Common Pitfalls
165 
1661. **Manual routing.** Every minute of manual routing is a minute the lead
167 waits. A lead contacted in 5 minutes is 100x more likely to convert than
168 one contacted in 30 minutes. Automate routing end-to-end.
169 
1702. **No enrichment before routing.** Routing an unenriched lead means the
171 SDR wastes time researching basic info. Enrich on form fill automatically.
172 
1733. **Vague stage definitions.** When MQL means different things to marketing
174 and sales, leads bounce between teams. Define stages with hard criteria.
175 
1764. **SLA theater.** Defining SLAs without tracking and enforcement means
177 they're aspirational. Automate alerting when SLAs are missed.
178 
1795. **Over-qualifying inbound.** An inbound lead who took the time to fill
180 a form has already self-qualified to some degree. Don't make them jump
181 through more hoops — get them to a human.
182 
183## Execution Artifacts
184 
185- `references/framework-notes.md` — Named frameworks and reference tables
186- `templates/output-template.md` — Deliverable shell for agent output
187- `scripts/check-output.py` — Lightweight deliverable validator
188 
189## Related Skills
190 
191- **website-visitor-identification**: Company/person visitor ID → MQL routing
192- **lead-scoring**: Build the scoring model that powers triage decisions
193- **pipeline-management**: Manage leads after they enter the pipeline
194- **crm-integration**: CRM setup for automated routing and enrichment
195 
View all files on GitHub →

Details

License
MIT
Stars on the repo
★ 62
Checked
Source
LeadMagic/gtm-skills ↗
Creator
LeadMagic · 129 listings
View creator

Similar skills

See all →
SkillSupabase Developer Toolsupabase/agent-skills · by supabaseUse when doing ANY task involving Supabase. Triggers: Supabase products (Database, Auth, Edge Functions, Realtime, Storage, Vectors, Cron, Queues); client libraries and SSR integrations (supabase-js, @supabase/ssr) in Next.js, React, SvelteKit, Astro, Remix; auth issues (login, logout, sessions, JWT, cookies, getSession, getUser, getClaims, RLS); Supabase CLI or MCP server; schema changes, migrations, declarative schemas, security audits, Postgres extensions (pg_graphql, pg_cron, pg_vector); debugging and troubleshooting errors or unexpected behavior on Supabase projects (HTTP errors, Postgres errors, RLS surprises, permission denied, schema cache issues, timeouts, Edge Function crashes, Realtime drops, Storage failures) and reading or querying logs (Logs Explorer, ClickHouse).★ 2.7k GitHub starsSkillNext.js App Router Guidewshobson/agents · by wshobsonMaster Next.js 14+ App Router with Server Components, streaming, parallel routes, and advanced data fetching. Use when building Next.js applications, implementing SSR/SSG, or optimizing React Server Components.★ 39.9k GitHub starsSkillDeal Review Agentalirezarezvani/claude-skills · by alirezarezvaniUse when reviewing a specific inbound deal before close — when sales has asked for a discount that exceeds AE authority, when the customer has redlined the MSA, when per-deal economics (margin after discount, multi-year payment shape, indemnity exposure) need to be quantified, or when discount approval needs to be routed to a named human approver (Sales Director, VP Sales, CFO, CRO, General Counsel). Covers deal review, discount approval routing, per-deal margin scoring, deal exception handling, MSA redline triage, contract landmine detection (uncapped indemnity, MFN, perpetual license-back, missing DPA), and named-approver chain assembly. NEVER auto-approves — every output is a numeric scorecard plus a routing recommendation to a named human.★ 26.3k GitHub starsSkillSaaS Project Scaffolderalirezarezvani/claude-skills · by alirezarezvaniGenerates complete, production-ready SaaS project boilerplate including authentication, database schemas, billing integration, API routes, and a working dashboard using Next.js 14+ App Router, TypeScript, Tailwind CSS, shadcn/ui, Drizzle ORM, and Stripe. Use when the user wants to create a new SaaS app, start a subscription-based web project, scaffold a Next.js application, or mentions terms like starter template, boilerplate, new project, or wiring up auth and payments.★ 26.3k GitHub starsSkillReact Frontend Engineeralirezarezvani/claude-skills · by alirezarezvaniFrontend development skill for React, Next.js, TypeScript, and Tailwind CSS applications. Use when building React components, optimizing Next.js performance, analyzing bundle sizes, scaffolding frontend projects, implementing accessibility, or reviewing frontend code quality.★ 26.3k GitHub starsAgentCLI Developer AgentVoltAgent/awesome-claude-code-subagents · by VoltAgentUse this agent when building command-line tools and terminal applications that require intuitive command design, cross-platform compatibility, and optimized developer experience.★ 25.2k GitHub stars

More from LeadMagic

SkillFirst-Party Analytics SetupLeadMagic/gtm-skills · by LeadMagicSet up first-party tracking and analytics — website pixels, conversion tracking, UTM architecture, cookie consent, server-side tagging vs client-side, 1P vs 3P data strategy, and identity resolution. Use when setting up tracking, implementing pixels, building attribution, or preparing for privacy-first measurement. Triggers on: "pixel", "tracking", "conversion tracking", "first-party data", server-side tagging", "UTM", "cookie consent", "1P vs 3P", "identity resolution", or any tracking implementation request.★ 62 GitHub starsSkillStrategic Account MarketingLeadMagic/gtm-skills · by LeadMagicRuns strategic 1-to-1 ABM for 5-15 high-value accounts: account plans, custom microsites, executive engagement, direct mail, and board-level connections. Use when a named enterprise account justifies bespoke content and executive time, or when the user needs a strategic account plan. Triggers on: "1-to-1 ABM", "strategic ABM", "custom ABM", "key account marketing", "named account".★ 62 GitHub starsSkillCluster Account MarketingLeadMagic/gtm-skills · by LeadMagicRuns ABM at scale (1-to-few) for 15-50 clustered accounts: industry or persona clusters, semi-custom campaigns, and cluster-level content. Use when named-account ABM needs to reach more accounts without bespoke work per account. Triggers on: "1-to-few ABM", "ABM scale", "cluster ABM", "industry ABM".★ 62 GitHub starsSkillProgrammatic Account TargetingLeadMagic/gtm-skills · by LeadMagicRuns programmatic 1-to-many ABM for 50-200+ accounts: automated personalization, scaled outbound, intent-based targeting, and lookalike expansion. Use when ABM coverage must grow without adding headcount or when the user wants automated account-based outreach. Triggers on: "1-to-many ABM", programmatic ABM", "scaled ABM", "automated ABM".★ 62 GitHub starsSkillAccount Strategy DesignerLeadMagic/gtm-skills · by LeadMagicDesigns an account-based marketing program: tier selection, account scoring, channel orchestration, BDR alignment (account-based sales development), and a measurement framework. Use when the user is launching or redesigning ABM, choosing between 1-to-1, 1-to-few, and 1-to-many, or building a target account program. Triggers on: "ABM strategy", "account based marketing", "ABM playbook", "design ABM", "target accounts", "ABSD", "account based sales development", "Lars Nilsson".★ 62 GitHub starsSkillTarget Account SelectorLeadMagic/gtm-skills · by LeadMagicBuilds and tiers a target account list: fit and intent scoring models, tier assignment, and TAM segmentation. Use when the user needs to decide which accounts to target, score or tier an account list, or prioritize a TAM for ABM or outbound. Triggers on: "account selection", "target account list", "tier accounts", "prioritize accounts", "TAM segmentation".★ 62 GitHub stars