Skip to main content

Auto-Route New Leads to the Right Rep

By the end of this recipe you'll have an automation that catches every new lead the instant it arrives, routes it to the right rep by territory or segment, assigns them as the owner, and stamps the row with a status and timestamps — so no lead ever sits in an unassigned pile. Because your lead capture, your pipeline board, and your team all live in one workspace, the automation has the context to do the triage a sales manager would otherwise do by hand — in seconds, around the clock.

Readiness: Available now — built as a single Automation. The version where a named teammate owns routing end to end is rolling out in early access.

What it does​

The moment a new lead arrives — a web form is submitted, or a row lands in your Leads table — one automation runs the triage:

  1. Reads the lead and works out which bucket it belongs to — by region, segment, company size, product interest, or a combination.
  2. Routes it to the right rep by assigning them as the row's Owner, so exactly one person owns every lead.
  3. Stamps the board — sets Status → Assigned, records the Assigned date, and sets a Follow-up by date so the clock starts ticking.
  4. Tells the rep with a direct message (and, if you like, a note in your sales channel) so they can reach out while the lead is still warm.

No lead sits unclaimed. No manager plays traffic cop. The rep hears about it in seconds instead of the next morning — which matters, because speed-to-lead is one of the strongest predictors of whether an inbound lead ever converts.

Build it yourself​

One-time setup​

Create the Leads board

Make a board with a table for leads. Add columns for Company (and contact Email), Region (a single-select like Americas / EMEA / APAC), Segment (a single-select like SMB / Mid-Market / Enterprise), Company size (a number), Product interest, an Owner people column, a Status single-select (New, Assigned, Working, Won, Lost), an Assigned date, a Follow-up by date, and a Message rich-text column for anything the lead typed. If leads come in through your website, build a public form from this table so submissions become rows.

The routing automation​

Trigger: Form submitted

Add a Form submitted trigger so the automation runs the instant someone submits your lead form. However your leads actually arrive, there's a trigger for it — if they land in the table by import, the API, or an inbound integration instead of a form, use Row created on the Leads table and the rest of the steps are identical.

(Optional) AI step: clean up messy leads

If your form has a free-text "What do you need?" field, add an AI → Classify step to tag the lead's Segment (SMB / Mid-Market / Enterprise), or an AI → Extract step to pull structured details (company size, use case) out of the message and drop them into columns. Map the result to the field you'll route on. Skip this if your form already captures region and segment as clean select fields — routing on structured fields is always more reliable than routing on free text.

Condition: route by territory or segment

Add a Condition block that checks where the lead should go. Use Compare two values for a single rule (for example, Region equals "EMEA"), or a Row filter with AND/OR groups to combine rules (for example, Segment is Enterprise AND Company size greater than 500). The condition's true output handles this rep; its false output flows on to the next condition for the next region or segment.

Action: assign the right rep

On the matching true branch, add an Assign user(s) action that adds the correct rep to the Owner people column. Then build a cascade — condition → assign, condition → assign — so each territory or segment ends with exactly one owner. Add a final catch-all branch that assigns an inbound owner or your sales manager, so a lead can never fall through with no rep.

Action: stamp the board

On the same branch, chain three quick actions so the row carries its full state: a Set field action to set Status → Assigned, a Set date to now action to stamp the Assigned date, and a Set date relative action to set Follow-up by (for example, Assigned date + 1 day). This is the "stamp the board" half of the outcome — every routed lead now shows who owns it, when it was assigned, and when first contact is due.

Action: tell the rep

Add a Send direct message (or Send notification) action to the assigned rep so they know a lead is waiting, with the company name and a link to the row. For team visibility, add a Post channel message to your #sales channel too — "New EMEA lead → Aisha."

(Optional) Action: start an SLA timer

Add an SLA timer control action to start a first-response SLA timer on the row. Now you can measure speed-to-lead, and even build a separate automation that fires on SLA breached to escalate any lead a rep hasn't touched in time.

