Help CenterThe Lead capture section in a web experience lets you prepare fields requested before a conversation starts. Select the employee first, then review the form and the tools available to that experience.
Before you begin
Define why the information is needed and who will follow up. Prepare the minimum fields and consent text appropriate to that purpose. Have your organization's responsible owner review the wording and handling process before collecting real visitor information.
Steps
1. Select the employee
Open Deploy → Web & embeds → Create experience. In Employee & connection, select the intended Employee. Add lead capture form is disabled until an employee is selected.
2. Open the lead form
Choose Add lead capture form. Enter a clear Title and Consent text that explain the purpose and what happens next. The editor describes this as information requested before the conversation starts.
3. Review each field
For each field, review Field type, Label, Placeholder, and Required field. Use a visible label that explains the requested information; a placeholder should not be the only explanation.
Use Add field for another necessary field and the available remove control for an unwanted one. The initial single-field remove control can be disabled. Do not make optional information required simply because the editor allows it.
4. Confirm the form and review tools
Choose Confirm when the fields are ready, or Cancel to leave the editor. Review the parent web-experience form before publishing.
Check Connected tools and the employee's Tools and instructions. Limit actions to the visitor's task. Instructions should identify what must be confirmed and when a person should take over. An instruction to ask for confirmation is not a replacement for limiting access.
5. Test the visitor form and result
After publication, use non-sensitive test data at the actual entry point. Check the title, consent, labels, and required fields before submitting once.
Open Insights → Leads with the intended employee and date range to look for the result. If it is missing, check the submission outcome and filters before trying again. Test an outside action separately and verify its result in the connected service.
Expected result
The form asks only for information needed for its purpose. Before real collection begins, verify the visitor form and the resulting record or destination, including any required confirmation and handoff.
Status meanings
Confirm belongs to the lead-form editor; it is not the web experience's Publish action. A saved configuration does not prove that a visitor submission or outside action has completed.
Usage credit impact
Visitor conversations and connected actions may affect usage. Review current account information rather than estimating the cost of a full session from a single lead submission.
Information stored or shared
Fields may contain personal information. Limit access to submitted details and any downloaded copies. A connected action can pass information to another service. Do not request passwords, payment credentials, or unrelated private records in a lead form.
Limits and permanent actions
Consent text in a product form is not legal approval for a use case. Confirm your purpose, access, and handling requirements with the responsible owner. Sending messages or changing records can have lasting effects; test and limit those actions before making them available to visitors.
Common problems and recovery
- Add lead capture form is unavailable: select an Employee first.
- A field is unclear: use a specific Label, review its type, and make the required setting match the purpose.
- A lead is missing: check the visitor's displayed submission result and the employee/date filters under Insights → Leads before submitting again.
- An action runs unexpectedly: stop using it, review its allowed scope and instructions, and involve the connected service's owner before another test.
Next step
Review connected tools and results in Insights, then complete the safe data checks.