Sales
Lead Form

Lead Form (Embeddable Lead Capture)

Purpose: The Lead Form lets people outside your workspace submit their details straight into your PMSuite lead list. You publish the form either as an embedded block on your own website or as a standalone link you can share, choose which fields appear, and decide which of those fields are mandatory. Submissions land as lead records you can then work through your normal pipeline.

Who can use it: Configuring and publishing the form is an admin-level task — Company Admins have access by default, and any other role sees it only if Settings → Roles & Permissions allows it. The published form itself is public — anyone with the embed or link can submit it, no PMSuite login required.

Prerequisites

  • Lead Sources configured, if you want the Source field on the form to offer meaningful choices. See Lead Sources & Categories.
  • Products set up, if you want submitters to indicate which product they're interested in. See Adding Products.
  • Lead custom fields defined in advance if you want them available as form fields.
  • A Google reCAPTCHA site/secret key pair if you intend to protect the form with CAPTCHA (see Step 4).

How to Access

Navigation: Sidebar → Sales → Lead Form.

Related lists you'll use alongside it: Lead Contact (/account/lead-contact) for the leads that come in, and Deal / Lead Report (/account/lead-report) for volume reporting.

How to Use

Step 1: Choose How to Publish the Form

The Lead Form is delivered two ways, and you can use both at once:

  • Embeddable iframe — copy the supplied embed code and paste it into a page on your own website. The form renders inside your page.
  • Standalone shareable link — a direct URL to the form, for when you don't want to (or can't) embed it. Useful in email signatures, social posts, ads, and QR codes. Styled and logo variants of the standalone form are available, so the shared page can carry your branding rather than a bare form.

Step 2: Choose Which Fields Appear

The following fields are configurable on the form:

  • City
  • State
  • Country
  • Postal Code
  • Source
  • Product
  • Any custom fields you have defined for Leads

Toggle each one show or hide depending on what you actually need from a first touch.

Step 3: Decide Which Fields Are Required

Each field has its own required/optional setting, independent of its show/hide setting. A field that is shown can still be optional, and you can mix freely — for example, show City, State, Country and Postal Code but make only Country required.

A practical rule: the more fields you mark required, the fewer submissions you get. Keep required fields to the ones your sales team genuinely cannot start a conversation without.

Step 4: (Optional) Protect the Form with reCAPTCHA

⚠️ Both steps are required. CAPTCHA for the lead form needs two separate pieces of setup. If either one is missing, validation fails silently — there is no on-screen error explaining what went wrong.

  1. In PMSuite: go to Settings → Recruit Settings → General tab and configure the Google reCAPTCHA toggle and keys there. This is the correct location — not Sign Up Settings. Mixing these two up is the single most common cause of "my lead form CAPTCHA isn't working".
  2. In the Google reCAPTCHA admin console (google.com/recaptcha/admin): whitelist the domain that actually serves the form. For an embedded form, that's the domain of the page hosting the iframe. Google will not validate a challenge coming from a domain it doesn't recognise.

Do both, then submit a test entry yourself before publishing widely.

Step 5: Publish and Test

Paste the embed code into your site (or share the standalone link), then submit one real test entry. Confirm it appears under Sales → Lead Contact. Testing end-to-end is the only reliable way to catch a half-finished CAPTCHA setup, since the failure mode is silent.

Effect on Other Features

  • Lead Contacts: every successful submission creates a lead record in Lead Contact, the same object you'd get from adding a lead manually or importing one.
  • Deals: submitted leads do not become deals on their own. Creating a deal from a lead is a separate step — see Creating Deals.
  • Clients: a lead only converts to a Client when an associated deal's stage is set to "Win." That is the only trigger for lead→client conversion, and no Project is created automatically at that point. See Deal Stages.
  • Reporting: form-sourced leads flow into the Deal / Lead Report like any other lead, which is why setting the Source field is worth doing — it's what lets you separate web-form leads from other origins.

Limitations

  • The configurable field set is fixed to the fields listed above. Workaround: define Lead custom fields for anything else you need to capture — they become available as form fields alongside the built-in ones.
  • CAPTCHA failures are silent — there's no on-screen error telling you the setup is incomplete. Workaround: treat a test submission as a mandatory part of publishing, and re-test whenever you change domains or reCAPTCHA keys.
  • reCAPTCHA only validates on domains you have whitelisted in Google's console, so moving the form to a new domain silently breaks it. Workaround: add every domain that serves the form (including any custom domain) to the reCAPTCHA admin console, and re-test after each change.
  • The form captures leads only — it doesn't create deals, assign an agent automatically, or start a pipeline. Workaround: review new form leads on a regular cadence in Lead Contact and create/assign deals from there.

Troubleshooting

The CAPTCHA never validates, and nothing tells me why. This is almost always one of the two setup halves being missing. Confirm the reCAPTCHA configuration is under Settings → Recruit Settings → General (people frequently configure Sign Up Settings by mistake), and confirm the form's host domain is whitelisted in the Google reCAPTCHA admin console. Both are required.

I configured reCAPTCHA but it isn't validating on a new domain. Google only validates challenges from domains it recognises. Add the domain that serves the form to the whitelist in the Google reCAPTCHA admin console, then submit a test entry again.

A field I need isn't in the list of configurable fields. Create it as a Lead custom field first; custom fields defined for Leads are available on the form.

Submissions aren't showing up. Check Sales → Lead Contact directly rather than relying on a filtered view — a date or type filter left applied to the list can hide recent entries. If entries are genuinely absent, re-test the form after verifying the CAPTCHA setup above, since a failed validation stops the submission.

I want the form to look like our brand. Use the styled/logo variants of the standalone shareable link, or embed the iframe inside your own page so your site's surrounding layout provides the branding.

Related Articles