> ## Documentation Index
> Fetch the complete documentation index at: https://docs.avina.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Third-Party Slack Signals

> Turn alerts from any Slack-connected vendor into Avina signals and automations.

### **What is a Third Party Slack Signal?**

A **Third Party Slack Signal** lets Avina ingest intent or engagement data that another vendor posts directly into a Slack channel you control. For example, if your team receives ZoomInfo Intent alerts in #zoominfo-feed, or G2 Buyer Intent pings in #g2-intent, simply point Avina at that channel. From that moment on, every message that lands there is parsed by Avina’s AI, enriched, scored, and surfaced alongside your other signals, effectively turning **any provider with a Slack feed into a native Avina integration**.

Common sources include ZoomInfo Intent, G2 Buyer Intent, Bombora Company Surge, BuiltWith signal digests, CB Insights events and trends, and even custom webhook bots your RevOps team has built.

### **Why Third Party Slack Signals Matter**

* **One Unified View:** Reps no longer bounce between vendor portals. Every signal appears in Avina's Signals Feed with full context, AI-assisted account research, and AI-drafted outreach.
* **Contextual Scoring:** Any single signal (such as a ZoomInfo intent surge) is more meaningful when Avina layers on recent marketing engagement, open opportunities, and ICP fit analysis to produce an AI-driven account score.
* **Infinite Extensibility:** As long as a provider can post to Slack, you can harness its data in Avina without waiting for roadmap-level integrations.
* **Faster Time-to-Value:** Set-up is minutes, not weeks; no APIs, ETLs, or engineering tickets required.

### **Scenarios for Using Third Party Slack Signals**

* Your intent vendor offers Slack notifications but no robust API.
* Ops wants to prototype a new data source before committing to a long-term integration.
* You need to combine niche signals (e.g., GDPR compliance tech adoption from BuiltWith) with broader intent to refine targeting.
* Field reps live in Slack and already subscribe to multiple vendor channels.

## **Integration & Setup Guide**

1. **Send data to Slack**

   E.g. Configure ZoomInfo to post intent alerts to #zoominfo-feed.
2. **Include rich payloads**

   Each message should contain:

   * **Company name and domain**
   * **Signal description** (e.g., "Topic interest: Revenue Intelligence" or "G2 reviews page view")
   * **Optional:** relevant contacts, emails, titles, or URLs. More data → better summarization and signal scoring.
3. **Tell Avina where to listen**

   In Avina, navigate to **Settings → Signals**, enter the channel name and choose or type the provider name. That's it!

   Need help? Ping the Avina team; that’s it!

Once connected, every new Slack message is:

* **Parsed** by Avina’s AI to extract the signal and related entities.
* Then, like every other signal:
  * **Qualified** based on your ICP fit criteria.
  * **Enriched** with contact information and firmographics, if missing.
  * **Scored** within the full account context.
  * **Routed** to the Signals Feed, Slack alerts, sequences, and your CRM.

## **High-Value Automated Plays**

* **Instant Warm Outbound:** Auto-enroll matching contacts into sequences citing the exact intent topic pulled from the Slack message.
* **Focus Lists in CRM:** Automatically tag accounts with \[ZoomInfo Intent] and prioritize them on rep dashboards.
* **Real-Time Slack Alerts:** Forward high-intensity spikes to AE-specific channels with one-click “Create Task” buttons.
* **Cross-Signal Compound Scoring:** Boost account score weightings when a Third Party Slack Signal lands within 7 days of website pricing-page visits.
* **Ad Audience Sync:** Drop companies into a “High Intent – Third Party” segment for targeted LinkedIn or GDN retargeting.

### **Context-Focused Messaging Examples**

**Email**

In response to a surge in “pipeline forecasting & deal-risk” intent topics:

> *Subject:* Reducing forecast blind spots
>
> Hi \[First Name],
>
> Teams like Acme Robotics cut unknown pipeline by 23 % after blending early intent cues into their CRM. I’ve distilled the playbook into a 2-page brief.
>
> Happy to send it over or walk you through the highlights, whichever’s easier.
>
> Best,
>
> \[Your Name]

### **LinkedIn DM**

In response to an account-level push on \[Initiative] (e.g., new job posts + intent surge):

> Hi \[First Name], noticed \[Company] doubling down on **\[Initiative]** this quarter. I have a one-pager on how peers streamline hand-offs between Marketing Ops and Sales using light automation.
>
> Want a copy (no form fill)? Always up for swapping RevOps notes.

### **SMS / Text**

In response to a Bombora Company Surge, account spiked on “sales forecasting accuracy” research:

> Hi \[First Name]:\[Your Name] here from Avina. Just emailed you a 2-page cheat sheet on shortening discovery cycles in RevOps that I thought could be helpful. Happy to dive in if you want to look at it together!

### **Why Third Party Slack Signals Work**

Combining vendor-level intent with Avina’s holistic account view turns scattered pings into rich, prioritized actions. Teams strike while interest is genuine, armed with complete context, and never miss a hidden surge in demand, no matter where the data originates.

## **CRM Integration Details**

**CRM Activity Tag:** `avina_third_party_slack_signal`