Scope
This guide covers daily operation for Forms & Lead Widgets. Availability depends on your tenant package, role and configured providers.
Purpose
Collect structured enquiries from embedded conversion surfaces.
Publish widgets and review submitted lead context.
Before you start
Correct tenant and project selected
Required source or provider is available
An accountable owner is identified
Test data can be separated from live activity
Procedure
- State the operating objective and the record, audience, campaign or project in scope.
- Publish widgets and review submitted lead context.
- Inspect the current status and supporting context before changing anything.
- Account for system behaviour: Route submissions to owners, segments, journeys or workflows.
- Resolve failures, missing data or approval requirements before continuing.
- Close the loop: Measure views, starts, submissions and downstream quality.
Verify the result
Measure views, starts, submissions and downstream quality. Confirm that the intended record, state, run or report is visible to another authorised operator and that its next owner is clear.
Completion checkpoint
The capability is in the intended state, evidence is current, exceptions are owned and the next action can be understood without a separate status message.
Controls and limitations
Protect PII, validate consent and restrict sensitive fields. Predictive, attribution and recommendation outputs support operator judgement; provider and data limitations remain relevant.