The intent surge response playbook
Last updated July 20, 2026
The intent surge response playbook is run by SDRs and ABM teams the moment an intent tool flags a target account surging on your category. The trigger is the spike, and the entire play is a race: the list goes to B2BMail within 48 hours of the alert and the FedEx envelope lands on the decision-maker's desk while the account is still researching.
To be clear about the mechanics: there is no integration between intent platforms and B2BMail. The intent tool surfaces the account; a rep builds the contact list for that account's buying committee and uploads it. That manual step takes minutes, and it is the only step between a surge alert and a tracked envelope in the FedEx network.
Key takeaways
- The trigger is a named target account crossing your intent tool's surge threshold — not any account, anywhere, showing any activity.
- Speed is the whole play: upload the list within 48 hours so the envelope arrives while the account is still researching.
- Address verification runs before anything prints, so a rushed list never turns into envelopes that can't land.
- The delivery call happens the same day the tracking dashboard confirms the envelope is on the desk.
- The letter never mentions the intent data — the timing does the work while the signal stays invisible.
Who runs it, and when
The SDR or BDR who owns the account runs this play, sometimes with an ABM marketer supplying the surge alerts and the materials. It only fires on accounts that were already on your target list. A surge from a company you would never sell to is not a trigger; it's noise. The qualification test is two questions: is this account on our list, and does the surge topic map to what we actually sell? If a target account is suddenly researching your category — or a competitor's brand — the clock starts.
Run it as a standing motion, not a campaign. Most weeks it fires on a handful of accounts; some weeks on none. That irregularity is fine. The play's value is being physically present inside a real buying window instead of discovering it in next quarter's closed-lost notes. Why intent signals pair unusually well with physical mail is covered at /answers/intent-data-and-direct-mail — this page assumes that case and focuses on execution.
The cadence
The clock starts on the spike day, but the table is keyed to D0 — the day FedEx confirms delivery. Everything before D0 is compression: from alert to uploaded list in under 48 hours.
| Day | Channel | Move |
|---|---|---|
| D-4 | Intent tool | Spike detected: a named target account crosses your surge threshold on your category or a competitor term. |
| D-4 | — | Rep qualifies the surge and builds the contact list — the two or three buying-committee members who'd own this purchase. |
| D-3 | — | List uploaded to B2BMail. Addresses verified before print; any contact without a deliverable address is flagged, not mailed. |
| D-3 | Light relevance touch to the primary contact — a useful point on the surge topic, no pitch, no mention of mail. | |
| D-2 | Connect with the senior contacts. No pitch in the note. | |
| D-1 | — | Envelopes ship FedEx Priority. Tracking IDs appear in the dashboard. |
| D0 | — | Envelope lands (tracking dashboard confirms delivery to each contact). |
| D0 | Phone | The delivery call — within hours of confirmed delivery, while the envelope is still on the desk. |
| D+1 | Reference the letter by its physical fact ('the FedEx envelope on your desk') and repeat the single ask. | |
| D+3 | Phone | Second call attempt. Voicemail references the letter, not the pitch. |
| D+5 | One proof point from the enclosed one-pager, two sentences, same ask. | |
| D+8 | Close the loop. No response means the account returns to normal cadence until the next surge. |
What to send
Send the meeting-request letter at /templates/meeting-request-letter, with a one-pager built from /templates/sales-one-pager as the enclosure. The letter should be about the problem the account is evidently researching — but written as if the timing were a coincidence. Never write anything that implies you watched them research: no 'I noticed your team has been evaluating,' no 'companies looking at this space right now.' Intent data buys you timing. Revealing it buys you distrust.
Keep the letter under 250 words with one ask. The enclosure carries the proof; the letter carries the reason to meet.
The delivery call
The dashboard tells you the envelope landed this morning. The call runs on that fact, not on a pitch. A skeleton:
"Hi [First name] — [Your name] at [Your company]. I sent you a FedEx envelope that landed this morning — a short letter about [the problem]. Has it reached your desk?" If yes: "The one thing I'd add to it: [single sharpest point]. Worth 20 minutes to see whether it applies to [their company]?" If no: "It'll be the FedEx envelope with my name on it. There's one specific idea in it about [problem] — I'll follow up by email so I'm easy to find."
The call is short on purpose. The letter did the arguing; the call converts attention into a slot on the calendar.
KPIs and failure modes
Track speed and conversion, qualitatively and honestly: time from surge alert to uploaded list (the 48-hour test), the share of qualified surges that got an envelope at all, delivery-call connect rate, and meetings booked per surge cycle. Because every envelope has its own FedEx tracking ID, there's no ambiguity about which surging accounts received one and when.
Three failure modes recur. First, chasing every spike: surges on poor-fit accounts burn budget and train the team to ignore the play. Second, letters that reveal the intent data — they read as surveillance and poison the account. Third, slowness: a list built a week after the alert produces an ordinary cold touch, because the research window has already closed.
Frequently asked questions
How fast can the envelope actually arrive after an intent alert?
The rep's list-building is the variable — the rest is fast. Once the list is uploaded, B2BMail verifies each address, prints, and ships FedEx Priority, which moves in days, not weeks. The tracking dashboard shows when each envelope will land and when it does, so the delivery call can be timed to the day.
Should the letter mention that we saw their intent surge?
No. The surge tells you when to send and roughly what to write about; it should never appear in the copy. A letter that arrives at exactly the right moment reads as good instincts. A letter that says 'we noticed your team researching this' reads as monitoring, and buyers punish that.
What if the key contact at the surging account has no verifiable address?
Then that envelope is never printed — B2BMail verifies a deliverable business address for every contact before anything goes to print, and unverifiable contacts are flagged instead of mailed. The rep covers that person digitally while the verified members of the committee get the physical touch.
Land on every prospect's desk
B2BMail puts your message in a FedEx envelope on the desk of every decision-maker at your target accounts — with per-piece tracking and every address verified before it ships.