# Salesforce Web-to-Lead: what a sales manager should check so web leads do not rot in the queue

https://salesbond.app/blog/salesforce-web-to-lead-lead-queue-manager-check/
Published: 2026-10-20 · Updated: 2026-10-26

Web-to-Lead is a Salesforce feature that turns submissions from a form on your website into Lead records. It does the capture and nothing else: it does not decide who owns the lead, it does not check that anyone called, and it does not tell you when the form has started sending junk. That part is the sales manager’s job, and it fits in a short weekly check of four things: owner, first touch, source and duplicates.

## What Web-to-Lead in Salesforce does (and what it does not)

The mechanics are simple. In Setup you enable Web-to-Lead, pick the Lead fields the form should collect, and Salesforce generates an HTML form that posts to a Salesforce endpoint. When a visitor submits it, Salesforce tries to create a Lead and sends the visitor on to the return URL you entered ( [Salesforce Tutorial: Web to Lead setup guide](https://www.salesforcetutorial.com/web-to-lead-salesforce/)).

That is the whole feature. There is no inbox where web leads wait to be reviewed; they land in the Lead object next to everything else. There is no built-in alert when a lead sits untouched. Salesforce’s own setup guidelines tell you to add a validation rule on the Email field for web-generated leads ( [Salesforce Help: Guidelines for Setting Up Web-to-Lead](https://help.salesforce.com/s/articleView?id=sf.setting_up_web_to_lead.htm&language=en_US&type=5)), which says a lot about what the form checks by itself.

Web-to-Lead is plumbing. Plumbing is fine. Somebody still has to own the tap. Zoho CRM has a similar built-in form, and teams there also have to decide on Zoho Forms: see [Zoho CRM web forms vs Zoho Forms](https://salesbond.app/blog/zoho-crm-web-forms-vs-zoho-forms/).

## The five fields a manager should require on the form

Marketing wants a short form, and they are right that fewer fields convert better. The argument is not about length. It is about which fields sales actually leans on, and there are five:

- Last Name, so a rep can open the call with a name.
- Company, the field assignment rules and duplicate rules most often key on.
- Email, with a validation rule behind it.
- Lead Source, as a hidden fixed value per form, so the visitor never picks the channel.
- A hidden form or page identifier, so you can tell the pricing-page lead from the ebook download.

Email deserves a sentence more. Put the check in Salesforce as a validation rule on the Lead Email field, as the guidelines above suggest. The catch: a submission that fails a validation rule never becomes a lead ( [Salesforce Tutorial](https://www.salesforcetutorial.com/web-to-lead-salesforce/)), so sales won’t see it anywhere. Whoever owns the website must know the rule exists.

## Who owns a web lead: assignment rule or queue

The lead exists. Now who sees it? Salesforce’s guidelines are short on this: an active lead assignment rule sends web leads to users or queues, and leads that match no rule, or arrive while the rule is inactive, go to the default owner set in Lead Settings ( [Salesforce Help](https://help.salesforce.com/s/articleView?id=sf.setting_up_web_to_lead.htm&language=en_US&type=5)).

The choice is a management decision, not an admin one. A rule that assigns straight to a rep is right when the routing is clear from the form: territory, product line, company size. “Untouched” then means one person’s name is on it. A queue is right when someone qualifies or enriches before a named rep should spend time. The cost is that a queue is nobody until somebody pulls from from it, and queues are where web leads go to age quietly.

The worst setup is the accidental one, where nothing matches and every web lead lands on a default owner who changed roles a year ago. Reviewing rules and default owner is covered in [how to audit Salesforce lead assignment rules](https://salesbond.app/blog/salesforce-lead-assignment-rules-audit/) and [finding unowned records in Salesforce queues](https://salesbond.app/blog/salesforce-queues-unowned-records-audit/). Here we only need the output: every web lead has an owner who knows they own it.

![Flow of one web lead: validation, assignment rule, owner or queue, first activity, with the places where Checks 1, 2 and 3 apply](https://salesbond.app/wp-content/uploads/2026/10/salesforce-web-to-lead-lead-queue-manager-check-2.png)

## Check 1: web leads with no owner or no first touch

Run this one every week, same day, same list view. Build a Lead list view filtered on Lead Source equals your web value and Created Date equals last week, sorted by Lead Owner, with Last Activity and Lead Status as columns. Three things to read off it.

First, who the owner is. If the owner column shows a queue name or the default user for more than a handful of rows, routing is broken, not the reps.

Second, whether anyone has touched the lead. In Salesforce the honest signal is an activity on the record: a logged call, a sent email, a completed task. A web lead created last Tuesday with Last Activity blank has not been worked, whatever gets said in the stand-up.

Third, how long the gap was. The response time you promise on the website is the standard. If the form page says you’ll get back to people within one business day, the check is whether the first activity date is the next working day or earlier.

What to do with the rows that fail: nothing clever. Reassign the ownerless ones today, ask for a first activity on the untouched ones by end of day and write down the count. The count is the point.

## Check 2: junk, spam and duplicates

The form is a public endpoint, so bots can find it and call it directly ( [Salesforce Tutorial](https://www.salesforcetutorial.com/web-to-lead-salesforce/)). Checks on your web page do not protect the Salesforce side. The controls have to live in Salesforce, and there are three, cheapest first.

Keep Require reCAPTCHA Verification switched on in the Web-to-Lead settings and regenerate the form after you change it ( [Salesforce Tutorial](https://www.salesforcetutorial.com/web-to-lead-salesforce/)). This stops the dumb bots, not a human typing a fake company name. After any change, submit a real test lead end to end, because a form that silently rejects everything looks exactly like a quiet week.

Second, the validation rule on Email from the field list, and if your junk has a pattern, a rule for that pattern too.

Third, duplicate and matching rules on the Lead object, so the fourth time the same person downloads the same guide you get one lead with four touches, not four leads with four owners. Setting those up is covered in [the manager’s check for Salesforce duplicate and matching rules](https://salesbond.app/blog/salesforce-duplicate-rules-matching-rules-manager-check/). For the weekly review, sort last week’s web leads by Email and then by Company and look for pairs.

## Check 3: Lead Source and Lead Status that make reports honest

Here is the test. Open a report of leads grouped by Lead Source for last quarter. Does your web value exist, and is it populated for every lead the form created? If not, the form is sending Lead Source blank, or the picklist carries three spellings of the same channel, and no report on marketing contribution can be trusted. Fix it at the form with the hidden value, then with a one-off data update for the history.

Lead Status is teh second half. Web leads stick on the entry status because nobody is penalised for leaving them there. In the weekly view, watch two things: leads still on the entry status after the first-touch deadline (those belong in Check 1), and leads on a working status for weeks with no activity. Those are usually dead; disqualify them with a reason so the funnel stops counting them as live. Which values to keep, and which one counts as converted, is covered in [Salesforce lead status values](https://salesbond.app/blog/salesforce-lead-status-values-converted/).

What happens after conversion is its own topic, in [Salesforce lead conversion and field mapping](https://salesbond.app/blog/salesforce-lead-conversion-field-mapping/). For this check it is enough that the two picklists tell the truth: where the lead came from, and where it is now.

## Web-to-Lead limits to know before you rely on the form

Salesforce caps Web-to-Lead at 500 leads in a 24-hour period. Past that, the Default Lead Creator named on the Web-to-Lead setup page gets an email saying the limit was exceeded, and further requests wait in a pending queue shared with Web-to-Case, which is processed when the limit resets; that queue holds up to 50,000 requests, and once it is full new requests are rejected ( [Salesforce Help: How many leads can we capture from our website?](https://help.salesforce.com/s/articleView?id=sf.faq_leads_how_many_leads.htm&language=en_US&type=5)). Salesforce takes requests for a higher limit through support. In practice the limit gets hit by spam more often than by a good campaign, so make sure someone actually reads the Default Lead Creator’s mail.

The other limit isn’t a number. The form only works as long as the Lead object agrees with it: add a required field, a validation rule or a restricted picklist later, and submissions that used to pass start failing ( [Salesforce Tutorial](https://www.salesforcetutorial.com/web-to-lead-salesforce/)). Retest the form after every change to Lead.

Web-to-Lead is also the wrong tool when you need file uploads, several related records created together, routing that depends on a lookup in another system, or fraud controls beyond a captcha; that is a job for an authenticated integration ( [Salesforce Tutorial](https://www.salesforcetutorial.com/web-to-lead-salesforce/)). Form vendors still end up creating a Lead in Salesforce, so every check here still applies.

## The weekly check, on one screen

- Every web lead from last week has a named owner, not a queue and not the default user.
- Every one of them has a first activity by the deadline you promise on the site.
- Lead Source is the web value on all of them; no blanks, no “Other”.
- No pairs by Email or Company, and the spam count is noted; if it jumped, reCAPTCHA and the email rule get a look.
- Lead Status has moved off the entry value, or the lead is disqualified with a reason.
- Someone reads the Default Lead Creator’s mail, including any limit-exceeded notice.

A disclosure, since this is where the manual work piles up. We build SalesBond, a sales management layer on top of the CRM a team already uses; we started with Pipedrive. It checks deals, not leads, so this weekly review stays yours. Once a web lead becomes an opportunity, Deal Health checks it with the rest of the pipeline, ownership and activity included. [Check your CRM with SalesBond](https://salesbond.app/).