Salesforce’s Web-to-Lead and Web-to-Case features convert website form submissions directly into Salesforce records – no middleware required. Web-to-Lead creates a Lead record from a contact form or demo request form. Web-to-Case creates a Case record from a support or help request form. Both features generate the HTML form code that can be embedded on any website, and both support auto-response emails and assignment rules that route the new records to the right team automatically. This guide covers the setup process, available customisations, limitations, and when to consider alternatives.
In practice, the biggest advantage is that the team can respond from a structured record instead of trying to reconstruct the request from scattered messages.
It also helps keep the first interaction tied to a record so the handoff is easier to follow later.
For sales and service teams, that can make the first response feel far more organised.
The value is not only in the form submission itself. It is in how quickly the data reaches the right workflow after it is submitted.
That makes them practical tools for organisations that want a faster and more reliable handoff from the web into Salesforce.
Salesforce Web-to-Lead and Web-to-Case are useful when a website needs to turn submissions into CRM records automatically. They help teams capture lead and support requests at the source instead of relying on manual copying or inbox triage.
Web-to-Lead: Capturing Leads from Your Website
How Web-to-Lead Works
When a visitor submits a Web-to-Lead form on your website, the form data is sent via a POST request directly to Salesforce’s servers. Salesforce creates a Lead record with the submitted field values, applies any active Lead assignment rules to route the lead to the correct rep or queue, and optionally sends an auto-response email to the submitter. The entire process happens server-side – no custom API integration required on your end.
Enabling and Configuring Web-to-Lead
- Go to Setup ? Feature Settings ? Marketing ? Web-to-Lead
- Click Edit and check Enable Web-to-Lead
- Set the Default Lead Creator: the Salesforce user who owns leads created via the web form (if no assignment rule matches)
- Set the Default Response Template: the email template sent to form submitters as an auto-response
- Save
- Click Create Web-to-Lead Form to configure the form fields and generate the HTML
Generating the Web-to-Lead Form HTML
- On the Web-to-Lead Form creation screen, select which Lead fields should appear on the form
- Optionally specify a Return URL: the page the visitor sees after successfully submitting the form (a “thank you” page)
- Click Generate – Salesforce generates HTML form code
- Copy the HTML and embed it in your website’s page template, CMS, or landing page builder
The generated HTML form includes hidden fields (oid – your Salesforce Organisation ID, and retURL – the return URL) that identify your org and route the submission correctly. The visible form fields map to standard Lead field API names.
Web-to-Lead Lead Assignment Rules
Once a Web-to-Lead record is created, Salesforce applies the org’s active Lead Assignment Rules to determine who receives the lead. Assignment Rules evaluate the lead’s field values (territory, industry, company size, form source) against a set of conditions and assign the lead to the matching rep or queue. Without an assignment rule match, the lead is assigned to the Default Lead Creator configured in the Web-to-Lead setup.
Web-to-Lead Limitations
- Daily limit: Salesforce processes a maximum of 500 Web-to-Lead submissions per day per org. Above this limit, submissions are queued and processed when capacity is available – or rejected if the queue exceeds the buffer. For high-traffic forms, this limit is a real constraint.
- No duplicate detection by default: Web-to-Lead does not check for existing Lead or Contact records before creating a new Lead. Repeated form submissions from the same email address create multiple Lead records. Deduplication must be handled by assignment rules, post-creation automation (Flow), or a third-party form integration.
- No built-in CAPTCHA: the generated Web-to-Lead form is vulnerable to bot submissions. Salesforce provides a basic CAPTCHA option in the form generator, but it uses an older CAPTCHA format. Modern solutions use reCAPTCHA (Google) or hCaptcha embedded in the form, with form submission validated before the POST to Salesforce.
- Limited form styling: the generated HTML is unstyled – all CSS and design must be applied by the web developer embedding the form
Web-to-Case: Capturing Support Requests from Your Website
How Web-to-Case Works
Web-to-Case functions identically to Web-to-Lead, but creates a Case record instead of a Lead. The submitted form populates Case fields (Subject, Description, Contact Name, Email, Product, Case Reason, Priority), applies the org’s Case Assignment Rules to route the case to the appropriate support queue, and sends an auto-response email to the submitter with their case number and confirmation.
Enabling and Configuring Web-to-Case
- Go to Setup ? Feature Settings ? Service ? Web-to-Case
- Check Enable Web-to-Case
- Set the Default Case Origin: the value that populates the Case Origin field for web-submitted cases (e.g., “Web”)
- Set the Default Response Template: the email template sent to the submitter confirming case creation
- Set the Default Case Owner: the user or queue that receives cases when no assignment rule matches
- Save, then click Generate HTML to create the form code
Web-to-Case and Email-to-Case
Web-to-Case and Email-to-Case are complementary features – both create Cases from customer contacts. Web-to-Case handles form submissions. Email-to-Case creates Cases from emails sent to a support email address (e.g., support@yourcompany.com). Most Service Cloud implementations use both: Email-to-Case for customers who prefer to email support, Web-to-Case for customers who use the support portal form.
Email Auto-Response Templates
Both Web-to-Lead and Web-to-Case send an automated email to the submitter after form submission. The template used is configured in the Web-to-Lead / Web-to-Case settings. Templates are created as Email Templates in Salesforce (Setup ? Communication Templates ? Email Templates). For Web-to-Lead, the template can include merge fields from the Lead record (the submitter’s name, company, the rep’s name from the assignment). For Web-to-Case, the template typically includes the Case Number so the customer can reference it in follow-up communication.
Modern Alternatives to Web-to-Lead
Web-to-Lead works but has limitations that make modern marketing teams prefer dedicated form and integration solutions:
- Pardot (Marketing Cloud Account Engagement) Forms: for Salesforce orgs using Pardot, Pardot forms capture leads with full tracking, progressive profiling, grading, and scoring – and sync to Salesforce Campaigns. Pardot forms are the standard for marketing-driven lead capture at enterprise scale.
- HubSpot Forms (via HubSpot-Salesforce integration): organisations using HubSpot alongside Salesforce use HubSpot forms for lead capture – HubSpot handles the marketing automation, and the HubSpot-Salesforce sync creates Salesforce records from HubSpot contacts
- Typeform / JotForm / Gravity Forms with Zapier: modern form builders connected to Salesforce via Zapier or native connectors – provide better UX, conditional logic, and multi-step forms than Web-to-Lead’s basic HTML
- Salesforce Experience Cloud (customer portals): for authenticated customer support, Experience Cloud self-service portals replace Web-to-Case forms with a full authenticated support experience
Is Salesforce easy to learn for beginners?
Salesforce has a learning curve, but its official free training platform Salesforce Trailhead provides structured paths from beginner to advanced. Most users handle day-to-day tasks within 2-4 weeks. Admin and developer skills take 3-6 months to develop proficiently.
What are the biggest Salesforce mistakes to avoid?
Top mistakes include: over-customizing before understanding your process, skipping user training, importing dirty data without cleansing, and not establishing naming conventions. Avoid these four and your implementation will be significantly more successful.
How often does Salesforce release new features?
Salesforce releases major updates three times per year in Spring, Summer, and Winter releases. Salesforce previews upcoming features in sandbox environments 4-6 weeks before each release.
Does Salesforce offer customer support?
Yes. Support is available via chat, email, and phone depending on your plan tier. Enterprise plans include dedicated customer success managers. The Salesforce Trailblazer Community offers extensive peer and official support.
Can Salesforce integrate with other business tools?
Yes. Salesforce AppExchange offers 7,000+ apps. Common integrations include Slack, DocuSign, Zoom, and ERP systems via MuleSoft.
Common Challenges with Salesforce Web-to-Lead and Web-to-Case Setup Guide and How to Solve Them
Problem: Getting Your Team to Consistently Use Salesforce
Adoption gaps occur when teams revert to old habits after initial training. Fix: Identify the 2-3 daily workflows where Salesforce adds the most value for your specific role. Focus training on those workflows first. Use Salesforce in-app guidance to provide contextual help at the moment of need rather than relying solely on one-time classroom training.
Problem: CRM Data Quality Degrading Over Time
CRM data decays at approximately 30% per year as contacts change roles and companies. Fix: Schedule a quarterly data quality audit. Use Salesforce deduplication tools to merge duplicate records. Establish data entry standards enforced through validation rules. Consider a data enrichment tool like Clearbit or ZoomInfo to update stale records automatically.
Problem: Salesforce Reports Not Matching Actual Business Results
Reports are only as accurate as the data entered. Discrepancies between CRM reports and actual revenue indicate data entry gaps. Fix: Audit closed-won records against actual invoices monthly. Make CRM data the source of truth for commission calculations so reps have a direct incentive to enter accurate data.
The best web-to-record setup is the one that keeps routing simple and dependable. If the form data is messy, the handoff becomes weaker.