Max overview
Understand Max as the AI teammate layer for daily operational execution: connected context, summaries, tasks, activity history, and follow-through.
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
Understand Max as the AI teammate layer for daily operational execution: connected context, summaries, tasks, activity history, and follow-through.
Concepts covered
Step breakdown
- Start with HomeReview connected Gmail, Calendar, Activity preview, and what Max has already summarized.
- Inspect ActivityUse Activity as the evidence layer for AI-generated work, summaries, labels, and completed actions.
- Move into tasksTurn suggested follow-up, briefs, and generated work into reviewed To-do's.
What Max does
Max is the operational AI teammate inside Frontline. It reads connected work signals, turns them into summaries and suggested work, and keeps the outcome visible in Activity.
The real product loop is simple: connect systems, review Home, inspect Activity, decide what belongs in To-do's, and tune Settings so Max behaves correctly for the operator.
What to look for on screen
Home shows connected Gmail and Calendar state, Activity preview, and time saved. Activity shows AI labels, summaries, and completed work. To-do's shows pending and completed tasks. Settings controls behavior. Directory explains ownership. Connections explains where the signal comes from.
Operational walkthrough
A new customer email arrives through Gmail. Max labels it, summarizes the important context, exposes the event in Activity, and helps the operator decide whether a follow-up task belongs in To-do's.
Before a meeting, Calendar context helps Max prepare the operator. After work happens, Activity becomes the audit trail so another teammate can understand what changed.
Operational outcome
Max should reduce context hunting. Operators should be able to answer: what happened, why it matters, who owns the next action, and which connected system supplied the evidence.
Operational playbook
Use Max overview as part of the Frontline Max Overview 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.
Transcript
Open searchable transcript
FAQs
What is Max overview?
Understand Max as the AI teammate layer for daily operational execution: connected context, summaries, tasks, activity history, and follow-through.
Why start with this overview?
The overview explains how this product area works before users enter a specific screen walkthrough or implementation blueprint.
How does this connect to the Frontline ecosystem?
Each overview shows how Studio, CRM, Max, Channels, AI agents, workflows, and Activity connect into one operating system.
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.