Boring AIBoring AI
Request access
Sales/First-party starter playbook

Inbound lead router

Enrich and route new leads to reps.

// what it does
  1. 01Capture. Take the inbound lead's details from the form or source and normalize the name, email, company, and any message.
  2. 02Enrich from what's available. Pull any existing account or contact context from Salesforce and the workspace knowledge base, and infer segment from the lead's message and email domain. Don't assume an external data-enrichment provider.
  3. 03Score and assign. Apply the scoring/routing rules (territory, segment, round-robin) to pick the owning rep.
  4. 04Record and notify. Create the lead record in Salesforce and notify the assigned rep in Slack with the enriched summary and score.
// guardrails in the draft

Always create the Salesforce record even if context is thin — don't lose a lead over missing details.

De-duplicate against existing contacts/accounts before creating a new record; if a match exists, attach rather than duplicate.

If routing rules are ambiguous or no rep matches, assign to the default queue and flag it, rather than guessing.

Never send outbound messages to the lead themselves; this agent routes internally only.

Before you publish this playbook

Playbook updated

Define ownership before enriching a lead

This starter uses Salesforce and Slack to route an inbound lead internally. It is suited to teams that already have territory, segment, or assignment rules but spend time applying them to inconsistent submissions. Gather those rules, the default queue, and the fields required for a useful Salesforce record. Decide how an existing contact or account should be handled before allowing a new record to be created.

The template uses available Salesforce context and workspace knowledge. It does not promise an external enrichment provider or verified information that is absent from those sources. Keep inferred context distinguishable from supplied facts. If your CRM is HubSpot, adapting this Salesforce draft requires reviewing the actions, fields, and matching rules; changing the integration name alone is not a working migration.

Evaluate assignment and duplicate handling

Test a lead with complete information, one with a personal email address, an existing contact, and a submission that matches no territory. Check whether the intended representative receives the Slack summary and whether the Salesforce record preserves the useful source details. For an ambiguous route, the expected result is the default queue plus a visible flag, not a confident guess about ownership.

This playbook does not contact the lead. Keep outbound messages outside the trial and review the CRM write permissions separately from Slack notifications. Success means the lead is accounted for, the owner is explicit, and thin context has not silently become invented fact. Review the records after the first runs and ask representatives whether the summary explains the score and assignment well enough to act on it.

// more agentic workflows to start from
Data & OpsDaily executive brief

Every morning, digest Linear, Fireflies, Gmail & Calendar into a stack-ranked Slack brief.

Preview the daily executive brief playbookData & OpsMeeting action tracker

Turn meeting decisions into reviewed tasks and a lasting decision log.

Preview the meeting action tracker playbookData & OpsWeekly stakeholder update

Draft a source-linked weekly update from project systems for human review.

Preview the weekly stakeholder update playbook

Make inbound lead router yours.

Request access and we'll start with a private draft. You keep control of the tools, permissions, tests, and publication decision.