tip

Keep the whole thing in one automation. A broad trigger (any new lead) followed by a cascade of condition → assign pairs is easier to read and maintain than one automation per rep — and the live validation flags any branch you forget to connect before you publish.

Or just ask Copera AI​

You don't have to lay out the graph by hand. Open Ask Copera AI and describe the outcome:

"Create a Leads board with columns for company, email, region, segment, owner, status, assigned date, and a follow-up date. Then build an automation: when our lead form is submitted, route the lead to the right rep by region — Americas to Diego, EMEA to Aisha, APAC to Mei — set them as the owner, mark it Assigned, stamp the assigned date, set a follow-up date one day out, and DM that rep that a new lead is waiting."

Ask Copera AI can create the board and its columns, then assemble the whole routing automation — trigger, conditions, and actions — for you. With the default Ask before acting permission mode, it shows a review card for each change before anything is created, so you approve the board setup and the automation before they exist. See What Copera AI Can Do for the full list of what it can build.

Make it a standing teammate​

Early access

Standing AI teammates are rolling out gradually. When one is available in your workspace, you can put a named teammate — a "Sales Ops" agent — in charge of routing: it reads each new lead, decides the best-fit rep from your rules and the lead's own words, updates the Owner field, and DMs the rep that a lead is waiting, all under its own identity. Until then, the automation above does the routing, stamping, and hand-off today. Learn more in AI teammates.

Tips​

tip

Speed-to-lead is the whole game. The automation fires the instant a form is submitted or a row is created, so a lead is owned in seconds, not hours. Pair it with the optional SLA timer and an SLA breached escalation so a lead can never go quiet without someone noticing.

tip

Route on clean fields, not prose. Conditions are exact when they compare select fields like Region and Segment. If your leads arrive as messy free text, add an AI → Classify or AI → Extract step first to turn the message into those fields, then route on the result.

tip

Always end with exactly one owner. Build routing as a cascade of condition → assign pairs, and finish with a catch-all branch that assigns an inbound owner or your manager. That way an odd lead that matches no rule still lands with a real person instead of sitting unassigned.

tip

Prefer round-robin? You can approximate it: keep a counter, add an Increment number action each time a lead arrives, and use a Formula condition to branch to the next rep in rotation. Territory or segment routing is simpler and the most common setup, so start there and reach for round-robin only when everyone genuinely shares one queue.

Frequently Asked Questions​

Can Copera automatically assign new leads to the right sales rep?​

Yes. An automation triggers when a lead form is submitted or a new row lands in your Leads table, uses condition blocks to route the lead by territory, segment, or company size, then an Assign user(s) action sets the correct rep as the row's owner. It also stamps the status and dates and messages the rep — all in seconds, with no manager in the middle.

Does lead routing happen instantly?​

Yes. The automation fires the moment its trigger event happens — a form submission or a row being created — so the right rep is assigned and notified within seconds. That speed-to-lead is one of the biggest predictors of whether an inbound lead ever converts.

Can I route leads by territory, company size, or product?​

Yes. Condition blocks compare the lead's fields — region, segment, deal size, product interest — using operators like equals, contains, and greater than, and you can combine several checks with AND/OR groups. Each condition sends the lead down a true or false path to the matching rep.

Can Copera do round-robin lead assignment?​

You can approximate round-robin with an Increment number action on a counter plus a Formula condition that branches to the next rep in rotation. Attribute-based routing — by region or segment — is simpler and the most common real-world setup, so most teams start there and add a round-robin catch-all for everything else.

Does the AI decide who gets each lead?​

The routing rules are yours to define. Optionally, an AI → Classify or AI → Extract step can read a lead's free-text message and tag it with a segment or pull out structured details, so messy inbound leads route cleanly — but the assignment itself follows the rules you set, so you always know why a lead landed where it did.