Frontline Max · Activity · Real product recording

Max connected operations

Follow a real connected Max operating loop across Gmail, Calendar, Activity, task preparation, settings, Directory, and connected systems.

Real product recording4 min

Product contextTo-do's with pending and completed operational tasks
Use this state to review what Max surfaced, what work moved forward, and which source context should be checked before acting.

Real Max screen

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.

Step stateMax connected operations completed state
Use this state to review what Max surfaced, what work moved forward, and which source context should be checked before acting.

Summary

Follow a real connected Max operating loop across Gmail, Calendar, Activity, task preparation, settings, Directory, and connected systems.

ProductFrontline Max

ModuleActivity

CategoryActivity

Concepts covered

ActivityFrontline MaxAI ActionsAssistant activity historyGenerated summariesOperational contextProductivity

Step breakdown

Start from connected HomeReview Gmail, Google Calendar, Activity preview, and time saved as live operational context.
Inspect ActivityRead AI-generated email labeling as evidence: action type, timestamp, source context, and generated summary.
Turn context into tasksUse To-do's to see pending work, completed work, due dates, related records, and teammate ownership.
Review settings and connectionsCheck email labeling, drafting, follow-up controls, Directory handoff context, and the connected app data flow.

About this walkthrough

This lesson uses real connected Max state: Gmail and Google Calendar are connected, Activity contains AI-generated email labeling, To-do's shows pending and completed work with related records, Settings controls email behavior, Directory supports handoff context, and Connections explains the data flow.

Operational playbook

Use Max connected operations 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.

Transcript

Open searchable transcript

Max now starts from real connected operational state. Gmail and Calendar are connected, Activity is populated, and Max can turn incoming signals into summaries, tasks, and follow-up. The Home view already teaches the operating loop: a new email arrives, Max labels it, summarizes why it matters, and keeps the source context visible. Activity is the flagship learning surface for Max. It shows AI-generated work as an operational timeline: what happened, when it happened, and what Max concluded. Read the activity item like evidence. The date, action type, and generated summary explain how Max interpreted connected email without hiding the reasoning. To-do's turns connected context into execution. The real To-do's surface separates pending and completed work, shows due dates, related records, assignees, and the Create task control. A useful To-do's review starts with real operational state: a pending investor report, a completed pipeline review, the related record, and the teammate responsible for follow-through. Settings explain how Max should use connected data. Email labeling, drafting, and follow-up controls make AI behavior inspectable before it affects work. These controls connect learning to trust. Users can see which email behaviors are enabled, what Max may draft, and when follow-up suggestions should appear. Directory gives Max organizational context. Even when contacts are still being built out, this surface teaches where ownership and handoff context will live. Use Directory alongside Activity and To-do's when work needs a person, owner, teammate, or escalation path. Connections are the source layer. Gmail and Calendar give Max the operational data it needs for summaries, activity, task suggestions, and meeting preparation. Connected apps are not setup decoration. They explain the data flow: messages and meetings enter Max, Max creates summaries and suggested actions, and Activity records the result. The completed Max system is easy to trace: connected email creates a summary, Max suggests or prepares work, and the Activity timeline records the operational outcome. Use this page as the blueprint for teaching Max: connected systems, AI-generated summaries, suggested work, and operational history in one visible loop.

FAQs

Why is Activity the flagship Max learning surface?

Activity shows AI-generated work as an inspectable timeline: connected email arrives, Max labels and summarizes it, and the result remains visible for review.

How do Connections change the Max experience?

Connections such as Gmail and Google Calendar give Max real operational signals for summaries, task preparation, suggested follow-up, and Activity history.

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.