Intent Spike Triage
The intent spike list, calibrated — new-to-threshold accounts with the default angle that actually converts.
Sample output for this workflow will appear here once it is captured.
Run the workflow in Claude, ChatGPT, or Phoenix Playground using the buttons below to see real output.
Overview
Triage the accounts that newly crossed an intent threshold on your category in the last 30 days. The single-trigger entry point for an SDR onboarding into a territory: returns the new-to-threshold accounts with a default opening angle per account, calibrated by intent stage and topic relevance per `intent-data-calibration`.
Use cases
Onboarding's first prospecting run that doesn't waste a week
Your new SDR runs this on day-three with a territory filter and gets a ranked list of accounts that crossed the intent threshold in the last 30 days, with the buying function and default angle per account. They build intuition by sequencing real, calibrated signals — not by hunting through dashboards.
Calibrated, not aggregated — `Researching` doesn't lead
The workflow respects `intent-data-calibration`: only `Evaluating` and `Buying` rows make the action list. `Researching` rows go to the watch list as corroboration. SDRs stop opening messages with 'I noticed you're researching X' — the move that destroys credibility on the first email.
View workflow prompt
# Intent Spike Triage
## Parameters
- `{{your_product}}` *(required)* — Your product or category — used to resolve canonical intent topic_ids. Example: `Datadog`
- `{{score_threshold}}` *(required)* — Intent score threshold (0-100). Use 80 — the canonical "strong intent" threshold — unless you have territory-specific tuning.. Example: `80`
- `{{territory_filter}}` *(optional)* — Optional firmographic filter (industry, country, employee band) to scope the territory. Example: `industry: SaaS, country: US`
## Purpose
You are an SDR onboarding into a territory or grading the week's intent surface for {{your_product}}. Return accounts that **newly** crossed score {{score_threshold}} (default 80) in the last 30 days with default opening angles calibrated by intent stage. Per [`intent-data-calibration`](https://phoenix.hginsights.com/gtm/skills/intent-data-calibration), `buyers_journey: "Evaluating"` and `"Purchasing"` are commercial-trigger-grade; `"Researching"` is education-stage and corroborates but does not lead.
## Process
1. **Resolve topics** — `list_intent_topics` once for {{your_product}}'s category. Capture canonical `topic_id`s and `topic_name`s.
2. **Cohort scan** — `intent_category` per resolved `topic_name` (intent-lookup mode; do NOT pass `filters` — that flips the tool to activity-search mode and drops `topic_name`). Returns the company list scoring on the topic. Apply {{territory_filter}} as a post-fetch firmographic gate via `company_firmographic` instead.
3. **Per-account intent detail (current + historical)** — for each surfaced domain, call `company_intent` TWICE: (a) current window with default `start_date`/`end_date` to capture today's score; (b) prior window with `start_date: today-60`, `end_date: today-30` for the same topic_ids. Post-fetch filter `topics[]` for the resolved `topic_id`s on both. Keep accounts where current score ≥{{score_threshold}} AND prior-window score was below {{score_threshold}} (the "newly crossed" cut). If the prior-window call returns no rows for the topic, treat as inconclusive (drop or move to Watch).
4. **Stage calibration** — note `buyers_journey` per row: `"Evaluating"` / `"Purchasing"` rows lead; `"Researching"` rows go to the watch list, not the action list.
5. **Function hint** — `company_fai` once per surviving account to suggest the buying-function contact via `contact_search` titles only (no enrichment in this workflow — it's a triage step, not a contact-list build).
## Output Format
- `# 📈 Intent Spike Triage — accounts that just crossed the line`
- `## Action list` — table: rank | domain | topic_name | buyers_journey | score (and Δ vs 30d ago) | suggested function | default opening angle
- `## Watch list` — `"Researching"`-stage rows (corroborate but don't lead)
- Per-row citation: `[company_intent]` for score, `[intent_category]` for category, `[company_fai]` for function
## Quality Checklist
- Every Action-list row is `buyers_journey: "Evaluating"` or `"Purchasing"` — `"Researching"` rows ALWAYS go to Watch
- "Newly crossed" check confirms the topic was below threshold ≤30 days ago, not just at-threshold now
- Topic-absence is inconclusive (not "no intent") — fall back to `intent_category` per the skill
- No contact enrichment in this workflow (its role is triage, not contact-list building)