A lead notification is fully configured only when a real test lead appears in the space and the team receives the email. The widget can work technically while notifications remain invisible because of a missing recipient, SMTP settings, spam filtering or an existing lead space.
Enter a recipient address, enable lead notifications, send a test inquiry with an email address through the live widget, then check lead space, status, summary and inbox.
Start with a narrow boundary: which website, space, file, recipient or decision is affected? This makes the task reviewable instead of turning it into a broad catch-all request.
A useful work order is: “Create a checklist for our LeadOS notification with recipient address, SMTP, test lead, spam folder, lead space and handoff mode.” For important cases, add that uncertainties must be marked visibly instead of being filled in silently.
Pay special attention to recipient address, SMTP, spam filter, lead space, AI mode and test message. These points decide whether the result is only useful for the moment or can be found, checked and continued by the team later.
Do not test only in the widget preview. Preview does not replace a real visitor chat on the embedded domain.
A complete test covers the live widget, contact data, lead space, team handoff and email delivery.