Pipedrive Web Forms can send website enquiries directly into your CRM as leads or deals. For a small business already using Pipedrive, that gives the person handling enquiries a practical place to start. Decide what happens to each submission before building the form. LeadBooster overview.
Table of Contents
Check LeadBooster access before you start
Web Forms belongs to LeadBooster. Pipedrive currently includes that package on Premium and higher plans; Lite and Growth can add it separately. Check your account’s subscription before assuming you need an upgrade or another form service. LeadBooster also includes Chatbot, Live Chat and Prospector; Web Visitors is separate. Current package details.
Choose leads or deals deliberately
A lead represents an early sales opportunity and must connect to a person or organisation. The person’s email and telephone number belong to the contact record; the enquiry has its own context. One person can have several opportunities. Pipedrive’s record explanation.
Our recommendation for a general contact form is to start with leads when somebody still needs to qualify the request. Use a deal destination when the submission meets your team’s agreed threshold for entering the pipeline. A submitted question alone does not establish a qualified sale.
Illustrative example: a training company receives requests about course availability. Each request starts as a lead. Staff confirm the organisation’s needs before creating a deal for a specific booking. Keep the request’s details separate from the person’s enduring contact information.
Build a short form with clear destinations
Setup requires deals admin permission. Open Leads → Web Forms → New Web Form, choose a template and create the form. Add input blocks for the details you need, selecting the intended Pipedrive field. Text, single-choice and multiple-choice custom fields are among the supported types. Form setup guide.
Create missing fields under Personal preferences → Data fields, choosing the correct entity first. Leads share deal fields. Field types cannot be changed after creation, so settle the answer format before accepting real submissions. Our Pipedrive custom fields guide covers the broader design decisions. Official field instructions.
For the training example, a suggested starting brief is name, work email, course of interest and a short explanation. Keep the requested course on the opportunity, and contact details on the person. Before launch, record each question’s destination field so a colleague can verify the resulting records without guessing.
In the form’s submission settings, select how responses are saved and configure the acknowledgement or redirect. Set a realistic expectation for a reply. Check the preview’s labels and styling. Images added inside the form appear on the standalone shared version, not the embedded version. Submission and display settings.
Separate enquiry details from newsletter choices
Pipedrive’s privacy-field instructions recommend separate person fields for different permissions. They describe single-option fields with at least two choices, or a multiple-option field when displaying only one choice. You can link relevant documentation from the form text.
For an enquiry form, keep a newsletter choice optional and distinct from the request itself. Check that declining it still allows an enquiry through. Have whoever handles your privacy obligations review the wording and intended use of the data; the presence of a checkbox does not establish compliance.
Check spam protection and embedded scripts
Enabling spam protection uses Google reCAPTCHA and its cookie. Embedded forms also use Cloudflare bot protection, and Pipedrive documents a tracking script for form engagement. Its Web Forms do not automatically recognise consent-platform signals. Where consent is required before loading those scripts, the website must handle that gating. Pipedrive’s cookie and tracking details.
Ask the person maintaining your website to check the actual page with your consent configuration. Test the permitted and declined states and make sure visitors can understand how to contact you if the form cannot load. Treat spam protection and privacy configuration as separate checks.
Rehearse the visitor journey before sharing widely
You can distribute a form directly or embed it in your website. Choose the route visitors will actually use; a successful standalone preview does not verify the surrounding website page. Pipedrive’s sharing options.
The following are suggested acceptance checks, not results from hands-on testing:
- Use clearly labelled sample details on a phone and desktop. Check that the questions remain readable and the submission control is easy to reach.
- Try the intended optional choices and inspect any validation messages before correcting the form.
- Submit through the real page or shared link, then compare the saved enquiry and contact information with your written field map.
- Check the acknowledgement or destination page explains the next step. Remove sample records once the review is complete.
Give new enquiries a clear next action
Open the new item in Leads Inbox and inspect its owner, person and organisation details. The lead panel supports notes and scheduled activities. Agree who checks incoming enquiries and who covers absence; a saved record needs someone responsible for responding. Leads Inbox documentation.
For the training company, a suggested first action is to clarify the requested course and attendee requirements. Record what was agreed, then convert a qualified lead into the appropriate deal pipeline. Our Pipedrive activities guide explains how to organise the continuing follow-up.
Review submissions and keep the form active
The form dashboard reports views, interactions, submissions and conversion. Conversion measures the share of views resulting in submission; it does not tell you how many enquiries became customers. Compare these figures with the quality of the records your team receives. Performance and status definitions.
When replacing a form, update the pages and links that use it before deactivating the old version. Pipedrive warns that an inactive form appears as a broken link to visitors. Review the route from enquiry to response after each substantive change, including changes to the fields staff rely on.
Sources reviewed 7 October 2026 against official Pipedrive documentation. The training-company example and acceptance checks are illustrative recommendations.
