Leads and enquiry forms

Use Leads to manage enquiries before opening a case. Each pipeline has its own stages. A lead records the enquiry, its owner, priority and collected answers.

Review and follow up

1. Select Leads, then open a pipeline.
2. Select New lead to record an enquiry received by phone or email. Public form submissions appear in the entry stage chosen for that form.
3. Open a lead to review its collected answers. Assign an owner and set a priority under Manage lead.
4. Use Move stage on a board card, or change the stage in the lead, as work progresses.

Use All leads to find enquiries across pipelines. Filters and paging help you return to the records you were reviewing. Select Refresh leads on a board to fetch new enquiries.

Configure a pipeline

A Matter administrator can create pipelines and edit their settings. Staff use the existing Matter roles to work with Leads; there is no separate Leads role to assign.

In a pipeline’s Settings, name and order the stages, choose their colours, and select one initial stage. Mark terminal stages as Converted (won) or Disqualified (lost) when those outcomes fit your workflow.

The default pipeline supplies the starting destination for new forms created without an explicit pipeline. Changing it does not move existing leads or reroute existing forms.

Retiring a stage keeps its existing leads. An occupied retired stage stays on the board so you can move those leads to an active stage. Forms routed to a retired stage stop accepting enquiries. Choose an active entry stage for each affected form and publish it again, or restore the stage.

Build and publish a capture form

1. Open the destination pipeline and select Capture forms → Create capture form.
2. Choose a template, or select Start blank and name the form.
3. In Build, review the questions and required fields. Use Preview to check what a visitor will see.
4. In Publish & share, check Where leads land and the entry stage.
5. Review the protection and embedding settings, then save them.
6. Select Publish form. Open its public link and check the published version before sharing it.

Several forms can feed the same pipeline. Each form has its own entry stage, public link and published version. Saving a draft does not change the public form. Select Publish changes to make saved edits live.

Select Unpublish to stop new submissions while retaining the draft and earlier leads. Rotate link invalidates the old public link immediately; update every shared link and website embed afterward.

Embed a form on your website

Copy the embed code from Publish & share into a page that accepts HTML. The code includes a separate link that visitors can open if the embedded form is unavailable.

By default, any website can embed the form. Add allowed websites to restrict embedding. Addresses match the scheme, hostname and port: https://example.com and https://www.example.com are different websites. Save and publish the settings, then test the actual website page.

An unlisted website shows a browser refusal instead of the form. Turning embedding off blocks all websites from framing it. The public link remains available in both cases. Website restrictions do not make the form private.

Protect public submissions

The hidden trap field rejects submissions that fill a field visitors cannot see. Optional submission limits restrict attempts per visitor or across the form.

The optional human check uses Cloudflare Turnstile. It requires verification to be configured by Neudash before the form can be published with that option. Visitors may need to repeat an expired check. If verification cannot load, they can retry without re-entering their answers.

If a form is unpublished, its pipeline is archived, or its entry stage is retired, it cannot accept a new enquiry. Reopen the form from its current link after the administrator fixes the destination and publishes any routing changes.

Reuse collected details

Open the lead and use Convert enquiry details to create a Contact or Organisation from a populated subject. Review the target and selected details before confirming. The resulting record is linked to the lead so you can continue from it.

Changing a lead to a Converted stage records an outcome. It does not create a case or replace the details-conversion review. Create the case separately when you are ready to engage.

Archive and recover

Archive records when they should leave the active lists. Archiving a pipeline stops new enquiries entering it, including through its public forms. Existing leads retain their stage history.

A Matter administrator can open Workspace settings → General & apps → Recently deleted, select Leads, Lead pipelines or Lead capture forms, and inspect the available recovery action. Recovery is available for six days after archiving. Records become eligible for permanent removal after seven days. The recovery list shows when each record was deleted.

After recovery, review the pipeline and form destination before sharing a public link again.