Managing AI-generated tasks
Use To-do's to review tasks Max created or suggested from connected email, calendar context, summaries, and operational activity.
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 To-do's to review tasks Max created or suggested from connected email, calendar context, summaries, and operational activity.
Concepts covered
Step breakdown
- Open To-do'sStart in the To-do's 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
To-do's is Max's execution queue. It shows work that needs a human decision: pending tasks, completed tasks, ownership, due dates, related records, and follow-up that came from connected context.
The key screenshot is the pending/completed task view. Use it to explain that Max is not just summarizing work; it is helping work become reviewable, assignable, and complete.
How operators use it
Open a pending task, confirm the owner and related record, read the source summary, then decide whether to complete it, edit it, delegate it, or create a new follow-up.
Completed tasks are useful too: they show what already moved, so a teammate does not repeat the same review.
Operational examples
A generated investor-report task appears after Max summarizes related activity. The operator checks the due date and owner, opens the related record, then completes the task once the report is sent.
A completed pipeline review stays visible so the sales lead can see that Max-supported work already happened and continue from the latest state.
Product context
To-do's is where Max turns context into visible execution. Tasks may come from generated summaries, connected tools, assistant activity, or manual follow-up.
The section exists so users can decide what should be accepted, edited, delegated, completed, or ignored.
Operational example
The real To-do's surface separates pending and completed work. A teammate can review a pending investor report, a completed pipeline review, the related record, due date, assignee, and whether a new task should be created.
Operational playbook
Use Managing AI-generated tasks as part of the Frontline Max To-do's 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 To-do's in Max?
Use To-do's to review tasks Max created or suggested from connected email, calendar context, summaries, and operational activity.
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.
How should Max fit into daily work?
Use Max to orient, review activity, confirm suggested actions, and continue execution. It should reduce context hunting and make AI-generated work visible.
When should a suggested action become a task?
Convert a suggestion when the owner, priority, source context, and next step are clear. Edit or dismiss suggestions that lack enough operational context.
How do Max and Studio workflows work together?
Studio workflows move operational processes. Max helps teammates review what happened, understand activity, and decide which follow-up or task deserves attention.