Intent-Surge Campaign Trigger

Detect the accounts whose category intent is high and trending up right now and trigger a fast-response campaign — the window is open now, not next quarter.

Demand Gen - Intent surge

The accounts whose intent just surged — campaign them while the window is open

29
Accounts surging
A surge is a window
High, trending-up category intent.
Fast response, not next-quarter drip.
AccountSurgeFirst touch
AcmeScore 95, trend upTiming-aware opener
BetaScore 91, seen 3d agoPain-led opener
GammaEvaluating nowFast response
Why it lands
Steady-state high intent is interesting; a high score that is trending up and seen this fortnight is a buying window. This finds the surges and fires a fast-response campaign while the buyer is actively shopping — not a quarter later.

Overview

Identify accounts whose HG intent on a category is high, trending up and recent (a buying-window signal) and assemble a fast-response campaign target list with the personas and a recommended first touch — so demand gen acts on the surge while the window is open.

Use cases

  • Catch the buying window

    Intent surges decay. A campaign that responds in days while the account is actively researching wins where a monthly batch-and-blast misses entirely.

  • Tasteful timing references

    The opener references the timing without saying 'we tracked your searches' — surge-aware but not creepy, which is the difference between a reply and a block.

View workflow prompt
# Intent-Surge Campaign Trigger

## Parameters

- `{{category}}` *(required)* — The category to monitor for intent surges. Example: `data integration`
- `{{target_segment}}` *(required)* — Segment to scope the surge scan. Example: `US mid-market, 200-2000 employees`
- `{{offer}}` *(required)* — The offer to respond with. Example: `managed data-integration platform`

## Purpose
Find {{target_segment}} accounts showing a {{category}} intent surge (a high score with a positive topic trend, seen in the last 2-4 weeks) and assemble a fast-response campaign for {{offer}} — because a surge is a buying window that closes, and a campaign that fires next quarter misses it.

## Process
1. **Detect surges** — resolve {{category}} to topic IDs with `list_intent_topics` (short keyword in `name`), then `search_companies` with `intent.topics: { ids, inclusion_method: "ANY_PRESENT" }` and `intent.signal_score: "HIGH"` for the candidate pool; for each candidate, `company_intent` with `topic_ids`, `fields: ["topics"]`, `granularity: "global"` and a recent `signal_date` window. Count an account as surging only when the topic score is high, its `trend` is positive and `last_seen_at` falls in the last 2-4 weeks (not just high steady-state intent). The tools return the current score and trend, not a week-by-week history, so do not quote percentage rises over a period.
2. **Scope to segment** — `company_firmographic` to confirm {{target_segment}} fit; drop misses.
3. **Find responders** — `contact_search` for the relevant personas at each surging account.
4. **First touch** — draft a surge-aware opening line per account that references the timing without being creepy about the data (per opening-line-discipline).
5. **Sequence the response** — recommend the channel + cadence for a fast-response motion (the surge decays, so speed matters).

## Output Format
Markdown with:
- `# Intent-Surge Campaign — {{category}}`
- `## Surging Accounts` (ranked by score, topic trend and recency)
- `## Responders` (personas per account)
- `## First-Touch Openers` (one per top account)
- `## Response Cadence` (channels + timing)
- `## Citations`

## Quality Checklist
- Surge detection distinguishes recent rise from steady-state high intent
- Score, trend and recency cite `company_intent`
- Openers reference timing tastefully, not 'we saw you searching'
- Cadence reflects that surges decay (fast response)