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

# What to do with identified visitors

> Choose a practical workflow for Leadpipe instead of letting the data sit idle

## Start with one clear use case

Leadpipe works best when you decide what should happen after identification.

The simplest approach is to start with one use case, one owner, and one destination.

## The three cleanest starting plays

<Columns cols={3}>
  <Card title="Sales play" icon="briefcase" href="/guides/sales-play">
    Route qualified visitors to a CRM, queue, or rep workflow.
  </Card>

  <Card title="Ads play" icon="megaphone" href="/guides/ads-play">
    Use high-fit traffic to improve retargeting and audience-building workflows.
  </Card>

  <Card title="Lifecycle email play" icon="mail" href="/guides/lifecycle-email-play">
    Send filtered visitors into email or outbound systems that already have a follow-up motion.
  </Card>
</Columns>

## Common use cases by team

| Team             | Good first use case                             | What success looks like                                     |
| ---------------- | ----------------------------------------------- | ----------------------------------------------------------- |
| Sales            | Send high-fit visitors to a CRM or Slack        | Reps can act on recent, relevant traffic quickly            |
| Marketing        | Build better retargeting or follow-up audiences | Better audience quality and clearer campaign prioritization |
| Founder-led team | Review a narrow saved view every day            | Fast manual follow-up on the best traffic                   |
| RevOps or ops    | Route filtered visitors into existing systems   | Cleaner handoff and better workflow consistency             |
| Agency           | Build one repeatable client workflow            | Clear reporting and one obvious next step for the client    |

## How to choose the right first play

<AccordionGroup>
  <Accordion title="Choose sales first">
    Pick this when your team already works leads in a CRM and can act quickly on named visitors.
  </Accordion>

  <Accordion title="Choose ads first">
    Pick this when paid media is important and you want to recover value from traffic that would otherwise disappear.
  </Accordion>

  <Accordion title="Choose lifecycle email first">
    Pick this when your team already has an email or outbound process and just needs better inputs.
  </Accordion>
</AccordionGroup>

## A simple workflow to put in place

Every Leadpipe workflow should answer five questions clearly:

1. Which traffic should count as useful?
2. Who owns the next step?
3. Where should the data go?
4. How fast should the team act?
5. What metric proves the workflow is working?

## A good first workflow is narrow

Start with one narrow slice:

* one pixel or domain
* one ideal customer profile
* one saved view or segment
* one destination
* one owner

That is usually enough to prove value without creating operational noise.

## Good first workflows

* Send pricing-page visitors from target industries to your CRM
* Send high-intent visitors from one pixel to Slack
* Export a saved view for founder-led outreach
* Route one segment into your email or outbound tool
* Build one client-facing report around identified visitor activity

## Next steps

* Read [Integrations and delivery options](/guides/integrations-and-delivery-options) to decide how data should leave Leadpipe.
* Read [Trial success guide](/guides/trial-success-guide) to measure the rollout properly.