Meet the specialists
Nova is the team lead. Iris focuses on content strategy and Quill. Maya focuses on social content and Amplify. Atlas helps with website intelligence and Pulse. Remy works on customer experience and Relay. Leo helps with websites and landing pages in Launch.
Crew is currently Alpha. Available conversations and actions depend on enabled products, permissions and the context of the selected website.
Ask a useful question
- Select the website you want to discuss.
- Open the relevant specialist or Crew conversation.
- Describe the outcome you need.
- Identify the article, post, report or page involved.
- State constraints and approved facts.
- Review the response and any proposed action.
“Help me compare these two article angles for first-time buyers” provides more useful direction than “improve our marketing”. If an existing record matters, open or identify it rather than assuming the specialist has guessed the right one.
Keep the source of truth clear
Brain supplies shared business knowledge. A chat message is useful working context, but it should not become the only place an important product fact or policy is maintained.
When a conversation reveals a reusable answer, save it through the appropriate Brain editor after review. This helps other supported workflows use the approved information.
Understand the action boundary
A recommendation is not a completed change. Inspect proposals and explicitly approve supported actions through their controls. Product permissions and publishing approval still apply.
Check the resulting record after an action. For publishing, inspect delivery status and the public link. A confident statement in a conversation is not a substitute for the system’s saved result.
If a specialist lacks access to a product or record, correct the context or permissions rather than trying to bypass the restriction in the prompt.