Skip to main content
Human guide: work with your agent → Test a routing decision table before connecting it to live writes. Keep ambiguous or ineligible leads in an explicit exception path.

​
Before you start

Use an authorized workspace and a small file with stable source IDs. Have source access and your team’s acceptance policy available. This guide describes customer-authored logic, not an automatically enabled product policy.

​
1. Understand the decision

Routing applies business policy to accepted identity and qualification evidence. Enrichment does not define territories or commercial ownership. Test this fictional sample before calling providers:

​
2. Inspect supported operations

Inspect a returned ID with deepline describe <returned-id> --json. Compare required identifiers, outputs, access mode, and price. A similar title does not establish that a contract fits.

​
3. Implement the bounded workflow

Ask your agent to author inbound-lead-routing.play.ts using Write Plays. Have it declare the CSV input and preserve source IDs. Reuse existing contracts when they fit the transformation. Implement these rules explicitly:
  1. Define eligibility, territory rules, fallback behavior, and protected ownership.
  2. Resolve person and account identity before evaluating routing inputs.
  3. Return the proposed owner and exact rule reason. Keep unknown inputs unresolved.
  4. Test repeated events and conflicting ownership before enabling destination writes.
Keep external changes disabled for the first pilot. That control belongs in the authored logic, not a universal Play dry-run flag.

​
4. Check and pilot

Prepare pilot.csv using CSV-safe selection. Then check the source:
Resolve authoring errors first. After reviewing source and price, run only the pilot:
Use the ID returned by the pilot. Select a returned dataset path when several exist. Provider-backed execution can incur usage.

​
5. Verify the outcome

Compare proposed owners with a labeled decision table. Count unresolved leads separately from assignments and request failures.
Every source ID has a result or explicit exception. The fictional cases follow the stated policy, and actual results retain their evidence.
Ask your agent why a record was accepted, held, or rejected. Correct the rule before expanding input or enabling external writes.

​
Continue

HubSpot routing applies the boundary to a CRM. Governance explains authority.