Your First Signal¶
This guide walks through what happens when a partner co-sell signal fires — what it means, where it appears, and the recommended response workflow.
What Is a Signal?¶
A signal is an event detected in your partner ecosystem that indicates co-sell opportunity or risk. PartnerSignals monitors three layers of activity:
| Signal Type | What It Detects |
|---|---|
| Co-Sell Signal | A partner has an active relationship with one of your open opportunities |
| Overlap Signal | A partner account overlaps with your prospect — identified via Crossbeam or ecosystem data |
| Pre-Intent Signal | Early-stage buying indicators (research activity, product evaluation patterns) tied to a partner account |
Where Signals Appear¶
Signals surface in three places depending on your routing configuration:
- Signal Feed — the main view at eco.partnersignals.ai, updated in real time
- Slack — posted to your configured channel (e.g.
#partner-signals) with action links - CRM — as tasks or activity records on the relevant Opportunity or Account
Anatomy of a Signal¶
Each signal card shows:
Signal Type: Co-Sell — Active Partner Relationship
Account: Acme Corp (Salesforce ID: 001Xx000003GYwI)
Partner: CloudCo (Solution Provider)
Opportunity: Acme Corp Q3 Expansion — $240,000
Partner Touch: Intro call logged 2 days ago
Attribution: Co-Sell (estimated 35% weight)
Recommended: Sync with CloudCo rep this week
Fields explained:
- Signal Type — classification of the detected event (see table above)
- Account / Opportunity — the customer record this signal is tied to
- Partner — which partner triggered the signal, with their partner type
- Partner Touch — the specific activity detected (logged call, email thread, meeting)
- Attribution — estimated co-sell attribution weight if this deal closes
- Recommended — suggested next action based on signal type and deal stage
Responding to a Signal¶
Option 1 — Act Directly in the Portal¶
- Click the signal card to open the detail view
- Review the full timeline of partner activity on this account
- Click Log Action to record your response (sync scheduled, intro requested, etc.)
- The signal moves to In Progress state
Option 2 — Via Slack¶
If you have Slack routing configured, each signal includes action buttons:
- View Details — opens the portal signal detail page
- Mark Handled — closes the signal without logging a specific action
- Request Intro — queues a partner intro request (routed to your partner manager)
Option 3 — Via CRM Task¶
If CRM task creation is enabled, a task is auto-created on the Opportunity record with the signal summary and a link back to the portal for full detail.
Signal States¶
| State | Meaning |
|---|---|
| New | Signal fired, no action taken yet |
| In Progress | Action logged, follow-up pending |
| Handled | Closed with a logged outcome |
| Expired | Signal aged out (configurable window, default 14 days) |
What's Next¶
- Attribution Setup — configure how signals translate to revenue credit
- Partner Portal Guide — full reference for all portal workflows
- Slack Integration — set up signal notifications in Slack