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

# Hiring signals

> Ask your agent to qualify hiring evidence before routing an account.

[Agent guide: CLI and SDK instructions →](/docs/plays/signal-hiring)

## 1. Have your context ready

Have target companies, job families or roles of interest, freshness rules, and the allowed review action.

## 2. Ask your agent

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

```deepline-prompt theme={null}
/deepline-gtm Review hiring signals with Deepline for these accounts. Preserve the job posting source, observed date, company identity, and actual role requirements. Check freshness and my relevance rules. Distinguish a current posting from a filled, duplicate, or uncertain role. Return a reviewable account signal and proposed next question. Do not claim the company uses a technology solely because the posting mentions 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 signal is supported by the actual role and source. A job posting is evidence of a stated requirement, not proof of internal infrastructure or purchasing intent.

Ask your agent:

```deepline-prompt theme={null}
/deepline-gtm 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.

## Check your understanding

Does a job posting prove that a particular team has purchased or selected software?

> **Show the answer**
>
> No. It supplies evidence of a posted role under that source. Software
> selection needs additional evidence.

## Related guides

* [Signal playbooks](/docs/human/plays/signal-playbooks)
* [Deal risk review](/docs/human/plays/signal-deal-risk)
* [Champion tracking](/docs/human/plays/signal-champion-tracking)
* [Fundraising signals](/docs/human/plays/signal-fundraising)


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