> ## 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.

# Signals Agent

> Create signals just by describing them, or build them yourself for greater control.

Every deal starts with a signal: a prospect visits your pricing page, an account posts a job listing, or a champion moves to a new company.

Our **Signals Agent** lets you define the signals that matter the most to your business, and then monitors them for you around the clock. Ultimately, that means we cut through the noise for you, so that your team can focus on the right relationships while intent is fresh.

## Signal types

Avina supports a range of signal types, each designed to capture a different dimension of intent.

<CardGroup cols={2}>
  <Card icon="sparkles" title="AI Signals" href="/signals/custom-ai-signals">
    Describe exactly what you're looking for, and have our agent generate the perfect signal for you.
  </Card>

  <Card icon="globe" title="Web Visits" href="/signals/web-signals">
    Identify people that visit your website. Block out the noise by filtering on session times and number of pages visited.
  </Card>

  <Card icon="user-plus" title="New Hires" href="/signals/new-hire-signals">
    Find recent hires in any role, industry, or location.
  </Card>

  <Card icon="briefcase" title="Job Postings" href="/signals/job-posting-signals">
    Surface listings with specific titles, keywords, locations, or industries.
  </Card>

  <Card icon="crown" title="Champion Movement" href="/signals/champion-signals">
    Get notified whenever a key contact from a previous deal moves to a new company.
  </Card>

  <Card icon="megaphone" title="Social & News" href="/signals/social-news-signals">
    Monitor social posts, funding announcements, product launches, and events.
  </Card>

  <Card icon="mailbox-flag-up" title="Ad Engagement" href="/signals/ad-engagement-signals">
    Keep track of people engaging with your paid advertising campaigns.
  </Card>

  <Card icon="flower" title="Re-engagement" href="/signals/reengagement-signals">
    Find accounts that engage with you following a period of inactivity.
  </Card>

  <Card icon="send" title="Outbound Engagement" href="/signals/outbound-signals">
    Attribute post-outbound website activity when email pixels fail.
  </Card>

  <Card icon="zap" title="Third-Party Signals" href="/signals/third-party-slack-signals">
    Generate signals from the output of any Slack integration.
  </Card>
</CardGroup>

### Which engagement signal should I use?

Web Visits, Ad Engagement, Outbound Engagement, and Re-engagement all fire on "someone interacted with us" — but they answer different questions:

| Signal                                           | Triggers when…                                                     | Use when you want to…                                 |
| ------------------------------------------------ | ------------------------------------------------------------------ | ----------------------------------------------------- |
| [Web Visits](/signals/web-signals)               | An ICP prospect browses your site                                  | Act on fresh, first-party intent regardless of source |
| [Ad Engagement](/signals/ad-engagement-signals)  | An ICP prospect clicks one of your ads                             | Tie specific ad campaigns to pipeline                 |
| [Outbound Engagement](/signals/outbound-signals) | A prospect visits your site shortly after receiving outbound email | Recover attribution when email pixels are blocked     |
| [Re-engagement](/signals/reengagement-signals)   | A stalled/dormant account starts engaging again                    | Revive closed-lost deals or quiet pipeline            |

Signals can overlap (e.g., a re-engagement can also be a web visit) — Avina emits all applicable tags so your automations can target whichever angle matters most.

***

## Creating your first signal

You can get started with signals *with* or *without* the help of our agent. Either way, the details are always under your control.

### Create with AI

The easiest way to get from idea to signal.

<Steps>
  <Step title="Open the signal creator">
    Navigate to **Signals** and click **Create with AI**.
  </Step>

  <Step title="Describe your signal">
    Type out a description of the buying signal you want to track. Be as specific as possible: the more context you give, the better results you get.

    <Tip>
      **Good examples**

      *Recently hired CTOs at fintech companies with 50–200 employees*

      *Companies posting job listings for AI/ML engineers*

      *Startups that raised funding in the last 30 days*

      *Accounts that recently adopted HubSpot as their CRM*
    </Tip>
  </Step>

  <Step title="Review the signal's configuration">
    Avina's agent will analyze your request, select the best signal type, and populate the right filters. You'll be taken to a configuration page where you can review and adjust anything before going live.

    If the agent has any feedback on your prompt, you'll see it highlighted on this screen.
  </Step>
</Steps>

Once your signal's configuration looks right, continue to [Preview & activate](#preview--activate).

### Create manually

If you prefer a greater degree of control, you can build a signal from scratch by selecting the type and filters that matter most to you and your team.

<Steps>
  <Step title="Open the signal creator">
    Navigate to **Signals** and click **Create Manually**.
  </Step>

  <Step title="Choose a signal type">
    In the left panel, select a signal type from the dropdown. Hover over any option for details.
  </Step>

  <Step title="Define your filters">
    Once you've selected a type, applicable filters will appear onscreen for you to fill out.

    <Note>
      Your signal won't be able to be previewed or activated until all required fields are filled in.
    </Note>
  </Step>
</Steps>

Once your filters are in place, continue to [Preview & activate](#preview--activate).

***

## Preview & activate

Whether you built your signal with AI or manually, the final three steps are the same.

<Steps>
  <Step title="Preview your signal">
    Click the **Preview** button in the top-right corner to see a live preview of signals that match your configuration. This lets you validate that your signal is capturing the right intent before activating it.
  </Step>

  <Step title="Activate your signal">
    When you're ready, click **Activate Signal**.

    <Tip>
      **Signals may take a while to appear as alerts**

      When you click **Preview**, a number of important steps (such as ICP grading) are skipped to give you a quick sense of the breadth of intent described by your signal. Your **Feed** is built with a lot more care and intention, and so may take a bit longer to start receiving new intent. We promise, it's worth the wait!
    </Tip>
  </Step>

  <Step title="Choose what happens next">
    After activation, a guided modal asks what should happen when Avina identifies a new prospect from this signal. See [Post-activation: next steps](#post-activation-next-steps) for the available options.
  </Step>
</Steps>

***

## Post-activation: next steps

After activating a signal, a guided modal asks: **"When Avina identifies a new prospect from this signal, what should happen next?"** Pick one of the following options:

* **Launch AI Outreach:** create an [AI Sequence](/features/ai-sequences) that drafts and sends personalized emails to prospects from this signal.
* **Trigger an Existing Sequence:** enroll prospects into an outreach sequence you've already built in your sending platform.
* **Send to a Webhook:** push signal and lead data to external tools like Clay, Zapier, or your own systems.
* **Add to a CRM List:** sync prospects to a list or segment in your CRM for campaigns, ad audiences, and more.
* **Skip for now:** you can always configure actions later from the [Automations](/features/automations) page.

Each option (except Skip) creates an [automation](/features/automations) pre-configured with this signal as the trigger. You'll be taken to the automation builder to finish setting up the destination details.

***

## AI Qualification

<Tip>
  As a rule of thumb: if a filter already exists for something, use it; it's faster and more precise!
</Tip>

Many signal types support an optional **qualification** step. Use this field to describe requirements that can't easily be captured by other filters, e.g. "Series B companies" or "Companies with 50–200 employees." This allows Avina's agent to evaluate each potential signal against any number of freeform criteria before delivering them to your team.

See the [Qualification Agent](/features/ai-qualification-agent) for how signals are evaluated against your ICP and freeform requirements.

***

## Notifications

By default, Avina alerts you of incoming intent through the channel associated with your [Slack integration](/integrations/slack/overview). To route a signal to a specific channel, take the following steps:

1. Visit your signal's configuration page and click the <Icon icon="bell-ring" /> in the top-right corner of the window.
2. Type in the name of the channel that you'd like to receive alerts in.
3. Click **Save**.