Skills › Knowledge Work Plugins › lead-triage › gotchas.md
gotchas.md
76 lines · small-business/skills/lead-triage/reference/gotchas.md at 2574e29
5## Gotcha: "Pipeline" bare trigger runs full scoring when user just wants a status check
7**Why it matters:** "Pipeline" alone is ambiguous — the owner may want deal-stage totals, not a scored call list.
Gotcha: "Pipeline" bare trigger runs full scoring when user just wants a status check
Why it matters: "Pipeline" alone is ambiguous — the owner may want deal-stage totals, not a scored call list.
Raw lines 5 to 89### ✗ Bad
10```
11User: "how's my pipeline?"
12Claude: [runs full scoring, returns 12-lead ranked list]
13```
✗ Bad
User: "how's my pipeline?"
Claude: [runs full scoring, returns 12-lead ranked list]15### ✓ Good
16```
17User: "how's my pipeline?"
18Claude: "Quick pipeline overview (deal stages + total value) or prioritized
19 call list for today?"
20```
22---
✓ Good
User: "how's my pipeline?"
Claude: "Quick pipeline overview (deal stages + total value) or prioritized
call list for today?"Raw lines 15 to 23
24## Gotcha: Stale engagement data inflates scores
26**Why it matters:** `hs_email_open` is cumulative — opens from a year-old campaign make a cold lead look hot.
Gotcha: Stale engagement data inflates scores
Why it matters: hs_email_open is cumulative — opens from a year-old campaign make a cold lead look hot.
28### ✗ Bad
29```
30Lead has 20 opens (all 11 months ago). Scores 25/25 on engagement.
31Appears as #1. Owner calls; lead has no memory of the brand.
32```
✗ Bad
Lead has 20 opens (all 11 months ago). Scores 25/25 on engagement.
Appears as #1. Owner calls; lead has no memory of the brand.34### ✓ Good
35```
36Cap engagement signals at 30 days. If all signals are older than 30 days,
37engagement score = 0 and talking point notes:
38"Engagement signals are stale (last: [date]) — approach as cold outreach."
39```
41---
✓ Good
Cap engagement signals at 30 days. If all signals are older than 30 days,
engagement score = 0 and talking point notes:
"Engagement signals are stale (last: [date]) — approach as cold outreach."Raw lines 34 to 42
43## Gotcha: Customers appear in the lead list
45**Why it matters:** Calling a `Customer` or `Evangelist` as a lead prospect is embarrassing.
Gotcha: Customers appear in the lead list
Why it matters: Calling a Customer or Evangelist as a lead prospect is embarrassing.
52### ✓ Good
53```
54Filter strictly: lifecyclestage = Lead or MQL only.
55If a contact has a blank lifecycle stage, include with a warning flag:
56"⚠ Lifecycle stage not set — confirm this is a lead before calling."
57```
59---
✓ Good
Filter strictly: lifecyclestage = Lead or MQL only.
If a contact has a blank lifecycle stage, include with a warning flag:
"⚠ Lifecycle stage not set — confirm this is a lead before calling."Raw lines 52 to 60
61## Gotcha: Proposing calendar slots that conflict with existing events
63**Why it matters:** Proposing a time the owner is already booked erodes trust immediately.
Gotcha: Proposing calendar slots that conflict with existing events
Why it matters: Proposing a time the owner is already booked erodes trust immediately.
Raw lines 61 to 6465### ✗ Bad
66```
67Claude proposes "Tuesday 2–2:30 PM" without checking Calendar.
68Owner already has a client call in that slot.
69```
✗ Bad
Claude proposes "Tuesday 2–2:30 PM" without checking Calendar.
Owner already has a client call in that slot.71### ✓ Good
72```
73Fetch Calendar for next two business days before proposing any slot.
74Only propose windows with no existing events ±15 minutes buffer.
75If no free window exists, say so and offer to look further out.
76```
✓ Good
Fetch Calendar for next two business days before proposing any slot.
Only propose windows with no existing events ±15 minutes buffer.
If no free window exists, say so and offer to look further out.