All use cases

Lead Router with SLA Timers

Every lead owned in minutes, or escalated.

AutomationsAgent: claude
Integrated Services
Slack
Required Configuration

This use case works best with the following environment variables, which are injected into your sandbox at runtime:

SLACK_WEBHOOK_URL
Prompt
Build a lead routing system with SLA enforcement: 1. Lead intake endpoint + manual entry form (seed 10 leads: source, territory, size) 2. Routing rules as editable data: by territory and deal size, round-robin within a team 3. SLA timers: each routed lead has a first-touch deadline (e.g. 15 minutes); a visible countdown runs per lead 4. Breach behavior: overdue leads escalate — reassigned to the next rep and posted to a Slack channel with lead details and time-in-queue 5. Board: unrouted, awaiting first touch (with timers), in conversation, escalated 6. SLA report: average first-touch time per rep, breach count per week Use Slack webhooks for escalation posts. Seed one lead already breached so the escalation path shows immediately.
Use this

Why this exists

Speed to lead is the most measurable revenue lever in sales: response inside five minutes is worth multiples of response inside an hour, and every ops team knows it. What most teams lack isn't the knowledge, it's enforcement. Leads land in a shared inbox, ownership is fuzzy, and the SLA is a slide in a deck. This blueprint turns the SLA into running code with a countdown.

What the agent builds

A lead routing system with an intake endpoint plus manual entry, routing rules stored as editable data (territory, deal size, round-robin within a team), and, the teeth, a visible first-touch countdown on every routed lead. When a lead breaches its deadline, it escalates: reassigned to the next rep and posted to a Slack channel with the lead's details and time-in-queue. The board shows unrouted, awaiting-first-touch (with live timers), in-conversation, and escalated. An SLA report tracks average first-touch time per rep and breaches per week.

It seeds ten leads including one already breached, so the escalation path is visible the moment you open it.

Make it yours

  • "Route enterprise-size leads straight to the senior rep, skip round-robin."
  • "Add a webhook so my website form feeds the intake directly."
  • "Make the SLA 5 minutes during business hours, 12 hours overnight."

FAQ

Does it need Slack? Escalations post via a Slack webhook (auto-configured when you connect the service). Without Slack, everything else works, escalations just stay on the board.

Can it replace my CRM? It's not trying to, it's the enforcement layer most CRMs lack. Ask the agent to push accepted leads onward to wherever your pipeline lives.

What counts as "first touch"? A rep marking the lead as contacted. If you want it stricter, verified by an email actually sent, that's a follow-up message.

Lead Router with SLA Timers | OutcomeDev Use Cases