Understanding assistant activity
Use Activity as the flagship Max timeline for AI-generated email labels, summaries, suggested work, and operational history.
Use this state to review what Max surfaced, what work moved forward, and which source context should be checked before acting.
Read the full product state before configuring behavior.
These captures are intentionally larger and quieter: no artificial labels, just the real screen, the controls that matter, and the operational outcome each state changes.
Use this state to review what Max surfaced, what work moved forward, and which source context should be checked before acting.
Summary
Use Activity as the flagship Max timeline for AI-generated email labels, summaries, suggested work, and operational history.
Concepts covered
Step breakdown
- Open ActivityStart in the Activity section of Max to understand the operational context.
- Review the product stateUse the visible UI, screenshots, and concepts to understand why this section exists.
- Apply it to daily workConnect the section to tasks, summaries, activity history, teammate context, or connected tools.
What this screen does
Activity is the operational log for Max. It shows AI-generated labels, summaries, actions, completed work, and the context behind what happened.
This screen matters because AI work needs evidence. Activity gives operators a timeline they can inspect before trusting, continuing, or correcting a next step.
How operators use it
Read the newest activity first, then open the detail to see the generated summary and source context. If the activity implies follow-up, move into To-do's or create the next task.
Use Activity during handoff: a teammate can quickly understand what Max did, what was already reviewed, and what still needs human judgment.
Operational examples
Max labels an incoming email, creates a summary, and records it in Activity. The operator opens the activity, checks the summary, and decides whether a customer reply or owner task is needed.
After a task is completed, Activity becomes the audit trail: it shows that work moved, not just that AI produced text.
Product context
Activity is the inspectable history of assistant work. It helps teams trust Max because actions, summaries, and completed work remain visible after the moment passes.
Use Activity when a user needs to understand what changed, why Max suggested something, or how a task reached its current state.
Operational example
A manager reviews Activity after a busy morning to see which email summaries were generated, which labels Max applied, and which suggested actions should become tasks or follow-up.
Use Activity as the flagship learning area: it shows AI-generated work as evidence, not as a hidden automation result.
Operational playbook
Use Understanding assistant activity as part of the Frontline Max Activity operating loop: inspect the current product state, confirm the source context, and decide what should happen next.
The goal is not to memorize screens. The goal is to understand how the product surface supports repeatable work, AI assistance, and accountable handoff.
Best practices
Start with the operational job before changing configuration. Name the owner, define the trigger or source context, and decide how the result should be reviewed.
Prefer narrow, inspectable setups over broad automation. Teammates should be able to explain why the system took an action from the visible product state.
Troubleshooting
If the result does not match expectation, check the source context first, then permissions, connected integrations, required fields, workflow logs, and any AI-generated output used by downstream steps.
When in doubt, compare the latest product state with the related record, activity, or workflow execution so debugging starts from evidence rather than guesswork.
Review loop
Use Max in a simple loop: orient on Home, review Activity, confirm To-do's, check connected context, then continue work or hand off with a clear next step.
AI-generated work should remain visible in Activity so teammates can audit what happened and avoid repeating context gathering.
FAQs
What is Activity in Max?
Use Activity as the flagship Max timeline for AI-generated email labels, summaries, suggested work, and operational history.
How should teams use this section?
Use it as part of the daily Max operating loop: orient, review context, confirm AI-generated work, and continue execution.
What should I review in Activity before acting?
Review what Max did, the source context, generated summaries, task changes, and whether the action needs confirmation. Activity should explain the path from context to work.
How do I know whether AI-generated work is complete?
Check whether the activity item shows the action taken, the related task or record, and any remaining follow-up. Suggested work should be reviewed before treating it as complete.
How does Activity support operational trust?
Activity creates an inspectable history of assistant work. Teammates can see actions, summaries, and context instead of relying on opaque AI output.
When should Activity lead to a workflow change?
If the same manual review or follow-up happens repeatedly, use Activity patterns to identify a workflow, task rule, or integration that should be automated.