--- title: "Automatic Lead Routing With a 15-Minute SLA | JustAutomate" description: "A new lead reaches the right rep in seconds: segment, region, industry and duplicates in one rule. Escalation after 15 minutes, live in 2 to 4 weeks." url: "https://justautomate.ai/en/automations/automatic-lead-routing/" lang: en --- Sales and CRM # Automatic lead routing with no argument over whose lead it is An enquiry from a form, an ad or a chat reaches the right rep within seconds, with context and a deadline for first contact. The rule checks segment, region, industry, whether the company is already in the CRM and whether the owner is away. A lead with no response after 15 minutes goes to their manager. Book a free consultation [See how the workshop works](https://justautomate.ai/en/services/process-workshop/) - 7 timesroughly how much more often a company that calls within the first hour qualifies a lead than one that waits an hour longer. Audit of 2,241 companies, Harvard Business Review - 15 minuteshow long a lead can wait for first contact before the rule escalates it to the manager - 2 to 4 weeksfrom workshop to routing running in production, tested on your own leads from the past few weeks The problem ## Why does a good lead land with the wrong person? A rep is on holiday and their leads sit until Monday. Two salespeople call the same company on the same day, because the CRM holds it once under the registered name and once under the name of a branch. A large lead goes to a junior, because the junior happened to be next in the queue. The form arrives at 18:40 and nobody sees it until morning, although for the buyer in Boston it is still the middle of the afternoon. None of this is unusual. It is the ordinary week of a team where one person assigns leads by rules kept in their head. The more channels you run, that is the website form, Meta Lead Ads, LinkedIn Lead Gen Forms, chat, phone and a landing page behind Google Ads, and the more people on the team, the more often the rule gets broken under time pressure. The cost is countable. In an [audit of 2,241 companies published in Harvard Business Review](https://hbr.org/2011/03/the-short-life-of-online-sales-leads) the average response time to an inbound web enquiry was 42 hours, and 23 percent of companies never replied at all. Companies that made contact within an hour qualified a lead nearly 7 times more often than those that waited an hour longer, and more than 60 times more often than those that waited a day. - A lead waits half a day for contact, because nobody knows it is theirs - Two reps call the same company and then argue over whose commission it is - An enquiry you paid for in ads dies in an inbox after hours - The assignment rules exist only in the sales manager's head Why now ## What changed, so that this takes weeks rather than a quarter? Every sourcing channel now hands over an enquiry a second after it is submitted: the website form, Meta Lead Ads, LinkedIn Lead Gen Forms, a Typeform after a webinar, chat. Nobody has to wait for someone to open an inbox and read it. Native assignment inside a CRM, such as lead rotation in HubSpot or Lead Assignment Rules in Salesforce, handles one criterion well. Put segment, region and industry together and it grows into dozens of entries that have to be corrected by hand every time the team changes. The [HubSpot developer documentation](https://developers.hubspot.com/) is public, so the logic can sit outside the CRM in n8n, Make or a custom API integration, and the CRM stays the place where the result is written down. The third change is the AI agent. A rule will assign a lead, but it will not answer a manager asking how many leads have been waiting longer than 15 minutes today. BOND, our company AI agent, answers that in a plain sentence in 5 to 10 seconds, with no CRM login and no report to build. What changes ## What does the sales team get? - ### Assignment in seconds, not in hours A webhook receives the enquiry, the rule checks segment, region, industry and deal size, and the rep gets a notification with the context: who it is, which company they are from, what they typed into the form. A notification on Slack, in Teams or by email within seconds of the form being sent - ### No duplicates, no argument over the lead Before assigning, the workflow checks the CRM by email, by domain, by fuzzy company name and by the identifier used in that market: Companies House, VAT number, Handelsregisternummer, Swiss UID. A confirmed duplicate goes back to the rep who already owns the account. Four matching criteria instead of a company name that every register spells differently - ### A holiday does not stop a lead An absence marked in Google Calendar or Outlook sends the lead to a stand-in. A lead outside your segments, from a country you do not cover, or with an incomplete email goes into a manual review queue rather than into nothing. Every lead has an owner or a place in the queue, there is no third option - ### An SLA that polices itself A lead with no first contact after 15 or 30 minutes of working hours in its own market escalates to the manager. You see the backlog the same day, not at the weekly review. The threshold is counted in the lead's own timezone: CET for Poland and DACH, GMT and BST for the UK - ### The source of the lead written into the CRM We record the last channel the lead came through and the first touch with the brand, rebuilt from the utm parameters kept from the first visit. The rep sees the whole path, not only its end. Last touch and first touch in HubSpot, Pipedrive or Salesforce - ### Questions about the funnel in a plain sentence How many UK leads came in after hours yesterday. Who has the most open opportunities from DACH today. How many duplicates did routing catch this month. The AI agent answers from the CRM. An answer in 5 to 10 seconds, in English or in Polish, with no report and no CRM login Proof ## Do you handle your own leads this way? Yes. Since March 2026 enquiries in our founders' agency have been handled by an AI agent, the same one behind the numbers on our AI automation agency page. Below is the scale of that work, together with what the number does NOT prove. Built for ourselves. These are not client deployments but implementations inside the founders' own companies. We say so plainly, because proof you cannot verify is not proof. - ![JustIdea Agency](https://justautomate.ai/klienci/justidea.png)![JustBot](https://justautomate.ai/agenci/justbot-80.webp)JustBottheir agent JustIdea Agency, a performance marketing agency of around 30 people 23 people from the company work with the agent 38 systems wired in permanently 112 processes run without a human 475 thousand lines of the agent’s code The agent is wired into HubSpot, the website forms, Slack and the data warehouse. Enquiries arrive from forms, from ads and from referrals. 8 of 38 systems it works in - Google Ads - Meta Ads - HubSpot - ActiveCollab - Ahrefs - GA4 - Search Console - BigQuery Before A person read the enquiry, created the contact and the company in the CRM by hand and decided who should get it. Response time depended on who happened to have their inbox open. After The agent picks up the enquiry, creates the contact and the company in HubSpot, checks for a duplicate by domain and notifies the team on Slack. A person steps in at the conversation, not before. 3,432 operations on leads and 1,301 on form submissions in 30 days, with no human involved And in your company ## What if our team works differently? Four sentences we hear most often, and how we answer them. - We have two salespeople, they sort it out over coffee. Then routing solves a problem you do not have yet, and we will say so in the consultation. Tidying up the CRM or finishing the contact form is the better use of the money. We come back to the subject when the person handing out leads becomes the bottleneck, or leaves the team. - Our rules are not written down anywhere. They almost never are, and that is the first output of the workshop: the rules from the sales manager's head land on paper together with the exceptions. Only once they are written down can they be automated, and only then do they stop being broken under time pressure. - HubSpot already has lead rotation, why add anything? If there is one criterion, rotation is enough and we will tell you that. With segment, region and industry at once, native rules grow into dozens of entries that need correcting every time the team changes. That is when the logic moves to n8n or Make and the CRM records the result. - We sell into the UK, Germany and Poland, and every market has its own rules. The rule knows the timezone, the holiday calendar and the company identifier used in each market: Companies House and SIC in the UK, Handelsregisternummer and NACE in DACH, UID and NOGA in Switzerland, NIP and PKD in Poland. Personal data is processed under the law of the country the lead comes from: GDPR 2016/679 in the EU, UK GDPR in Britain, the revised FADP in Switzerland. CRM HubSpot, Pipedrive, Salesforce, Zoho Sourcing channels Website form, Meta Lead Ads, LinkedIn Lead Gen Forms, Typeform, chat, Google Ads landing page Notifications Slack, Microsoft Teams, email Calendars and availability Google Calendar, Outlook, Calendly Company data Companies House, VIES, national business registers, enrichment by domain Automation layer n8n, Make, Zapier, custom API integrations ## Routing criteria and where the data comes from The rules a routing setup is usually built from. The order in which they are checked is agreed in the workshop, because when two criteria point at two different people the hierarchy decides, not the order of nodes in a scenario. | Criterion | Where the data comes from | When it makes sense | | ------------------------ | ------------------------------------------------------------------- | ----------------------------------------------- | | Duplicate in the CRM | email, domain, fuzzy company name, VAT number, Companies House, UID | always, checked first | | Segment and company size | headcount from the form, from the CRM or from enrichment by domain | separate SMB and enterprise teams | | Region | country, state or county, postcode ranges | territory split, several markets at once | | Industry | SIC in the UK, NACE in DACH, NOGA in Switzerland, PKD in Poland | reps specialised by sector | | Deal size | budget from the form, account size, history in the CRM | seniors on large deals, juniors on smaller ones | | Availability | holiday and sick leave in Google Calendar or Outlook | cover without reassigning by hand | | Workload | open opportunities per person this month | weighted round robin when quotas are uneven | These rows are a starting point. For most clients a first rollout covers three to four criteria, and the rest goes in when it turns out to be needed. How we work ## Five steps from rules in someone's head to routing in production Every step ends with something you can judge before you decide on the next one. 1. ### Workshop We take today's assignment apart: who decides, on what basis, how long it runs from enquiry to first contact and where the arguments start. We look at the systems you already have, including the spreadsheet quietly acting as a second CRM. 2. ### Rule design The hierarchy of criteria, the order they are checked in, the exceptions and the manual queue. Then the choice of tool: n8n, Make or an API integration with your CRM. We agree which personal data is genuinely needed for routing and how long to keep leads that never entered the process. 3. ### Rollout in parallel The workflow runs alongside the current assignment, with nothing switched off. We check the assignments against your own leads from the past few weeks, duplicates, after-hours leads and leads from countries you do not cover included. 4. ### Switch-over and training Once it checks out we switch to production with error monitoring. The sales manager learns to change a rule without us: a new joiner, a change of territory, someone off sick taken out temporarily, a different SLA threshold during a campaign. 5. ### Observation For the first few weeks we watch the real assignments: whether the hierarchy causes arguments, whether the SLA threshold is realistic for the market, whether cover works. We retune the rules against what actually arrives, not against what we predicted. Before and after ## How a sales manager's day changes ### Before - The morning starts with the inbox and passing on leads that came in last night - Settling an argument between two reps over whose lead it is - Finding out at the weekly review that nobody called some of the leads - Explaining the assignment rules to a new joiner out loud, again ### After - Last night's lead has an owner and a contact deadline before the manager opens the laptop - The duplicate went back to the existing owner before anyone had time to call - The 15-minute backlog shows up the same day, through an escalation - The rules are written down and the manager changes them alone, in one place The first assignments are visible on switch-over day. The SLA threshold and the hierarchy of criteria we judge after 30 days on real leads. For the person signing this off ## What a head of sales gets out of it Arguments over leads and the question of why nobody called stop landing on your desk, because a rule you approved settles them. Response time to a lead becomes a number in a system instead of an impression from the weekly review. The second thing matters more in front of the board. You know how many paid-for leads waited longer than the threshold and who received them. That is an argument in the conversation about the advertising budget that you do not have today. - Rules written down and versioned, independent of any one person - Escalation after 15 minutes instead of a backlog discovered a week later - The workflow runs in parallel, so the old assignment holds until the tests are done - Team changes are made on your side, with no ticket raised with us What it costs ## The workshop has a published price, the rollout is quoted after it The process workshop costs **EUR 3,500 net per week**, and runs from one to seven weeks. Lead routing is usually one week, because the process is narrow: from enquiry to assignment. We quote the rollout after the workshop, once it is clear how many channels and criteria are in scope and what state the CRM is in. You pay the cost of running the workflow directly to the tool provider, that is n8n, Make or Zapier, or you pay nothing at all when it sits on your own infrastructure. No margin from us. The same goes for model costs when an AI agent is part of the setup, where a single query costs the provider roughly EUR 0.005 to 0.07. - ### Process workshop EUR 3,500 net per week, and lead routing is usually one week A self-contained piece of work. It ends with the assignment rules written down, exceptions included, and a plan you could execute without us. - A map of how leads are assigned today and where they go missing - The hierarchy of criteria written down together with the exceptions - A tool recommendation: native CRM rotation, n8n, Make or the API - The SLA threshold and the metrics to measure at 30 days Start with the workshop - Most popular ### Workshop and routing rollout Quoted after the workshop scope follows from the number of channels and criteria The option most companies choose. Working routing 2 to 4 weeks after the workshop, tested on your own leads. - Everything in the workshop - A workflow in n8n, Make or over the API, wired into the CRM and the sourcing channels - Duplicate detection, cover for absences, a manual queue and SLA escalation - A parallel rollout and a switch-over with monitoring - Training for the sales manager on changing rules without us Talk about a rollout - ### Routing and an AI agent for sales Quoted after the workshop for teams that ask about the funnel a dozen times a day Everything in the rollout plus BOND, which answers questions about the state of your leads in a plain sentence. - Everything in the routing rollout - An AI agent wired into the CRM: how many leads are waiting, who holds what, how many duplicates - Alerts on after-hours leads and on a breached SLA - Access for the reps and for the manager, in English and in Polish Ask about the agent If the workshop shows that native rotation in your CRM is enough, we say so and show you how to set it up. The matter ends with the workshop instead of a rollout you do not need. ## Frequently asked questions What is automatic lead routing? It is a workflow that receives an enquiry from a form, an ad or a chat and assigns it to the right rep within seconds, by agreed rules: segment, region, industry, deal size and availability. On the way it checks whether the company is already in the CRM and notifies the owner with context. A person only decides in the cases the rule does not cover. How long does a lead routing rollout take? One week of workshop and 2 to 4 weeks of rollout, with tests on your own leads from the past few weeks. Lead routing is a single point of integration with one CRM over a webhook and an API, not a data migration, which is why it is shorter than most sales automations. Do we need n8n or Make if we already have HubSpot? Not always. With one criterion, lead rotation in HubSpot or Lead Assignment Rules in Salesforce is enough and we will tell you so. An outside orchestrator earns its place when several criteria apply at once, because native rules then grow into dozens of entries maintained by hand. What happens to a lead the rule cannot assign? It goes into a manual review queue with a note saying why it is there: a country you do not cover, a missing email address, a segment outside the definition. A lead never disappears inside the rules. When two criteria point at two people, the hierarchy agreed in the workshop decides. How does routing detect duplicates? By email, by company domain, by fuzzy name matching, so that Harrison Logistics Ltd and Harrison Logistics count as one company, and by the identifier used in that market: Companies House in the UK, a VAT number or Handelsregisternummer in DACH, UID in Switzerland, NIP in Poland. A confirmed duplicate goes back to the rep who already owns the account. What about Meta Lead Ads leads with no email address? The mobile Meta form often collects only a first name and a phone number. Matching then runs on the phone number and the company name, and where that is not enough the lead goes into the manual queue rather than creating a new record for someone who called a month ago. How do you count the SLA on leads from several countries? The 15 or 30 minute threshold is counted in the working hours of the lead's own market. The UK runs an hour behind Poland and DACH and has its own bank holidays, so both the timezone and the holiday calendar matter. An after-hours lead gets an owner straight away, and the SLA clock starts at the beginning of the working day. Is lead data safe when it is processed outside the CRM? We pass only the fields needed for the decision, and we agree that list in the workshop. Processing follows the law of the lead's country: GDPR in the EU, UK GDPR in Britain, and the revised Swiss FADP, which sets different transfer rules because Switzerland sits outside the EU. We also agree how long to keep leads that never entered the sales process. ## Let us find out where your leads go missing today The free consultation takes 30 minutes. You tell us how many reps you have and how you split leads between them today, even if the rules exist only in your head. We show you which of them can be turned into a workflow straight away and which need the CRM sorted out first. You do not have to share any systems at this stage. We run at most two rollouts at a time, so that someone is genuinely sitting on each of them. [Book a free consultation](https://justautomate.ai/en/contact/) **PS.** If anyone in your team asked whose lead it was this week, that is exactly the problem. A rule living in one person's head gets broken under time pressure, and it cannot be automated until it is written down. That is where the workshop starts. ## Related - [Automatic lead scoring](https://justautomate.ai/en/automations/automatic-lead-scoring/) - [Automatic follow-up](https://justautomate.ai/en/automations/automatic-follow-up/) - [CRM implementation and integration](https://justautomate.ai/en/services/crm-implementation/) - [n8n automation](https://justautomate.ai/en/services/n8n-automation/) - [BOND, business AI agent](https://justautomate.ai/en/services/bond-business-ai-agent/) - [Process workshop](https://justautomate.ai/en/services/process-workshop/) --- **JustAutomate** · contact: contact@justautomate.ai · form: https://justautomate.ai/en/contact/