Intent Targeting — Activation
Yesterday's intent spike, today's call list — names, titles, and the line that lands.
Intent topic → ranked call list with names and opening lines
| Account | Signal | Persona |
|---|---|---|
| Acme Co | AI Observability · 12 days | VP Engineering — Maria S. |
| Beta Industries | LLM Operations · 9 days | Director Platform — Devon K. |
| Gamma Cloud | AI Observability · 21 days | VP Engineering — Priya M. |
Overview
Distinct from intent-spike triage. Converts a chosen intent topic into a prioritized prospecting list with named personas and persona-aware opening lines — the activation flow that turns yesterday's intent spike into today's call list.
Use cases
Monday morning a real call list, not a Salesforce dashboard
Every Monday your SDR team needs to know which 50 accounts to call this week. Today that's a Salesforce report filtered by 'last touch >30d'. With this workflow it's 50 accounts where intent on your category is rising right now, the persona is named, and the opening line is written for them. Less Monday-morning meeting, more Monday-morning calls.
Distinct from triage — this is the activation flow
We already ship `sdr-intent-spike-triage` for grading the *quality* of signals this week. This workflow handles the *what do we do with them* step: turn the topic into a prioritized list with persona-aware openings. The two compose — triage informs which topic to activate against.
View workflow prompt
# Intent Targeting — Activation
## Parameters
- `{{intent_topics}}` *(required)* — JSON array of HG intent topics to activate against. Example: `["AI Observability","LLM Operations"]`
- `{{target_geography}}` *(required)* — Geographic filter. Example: `US`
- `{{target_segment}}` *(required)* — Segment filter — industry + employee band. Example: `mid-market software, 200-2000 employees`
- `{{persona_titles}}` *(required)* — JSON array of titles the activation targets. Example: `["VP Engineering","Director of Platform"]`
## Purpose
Distinct from `sdr-intent-spike-triage` (which grades signal quality this week). This workflow *activates*: takes {{intent_topics}}, filters to {{target_segment}} in {{target_geography}}, finds the {{persona_titles}} at each, and writes a persona-aware opening line per row. Output is a call-ready list.
## Process
1. **Resolve topics** — `intent_category` for each topic in {{intent_topics}}. Confirm the topic exists and pull baseline signal volume.
2. **Active accounts** — surface companies with rising intent on {{intent_topics}} in the last 30 days, filtered to {{target_segment}} in {{target_geography}}. Rank by combined intent score + recency.
3. **Persona mapping** — `contact_search` for {{persona_titles}} at each account. One row per account; up to 2 persona contacts per row.
4. **Firmographic gate** — `company_firmographic` to confirm the segment + geo before ranking. Drop misses.
5. **Persona-aware opening** — for each ranked row, write a one-sentence opening line that names the intent topic + the persona's specific responsibility + the recent signal. The line is the AE's first message.
## Output Format
Markdown with:
- `# Intent Activation — {{intent_topics}}`
- `## Top 50 Ranked Accounts` (table: rank | domain | intent score | recency | top persona)
- `## Persona Roster` (per top-25 row: title + one-sentence opening line)
- `## Citations` (every ranking metric cites the HG tool)
## Quality Checklist
- Every ranking metric sources from `intent_category` or `company_intent`
- Personas are real contacts from `contact_search`, not titles
- Opening line names a dated signal
- No row ranks without a confirmed persona