Start with the morning briefing.
You open the app and do not know where to look first. Open your company workspace to see recent activity and work needing attention. Check when each department was last updated before treating its figures as current.
Summarize recent activity, work waiting for review, and the three issues I should investigate first. Identify missing or outdated information.

Choose a department and a concrete task.
A vague request gets a vague answer. In Customers, review the opportunities that need follow-up. In Finances, inspect the latest recorded income and expenses. In Content, move an idea into a draft. In Messages, work through inquiries that need a response.
Draft a follow-up for this prospect using our recorded conversation and approved service description. Do not invent a price or promise a delivery date.
Review proposed work.
AI work you cannot check is work you cannot trust. Read the result and inspect any proposed file changes. Use the risk indicator to help prioritize review, then approve, request changes, or discard the proposal.
Keep the introduction. Shorten the proposal, remove the unconfirmed deadline, and ask one clear question at the end.
Saving a draft and sending it are separate steps. Check the workflow before taking an external action.

Keep your company knowledge useful.
Your AI works from what it has been told, so out-of-date facts make out-of-date drafts. Maintain the company profile as your products, customers, team, and operating rules change. The quality of later work depends on the information available to it.
Record why a decision was made.
Months later, nobody remembers why you chose it. Save the choice, the alternatives considered, and the reason behind it. Include what new information would justify revisiting it.
Prepare a decision note from this discussion. Separate the decision, the supporting evidence, and the assumptions we still need to test.
Maintain operational records.
Summaries are only as good as the records behind them. Review department updates against their source information. Keep customer stages, content status, and financial entries current so later summaries reflect the business as it is.
Turn useful tasks into repeatable workflows.
If you do the same task every week, you should not have to set it up every week. Once a task produces a useful result, reuse an appropriate skill or configure a recurring job. Monitor the run status and review its output.
Local background work depends on the app, computer, and required connections being available. Closing the window can leave work running; quitting the app stops its local processes.

Use the assistant your way.
Some people would rather type and some would rather talk. Type a request or use supported voice input. Choose your assistant’s language, tone, and voice settings. Voice processing depends on the selected provider and configuration.
For technical work, Advanced mode exposes terminals, agent workspaces, skills, and connection configuration.

Switch companies deliberately.
If you run more than one business, one mixed-up workspace gets confusing fast. Keep each business in its own workspace. Before sharing context through Company Strings, inspect what will become available to the other workspace. Cross-company questions should use only the scope you intend.
Check the system when something looks wrong.
When something looks off, you should not have to guess why. Use System Doctor to inspect company files, record validation, repository status, and connector readiness. Review suggested repairs before applying them.
