Run Your First Command Center Review

This workflow turns the Assistant home into a repeatable operating review. The goal is not to ask as many questions as possible. It is to identify one material issue, verify it against the records, and leave an owner and durable result.

Prerequisites

• You can sign in to an Eigenn team workspace.
• Bank, accounting, invoice, payment, inbox, or customer sources relevant to the review are connected in Marketplace.
• Recent syncs have completed.
• Someone is responsible for Workspace → Approvals.

1. Confirm Source Readiness

Open Marketplace and check the apps that should supply this review. Then open the detailed finance pages and verify that recent balances, invoices, and transactions exist.

Do not treat an empty Assistant tile as proof of a clean business state. On the first review, a $0, 0, No data, or Not run value should trigger a source check.

2. Open Assistant

Choose Assistant in the primary sidebar.

Before sending a message, scan:

• Today's briefing,
• Business command center,
• the selected specialist mode,
• the connected-app chips, and
• the Get set up checklist when it appears.

The setup checklist can guide you through Connect a bank, Set up automatic chasing, Run your first cash forecast, and Set a cash-floor alert. A skipped step remains available later.

3. Read Today's Briefing

Work the groups in this order:

1. Needs attention for overdue invoices, approvals, or new Workspace items.
2. Focus today for the highest-leverage action.
3. Highlights to confirm what has improved.

Choose one item to hand its prepared prompt to Assistant. If the item also links to a product page, open that page and keep it available for verification.

If the briefing does not appear, continue with the command-center widgets. The briefing hides when no source produces a usable signal.

4. Validate the Business Command Center

Review these live-backed widgets first:

1. Cash balance
2. Runway
3. Open invoices
4. Overdue receivables
5. Transactions
6. Inbox
7. App health

Use Open finance view to verify cash and account detail. For multiple currencies, rely on the detailed view rather than the single home total.

Then use the action widgets—Collections queue, Budgets, Time tracked, and Notifications—only when they support the decision you are reviewing.

5. Choose the Right Mode

Use one mode for the first question:

• Cash control for runway, burn, working capital, or payment timing
• Collections for overdue accounts and recovery work
• Documents for attached receipts, invoices, contracts, or page data
• Workflows for a recurring process and its approval or failure handling
• Autopilot when the question spans multiple areas and should be routed automatically

The first review is easier to audit when the question has one primary objective.

6. Scope Connected Apps

Choose Connected apps in the composer and select only the sources needed for the next request. You can also type recognized mentions such as @gmail or @slack.

App scoping affects the next request. It does not install the app, and selecting New chat clears the selected apps.

For a file-based review, attach up to five supported images or PDFs. To use data from a workspace page, type @page at the end of the composer and choose a page that contains data blocks.

7. Ask a Decision-Ready Question

Include the period, decision, and desired evidence. Good starting prompts already shipped in the command center include:

• Review cash position and explain the main risks.
• Explain runway and the top moves to extend it.
• Review open invoices and prioritize next actions.
• Build a collections playbook for overdue receivables.
• Review transactions that need categorization or receipts.
• Run a forecast risk scan and summarize the next decision.

Add your constraint, for example: “Use the next 13 weeks,” “separate confirmed facts from assumptions,” or “draft only—do not send.”

8. Review the Response and Tool Activity

Wait for the response to finish. Review the specialist and tool activity, supporting links, and any structured result.

If an analysis opens in Assistant canvas:

1. check its title and As of time when shown,
2. compare the values with the source page,
3. use Refresh when the result has a saved source call and needs current data,
4. use tabs to compare stacked analyses, and
5. ask a follow-up about a specific row or result before accepting the conclusion.

9. Verify the Material Facts

Open the page that owns each important number:

• Overview or Finances → Overview for the decision summary
• Invoices for invoice state and amount
• Receivables for collection work
• Transactions for categorization and evidence
• Finances → Reports for revenue, profit, burn, and spend detail
• Finances → Forecast for scenario assumptions
• Settings → Account → Bank Connections for connection problems

Resolve any disagreement in the source record. Do not change the source merely to make it match the Assistant answer.

10. Review Proposed Actions

Open Workspace → Approvals.

1. Filter to Open.
2. Select the relevant proposal.
3. Review what approval will do, the amount, context, and runway impact.
4. Choose Claim if you own the decision.
5. Choose Approve or Reject.
6. Wait for Done or Failed before treating it as executed.

Use Undo only when it appears and the undo window is still open.

11. Preserve the Review

Choose the preservation method that matches the result:

• Keep on home for a sourced analysis you want to rerun from Assistant
• Pin for a frozen snapshot that should survive chat retention
• Add to page for a living workspace document
• Share for a read-only public snapshot
• Save as decision on supported affordability, pricing, or hiring results

Use Chat history to browse conversations by their generated titles, search recent work, resume a conversation, or start New chat. Older chats are cleaned up automatically, so preserve material results separately.

12. Close the Loop

Record:

• the decision,
• the owner,
• the next checkpoint,
• the source pages used for verification, and
• whether any approval is still Approved, Executing, or Failed rather than Done.

Return to Overview and confirm that the remaining Do these first queue matches the work that is still open.

What Success Looks Like

Your first Command Center review is successful when:

• source readiness was checked before analysis,
• one decision-ready question was asked in the appropriate mode,
• material values were verified outside Assistant,
• every consequential action was reviewed in Workspace → Approvals,
• the result was pinned, added to a page, kept on home, shared, or saved as a decision when needed, and
• a named owner and follow-up point exist.

Troubleshooting

Assistant says I am signed out or my session expired

Choose Sign in, return to the team workspace, and reopen Assistant. Assistant chat requires both a user session and team context.

Message limit reached

Wait a few minutes before sending another request. The composer shows remaining-message warnings as the limit approaches.

A connected app does not appear in the answer

Confirm the app is installed in Marketplace, then select it under Connected apps or mention its recognized slug in the request.

A response has no canvas

Not every answer produces a structured analysis. Continue in the transcript, or ask for a table, comparison, chart, or other structured output when appropriate.

Refresh creates another tab

This is expected. Refresh keeps the prior analysis and adds the new result to the canvas stack so you can compare them.

An approval remains Approved

Approval and execution are separate. Check Done and Failed, then ask support to confirm proposal processing if the status does not advance.

A shared result does not update

Share links are frozen read-only snapshots. Create a new share after refreshing the analysis when recipients need current values.

Related Docs

• Assistant Command Center
• Assistant Automation
• Configure Assistant Operations
• Overview
• Weekly CFO Review
• Connect Records