Inbound leads: from the web form to the right sales rep

Someone fills in the form on your website. They are the easiest person to win over all week: they took the first step. Yet in many companies, their enquiry lands in a shared inbox, waits for a colleague to notice it, then gets copied into the CRM by hand, if it gets copied at all.

This guide describes the process that prevents this, from the form to the sales rep’s first reply. It draws on what runs for a property portal we operate, with Twenty, an open source CRM, and n8n, an automation tool, and on what we set up for teams with several sales reps.

Why does response time matter so much?

Because an enquiry goes cold fast. In 2011, Harvard Business Review published an audit of 2,241 US companies, each contacted through a test enquiry sent from its own website:

The same article reports a second study, covering 1.25 million leads received by 42 companies. Firms that tried to contact the person within an hour were nearly seven times as likely to have a meaningful conversation with a decision maker as firms that tried an hour later, and more than sixty times as likely as those that waited 24 hours or longer. The goal measured is qualifying the lead, not closing it. The data is American and fifteen years old: it gives an order of magnitude, not your response time, which you have to measure.

The most useful part is the causes the article identifies: leads pulled into the CRM once a day instead of continuously, and rules for distributing leads among reps based on geography or fairness. In other words, the process itself.

What are the steps of an inbound lead process?

The first two steps live in the CRM. The next three cross other tools, such as the team’s calendar and messaging, and that is where an automation tool like n8n takes over.

Step 1: save before you notify

Many forms simply send an email. If sending fails, nothing keeps a record of the enquiry, and the visitor will never know.

The rule that follows: the form first writes the enquiry to the CRM, or failing that to a database, and only then notifies anyone. If the email fails, the enquiry is still there, and the alert can be resent. If saving itself fails, the visitor must see it, along with another way to reach you. On a static website, this step goes through a small server function, described in our guide Forms and search on a static site: how to do it.

Step 2: link the enquiry to what you already know

An isolated enquiry forces the rep to piece everything together. A linked one arrives with its context:

• The person: matched by email address if they already exist, created otherwise, without duplicates.
• The company: attached through the email domain, when it is a business address.
• The subject of the enquiry: the product, property or offer on the page the form was sent from.
• The source: the page, language and campaign the visit came from. Without it, you cannot tell which source brings the enquiries that close.

In Twenty, the enquiry can have its own object, with fields your team names, instead of blending into an opportunity. Our guide Twenty beyond the CRM: the back office for your business data shows how these objects are built. If your database already holds duplicates, it is better to clean up your CRM data before connecting the process: a matching rule applied to dirty data creates new errors.

Step 3: assign the enquiry to the right sales rep

The process does not choose the rule: your sales leadership sets it, and the process applies it to every enquiry, with no exceptions and nothing forgotten. Common criteria combine:

The right-hand column is the one people forget. Territory-based routing that ignores holidays fills the inbox of someone who is away. So the full rule reads: “the account owner if there is one, otherwise the territory rep, otherwise the next in the round robin, skipping anyone who is absent”.

Written on one page, that rule becomes a workflow: in Twenty when everything happens inside the CRM, in n8n when it needs to check a calendar or another tool. It can be corrected in a single change, without touching each rep’s settings.

Step 4: notify in the tool the rep already uses

Sales reps do not sit watching their CRM. So the alert goes to a tool they already have open: the team chat, Slack or Teams, or even WhatsApp or Telegram. It fits in three lines: who is asking for what, where the enquiry came from, and the link to the record. An alert that copies the whole enquiry invites people to reply from the chat, and that reply never makes it back into the CRM.

AI can help at this step, and only this one: summarising a long free-text message, detecting its language, or filtering out what is not a sales enquiry, such as a job application or a complaint. The form fields are already structured and need no model at all. That is the position of our automation articles: most processes run without AI.

Step 5: track the first response time

The process records when the enquiry arrived and when the first contact happened. Between the two, a simple rule: past the deadline you set, the team manager receives an alert with the pending enquiry. Set the deadline from your own measurements, not from a promise: track it for a month, then choose a target you can hold.

Two cases deserve a written rule. Friday evening enquiries: does the clock run over the weekend, or is an acknowledgement enough until Monday? And enquiries outside every territory or language you cover: they go to a named person, never nowhere.

A process that stops does not tell anyone on its own. Our guide Monitoring your n8n workflows: no silent failures explains how to be alerted when a workflow goes quiet.

How long can you keep a prospect’s data?

In its guidelines on managing sales activities, the CNIL, France’s data protection authority, recommends keeping the data of a prospect who did not become a customer for three years from collection or from the last contact initiated by that person. Clicking a link in an email counts as contact; merely opening it does not. After those three years, the company may ask whether they want to keep receiving its messages; without a clear, positive answer, the data is deleted or archived. These guidelines are not binding, but they serve as a benchmark.

The process takes care of this too: a scheduled task finds prospects with no contact in three years and prepares either the reminder or the deletion. It is the kind of rule no team keeps up by hand.

Twenty, another CRM, or a spreadsheet?

The process works with any CRM that has an API. Twenty’s strengths are a data model shaped to your vocabulary, a complete API and no per-user licence once it is hosted on your own server; HubSpot does better on ease of use and built-in marketing, at the price of a per-seat subscription. Our comparison Twenty, Dolibarr or Odoo: which one for your team? helps you decide, and if your enquiries currently live in HubSpot, our guide Migrating from HubSpot to an open source CRM in seven steps describes the switch. A spreadsheet cannot run this process: it alerts nobody and keeps no history of the conversation.

Where should you start?

With step 1. If your enquiries currently arrive by email only, having them saved in a CRM before any notification is the change that protects you most, and fastest.

Our custom CRM and ERP offer sets up Twenty in your own vocabulary and connects it to your website, for €4,500. Routing, alerts in your team chat and response time tracking come under our n8n automation offer, from €2,400. If you already have a CRM with an API, the process plugs into it without replacing it.

Frequently asked questions

Sources

1. Harvard Business Review, "The Short Life of Online Sales Leads", March 2011 (new tab)hbr.org
2. CNIL, guidelines on data processing for managing sales activities, 2022 (in French) (new tab)cnil.fr