Sales — lead intake + triage
Capture inbound leads, enrich and score them, and route to an owner.
This is an illustrative scenario, not a real customer. The numbers and narrative below are a worked example of how this process would run on G8 — accurate to the product, but not a measured case study.
00 / Before and after
Before — manual
Form submissions land in a shared inbox. A rep skims them between calls, looks up the company by hand, and forwards the promising ones. Good leads sit for hours, and obvious spam still gets a reply.
After — on G8
Each submission runs the flow: it enriches the lead, scores it against simple rules, and either routes a standard lead to an owner or holds a high-value lead at an approval gate for a rep to claim.
01 / The G8 lifecycle, applied
From description to running flow
- 01 / Blueprint
Describe intake and routing
Revenue ops describes it plainly: on a new lead, enrich the record, score it, route standard leads round-robin, and flag high-value or risky leads for review. G8 compiles the Blueprint and surfaces the risky step.
- 02 / Contract
Bound enrichment and outreach
The contract allows reading enrichment data and notifying an owner, blocks any outbound email to the lead without sign-off, and requires approval before assigning a high-value lead.
- 03 / Simulate
Score against sample leads
Simulation runs a batch of example submissions and shows the score, the chosen owner, and which leads would pause for approval — without sending a single notification — so the rules can be tuned first.
- 04 / Run
Route in minutes, gate the big ones
Live, the webhook trigger runs per submission. Standard leads route automatically; a high-value lead pauses at the approval gate until a rep claims it, then resumes.
- 05 / Monitor
Track volume and conversion of the flow
Monitor shows how many leads ran, how many succeeded, and how many are waiting to be claimed — making a backlog of unclaimed high-value leads obvious at a glance.
02 / Connectors and approvals
Connectors used
- HTTPEnrich the lead and write the record to the CRM API.
- SlackNotify the assigned owner that a lead is theirs.
- EmailSend the rep an approval prompt for a high-value lead.
Approvals and blocks
- Assigning a high-value lead is approval-required — a rep claims it from the gate.
- Any outbound email to the lead is blocked until a human signs off.
03 / The illustrative outcome
Illustrative: standard leads reach an owner in minutes instead of hours, and the deals worth a human's attention are the only ones that wait for one.
Model your own process.
Describe it, contract it, simulate it, and watch it run — with humans on the risk.
Start a flow