signal-based-outreach

name

signal-based-outreach

description

Surface buying signals from real customer conversations, deal activity, and pipeline data in Unabyss — then turn each signal into a specific, timely outreach trigger. Use this skill whenever the user wants to know who to reach out to right now, what signals are worth acting on, which prospects have gone warm, or wants to build signal-based outreach sequences. Also trigger when someone asks about intent data, outbound triggers, or who to prioritize in sales.

Signal-Based Outreach

Instead of manually defining buying signals or importing intent data, Unabyss surfaces them from what's already happening — customer conversations, deal activity, job changes, product usage signals, and sales call patterns. Each signal becomes a specific outreach trigger with a suggested message.

Required Integrations

This skill uses Unabyss MCP — agentic_query for signal mining, query for specific account history.

If Unabyss is not connected, tell the user: "This skill requires Unabyss MCP. You can connect it from the Tools menu."

---

What Counts as a Signal

A signal is any event or pattern that suggests a prospect or customer is more likely to engage, buy, expand, or churn right now than they were last week. Good signals are specific, recent, and tied to a real event — not just "they visited our website."

Signal types to look for:

• Pipeline signals — deals that have gone quiet, prospects who asked a question but never got followed up, demos that happened but no next step was set
• Customer expansion signals — active customers hitting usage limits, asking about features they don't have, or mentioning new team members or use cases
• Timing signals — prospects who said "not now" and a relevant time period has passed, companies that just raised funding, new hires in relevant roles
• Conversation signals — someone mentioned a pain in a call that was never addressed, a competitor was mentioned, or a specific trigger word appeared ("frustrated", "evaluating", "switching")
• Re-engagement signals — cold contacts who recently engaged with content, replied to something, or were mentioned in a warm thread

---

How to Run

Step 1 — Mine signals with agentic_query

Look across all connected sources for signals that suggest a prospect, lead, or customer is worth reaching out to right now. Find:

- Deals or conversations that stalled without resolution — who, when, what was last discussed
- Prospects who expressed interest but were never followed up with
- Customers showing expansion signals — hitting limits, asking about new features, mentioning new use cases
- Anyone who said "not now" or "check back later" where that time has likely passed
- Sales calls where a pain point was raised but never addressed in follow-up
- Any recent event that makes a previously cold contact newly relevant — funding, new hire, role change, competitor mention

For each signal: who it involves, what the signal is, when it happened, and why it suggests now is the right time to reach out.

Call agentic_query_read to retrieve results.

Step 2 — For each signal, pull account history with query

For the top signals, run a quick query per account:

What's the full history with [name / company]? All interactions, what was said, what was promised, what they told us about their situation.

Step 3 — Produce the outreach triggers

For each signal, produce one trigger card:

---

Signal: [Account Name] Signal type: [Pipeline stall / Expansion / Timing / Conversation / Re-engagement] What happened: One sentence describing the signal and when. Why now: Why this makes today a good time to reach out. Suggested message: A specific, 3–5 sentence outreach message grounded in the signal — not generic. References what was discussed, what changed, or what was left unresolved. Channel: Email / Slack / LinkedIn — whichever fits the prior relationship.

---

Present all trigger cards ranked by signal strength — strongest first.

Step 4 — Offer to build a sequence

For the top 2–3 signals, offer to extend into a 3-step follow-up sequence if the first message goes unanswered.

---

Output Rules

• Use agentic_query for signal mining, query for individual account history — not both with agentic_query
• Every suggested message must reference the specific signal — no generic "just checking in"
• If Unabyss surfaces no signals, say so clearly — don't invent activity
• Cap the output at 10 trigger cards — if more exist, ask which accounts to prioritize
• No preamble before the first trigger card