LeadOS separates website, widget and agent deliberately so multiple domains, designs and tasks can be managed in parallel. A common mistake is treating a new widget or website as a single setting. That can overwrite assignments and make the setup hard to understand.
Create the website first, then the widget with design and position, and finally the matching agent with knowledge, tone and handoff rules. A widget belongs to a website but can use its own agent and quick actions.
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: “Review our LeadOS configuration: which website, widget, agent, language, goal and notification are active?” For important cases, add that uncertainties must be marked visibly instead of being filled in silently.
Pay special attention to website, widget, agent, language, design, allowed domains and handoff. 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 mix website data, widget design and agent rules in one field. The separation makes multi-site and agency setups stable.
Clean assignment prevents overwrites and makes LeadOS suitable for clients, agencies and multiple sites.