A new lead space should appear when a visitor chat becomes a traceable contact case with need and contact details. Not every greeting is a lead. Once name, email, phone, company or a clear consultation request is present, the team needs its own work context.
LeadOS collects chat history, detected contact data, source, summary and status in one space so sales or support can continue there.
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: “Define when our widget should treat a visitor chat as a lead and which fields must be visible in the lead space.” For important cases, add that uncertainties must be marked visibly instead of being filled in silently.
Pay special attention to lead criteria, contact fields, source, summary, status and duplicate detection. 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 create new spaces for every short test message or real inquiries will be hidden between noise.
The lead space is the work record for the contact, not only a copy of the chat.