Start from Home for your day, or open an account for the full relationship context. This guide describes the experience when customer memory is enabled.

Review your day

Your agenda shows work planned for the selected day and your meetings. Review Deadline approaching, Overdue, and Backlog to decide what to work on next. Use the member selector when you need another teammate's view. Select an account row to open its work and context directly from Home.

Planning and deadlines serve different purposes:

Add to my day chooses when you intend to work on an item.
Deadline records when it is due.
Moving work into today's plan does not mean the customer agreed to a different deadline.

Open the item's date controls to change either date. Use the assignee control when another teammate should own the next action.

Read an account

The account view organizes open work into Today, Upcoming, Overdue, and Backlog. Also on this account shows work outside your own list. Waiting on them separates customer-side dependencies from work your team needs to do.

The background provides People, Now, and Watch context when available. Read it alongside the open work: a stakeholder change matters because it can change who should receive the proposal or supply the missing evidence.

Inspect the evidence

Expand a work item to see its timeline and source references. Open a reference to review the underlying conversation. Look for later developments that narrow or qualify an earlier statement.

For example, “the fix is deployed” and “the customer passed acceptance” are different facts. Before marking a rollout complete, check which one the source actually supports.

Ask for help with the context attached

An expanded item may offer suggested assistance. Choose an action to open the Assistant with the relevant context. Ask about this opens a chat with the item's context attached when you want to direct the work yourself.

Make the desired outcome explicit:

Draft a reply to Elena acknowledging the missed pack deadline. Separate verified results from assumptions, name the outstanding Payroll dependency, and propose the next checkpoint. Do not imply that the renewal is approved.

Inspect the attached references and the response. A draft remains a draft until a sending action is actually completed. See Assistant approvals.

Review the finished brief

Ask for the decision you need to support, the reporting date, and the evidence standard. For the Pfizer account:

Prepare a renewal decision brief as of September 22. Use only the eight live pilot labs. Separate measured adoption and rework from Operations' capacity estimate and unvalidated agency savings. Include the Finance deadline, Payroll owner, sponsor handover, and next actions. Cite the original conversations. Keep renewal approval open.

Cust's resulting document brings those threads together. Before using it, review four things:

Decision and scope: the $144,000 renewal and eight-lab baseline, with the ten unlaunched labs excluded.
Evidence: adoption and rework are measured; 320 capacity hours and 96 avoided agency hours remain estimates. Jon's export verification closes only the data-integrity check.
People: Grace supplies Payroll and takes over the operating rollout; Elena retains the purchasing decision.
Next action: each checkpoint has the right owner and date, including the September 24, 16:00 final pack deadline.

Open a source reference to check the original wording and later updates. Ask Assistant to revise a claim or deadline when the evidence calls for it. The narrated walkthrough follows the complete route from Home to this result.

Close, dismiss, or reopen work

The control depends on who owes the next step and whether the item is a task or a commitment read from the account's history.

Item	Ownership and planning	Finish or remove it	Review it later
Tracked commitment on your team's side	Use the assignee, planned day, and due-date controls	Select Mark as done, or More → Dismiss when it no longer needs action	Open Recently closed, expand its history, and use More → Reopen or the Reopen checkbox
Task	Use the task assignee, planned day, and due date; More → Edit opens task editing	Select Mark as done to complete it, or More → Dismiss to remove it from open work	Review Recently closed and use Reopen when more work is needed
Customer dependency in Waiting on them	The statement names the customer-side obligation; it is separate from your team's plan	Select Resolve when the obligation is satisfied; Undo is briefly available	Resolved dependencies leave this section. Review the customer's reply in Interactions; there is no customer-dependency archive or reopen menu here

An Undo option is briefly available after closing an item. Expand it before acting when you need to check the timeline and evidence.

Memory can also resolve a tracked commitment when new source evidence supports that conclusion. For ordinary tasks, it presents a completion or relevance suggestion for you to review. Email reply and follow-up reminders can be dismissed automatically when source evidence resolves all the obligations they were waiting on. Tasks created by an automatically maintained Guidance plan, where enabled, can also close as the plan and supporting evidence change. Review their history and use Reopen if more work is needed.

When something looks incomplete

Work through the source, its account association, and then the interpretation, in that order.

What you see	First check	Next step
The email, meeting, or conversation is absent from Interactions	Confirm that the relevant source is connected and its sync has completed. A meeting entry may exist without its transcript	Follow email and calendar troubleshooting, call transcript setup, or the relevant integration guide
The source appears under a different company	Open the source and inspect its participants, domains, and configured company mapping	Ask the workspace admin to correct the source association or integration mapping. For Slack, check the channel-to-company mapping
The source is on the right account, but the commitment is missing	Read the imported content itself. Check that it contains the promise and deadline you expect, then allow time for memory processing	Activity outside the processed history or unavailable source content may be missing. If the commitment still does not appear, report the account and exact source
The item has the wrong owner, deadline, or interpretation	Expand its history and open both the original evidence and later updates	Correct your team's assignee or dates with the item controls. Use completion, dismissal, or reopening only when the evidence supports that status
A technical fix is closed, but rollout work remains open	Check whether the customer confirmed acceptance separately from the fix	Keep acceptance open until its own criteria are met, as in the Siemens scenario

For a persistent issue, use Assistant feedback. Include the account, source link, conversation date, expected result, and what currently appears. This gives the team a specific interpretation to investigate.