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

# Route inbound leads with explicit exceptions

> Ask your agent to route inbound leads with a visible exception queue.

[Agent guide: CLI and SDK instructions →](/docs/guides/inbound-lead-routing)

## 1. Have your context ready

Have example inbound events, target destinations, territory rules, suppression rules, and the approval boundary.

## 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 Prepare inbound routing with Deepline for these sample leads. Preserve event and lead identity. Resolve only the fields the routing decision needs, using inspected sources. Apply explicit territory, eligibility, and suppression rules. Return the proposed destination and supporting reason for each lead, with missing or conflicting cases held for review. Do not enable live routing or external writes yet.
```

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

Each lead is assigned under a documented rule or retained as an exception. A failed enrichment request is not silently treated as a low-fit lead.

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 missing geography justify choosing whichever territory rule runs first?

> **Show the answer**
>
> No. Apply the documented fallback or hold. Implementation order is not a
> routing policy.

## Related guides

* [Write Plays](/docs/human/sdk-v2/plays)
* [Batch CSV enrichment](/docs/human/sdk-v2/batch-csv)
* [Route HubSpot leads with verified owner IDs](/docs/human/guides/hubspot-lead-routing)
* [CRM field ownership and write authority](/docs/guides/crm-data-governance)


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