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

# Research accounts before outreach

> Ask your agent to research accounts with evidence for a specific decision.

[Agent guide: CLI and SDK instructions →](/docs/recipes/research-workflow)

## 1. Have your context ready

Provide account identifiers, the question you need answered, required sources, and what counts as current evidence.

## 2. Ask your agent

Paste this into your agent, then provide your task and example inputs when it asks:

```deepline-prompt theme={null}
/deepline-research Build a Deepline account-research workflow for this decision. Inspect existing research Plays and sources before choosing a maintained route or custom workflow. Define the research questions, evidence fields, source dates, and unresolved outcomes. Propose a representative pilot with external activation disabled. Show what a reviewer will see and the expected usage before running it.
```

Complete any requested sign-in yourself. Give the agent the missing information before approving execution. Provider-backed work can incur usage.

## 3. Review the result

The research answers the stated questions with retrievable evidence. Unsupported claims remain open questions, and the saved result preserves account identity.

Ask your agent:

```deepline-prompt theme={null}
/deepline-research Compare the result with the acceptance rule we agreed. Show the evidence for accepted and rejected outcomes, unresolved questions, and recorded Deepline usage where work ran. If work is still running or a response is uncertain, inspect the original saved execution before proposing another request. Explain the next decision I need to make.
```

Approve a larger job, recurring work, or external changes only after reviewing that decision.

## Turn the findings into a workflow

If the research answers your question, keep the cited report. If you need a repeatable workflow, carry the reviewed findings into execution:

```deepline-prompt theme={null}
/deepline-gtm Use the reviewed research findings and source plan from this conversation to implement the agreed workflow. Preserve the evidence, source limitations, and acceptance rules. Reuse retained results where appropriate. Explain remaining gaps and propose a bounded pilot before starting additional provider work. Do not repeat source discovery without a specific unresolved question.
```

If the next step is to define or evaluate an account score, use [the scoring guide](/docs/human/guides/account-scoring-workflows) before implementation.

## Check your understanding

Can a missing source response be rewritten as a confident claim that the account has no relevant event?

> **Show the answer**
>
> No. Preserve the source failure or missing evidence. Lack of a retrieved
> result is not proof of absence.

## Related guides

* [Competitive and ad intelligence](/docs/human/plays/play-ad-intelligence)
* [Warm outbound automation](/docs/human/recipes/warm-outbound-web-intent)
* [Build a paid ads audience](/docs/human/ads-audiences)
* [Query Database](/docs/human/database-access)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.