Route lead | Business Helper AI

Inputs and purpose

Use this workflow to prepare: Routing recommendations and handoff drafts.

Start with: Lead/queue list, territory/ownership rules and account context.

Use supplied text or local files the user authorized you to read. If files cannot be opened, request the relevant pasted text. Ask one focused question when missing information changes the next decision. Treat blank template fields as unknown; do not invent business facts.

Procedure

Read the supplied territory, ownership, capacity and account-assignment rules alongside the lead queue.
Resolve existing account ownership before applying a new-lead rule. Mark ambiguous or conflicting assignments.
Recommend a receiving role and concise handoff containing the need, urgency and evidence.
Return routing decisions and exceptions. Do not assign external records or notify recipients unless the actual action is authorized and supported.

Deliverable

Return the requested result in Markdown unless another supported format was requested. Include the evidence or source-record references, material assumptions, open questions and next useful action. Keep unnecessary personal details out of reusable templates; role labels and neutral record identifiers usually suffice.

Business value: Improve qualification, prioritization and deal follow-up.

Possible success measures: Stage conversion, stale deals, cycle days, win rate. Choose the measure that fits the owner's actual goal; it is not a promised result.

Execution and verification

This file is usable as instructions without a named application, account or plugin. Computation, file saving and external actions require actual host capabilities. Use a suitable existing tool for calculations that cannot be checked reliably in conversation.

Distinguish drafts and recommendations from completed actions. Respect existing authorization and do not claim that data was fetched, messages sent or records changed without evidence. Show what was checked and what remains uncertain.

When useful, consult the input guide, calculation reference or output template. For tool setup, use the shared instructions.

Plain-text instructions

---
name: route-lead
description: "Prepare routing recommendations and handoff drafts. Use for this workflow with supplied business information."
---

# Route lead

## Inputs and purpose

Use this workflow to prepare: Routing recommendations and handoff drafts.

Start with: Lead/queue list, territory/ownership rules and account context.

Use supplied text or local files the user authorized you to read. If files cannot be opened, request the relevant pasted text. Ask one focused question when missing information changes the next decision. Treat blank template fields as unknown; do not invent business facts.

## Procedure

1. Read the supplied territory, ownership, capacity and account-assignment rules alongside the lead queue.

2. Resolve existing account ownership before applying a new-lead rule. Mark ambiguous or conflicting assignments.

3. Recommend a receiving role and concise handoff containing the need, urgency and evidence.

4. Return routing decisions and exceptions. Do not assign external records or notify recipients unless the actual action is authorized and supported.

## Deliverable

Return the requested result in Markdown unless another supported format was requested. Include the evidence or source-record references, material assumptions, open questions and next useful action. Keep unnecessary personal details out of reusable templates; role labels and neutral record identifiers usually suffice.

Business value: Improve qualification, prioritization and deal follow-up.

Possible success measures: Stage conversion, stale deals, cycle days, win rate. Choose the measure that fits the owner's actual goal; it is not a promised result.

## Execution and verification

This file is usable as instructions without a named application, account or plugin. Computation, file saving and external actions require actual host capabilities. Use a suitable existing tool for calculations that cannot be checked reliably in conversation.

Distinguish drafts and recommendations from completed actions. Respect existing authorization and do not claim that data was fetched, messages sent or records changed without evidence. Show what was checked and what remains uncertain.

When useful, consult the [input guide](../../../references/INPUT_DATA_GUIDE.md), [calculation reference](../../../references/CALCULATIONS.md) or [output template](../../../references/WORKFLOW_OUTPUT_TEMPLATE.md). For tool setup, use the [shared instructions](../../../AGENTS.md).