Use the AI Workspace

A question about the business often needs both an answer and a way to inspect its evidence. Open AI Workspace to ask, review record links and see the tools and results in run history. Use Ask AI when you want to stay on your current screen.

Ask a question the system can verify

Name the record or time period and say what you need. For example:

Find open opportunities with no next action. Show the company, owner and last recorded contact. Do not change any records.

Read the returned record links and dates. If the answer lacks a needed source, ask for that source or inspect the record yourself before acting. An incomplete answer should stay incomplete until the missing information is available.

Request a change

Ask for one bounded action, such as preparing a reply to a named conversation. Choose Review beneath the answer to inspect the exact recipient, content and changes in chat. Approve or reject there, or use Approvals. After approval, inspect the execution result; approval alone does not establish that the operation succeeded.

Inspect a run

Use run history to find which tools were called, their outcomes and reported usage. This helps distinguish a missing connection, a denied operation and a provider failure.

If a run stops after an external request, inspect its action result before retrying. An uncertain result needs reconciliation to avoid a second send.

When a tool is unavailable

Check its connection requirement in the AI tool reference, then inspect Setup; module settings and your own permissions can restrict access too, independently of whether the connection itself is working, and enabling a connection never grants you additional authority on its own.

Model jobs and evaluation

AI requests name a registered job with capability and context requirements. An operator-selected model or configured fallback must satisfy those requirements. Free and low-cost models need a recorded passing evaluation before running consequential jobs such as the command agent. A fresh installation does not assume that evaluation has happened.

The model-call activity records the requested model, reported serving model and execution state. A started call without a terminal receipt needs investigation; it is not proof of a completed answer. Model availability and evaluation are separate from permission to change business records or send messages, which still follows the approval workflow.

Example: turn a review into an approved next action

Maya at the fictional Northline business wants to identify an opportunity that needs attention.

1. Ask: “Show open opportunities with no next action. Include record links and the date of the last recorded contact. Do not change anything.”
2. Open a returned opportunity and compare the answer with its saved history. If two records could match a name, resolve the identity before requesting a change.
3. Ask for a specific supported change to the chosen record. For example: “Prepare a next-action update for this opportunity: Maya will call on Tuesday, 15 September 2026. Show me the proposal before applying it.”
4. Open Review in the conversation. Confirm the opportunity and date, then approve only if the change is correct.
5. Inspect the execution result and reopen the opportunity. A proposed change or an approval is not yet proof that the update saved.

The example's names and dates are fictional; use your actual record and intended date. Available tools depend on the enabled modules, your access and the configured model. If the operation is unavailable, use the supported admin control or ask your administrator about the missing capability.

If the run stops or access changes

A denied operation must stay denied; retrying does not grant access. Ask the administrator to check your current membership and record permissions. If the model or provider times out, inspect the run and any staged approval before asking it to repeat the work. A stopped run may already have prepared a proposal. An uncertain external action needs receipt review before another attempt, especially for email or invoicing.

Tool discovery can find operations outside the screen you started from. Loading a tool group does not grant permission to execute it. Groups activated during one command run are not automatically remembered in a later run; ask for the task again when needed and review the newly prepared change.

Architect and Blueprints

Choose Architect to describe how your business works and supply the sources needed for one workflow. This opens the Architect conversation in the AI Workspace. Use Help beside the heading for the next steps and this guide. On a phone, scroll inside longer guidance; press Escape or select outside the panel to close it.

Choose Blueprints to review saved proposals, their versions and validation results. Compare the proposed changes with your actual business before approving an exact version. Approval and application are separate steps; a saved proposal does not mean the workspace has changed.