Productivity · Agent family

AI Productivity Agent Roles

Explore productivity roles that turn communication, schedules, meetings, research requests, and project signals into organized work people can inspect and approve.

Get StartedReview the workflow

Best for

  • Teams managing recurring coordination across email, meetings, projects, documents, and calendars
  • Leaders who want prepared decisions and orderly follow-up while retaining ownership of commitments

Typical inputs

  • Messages, calendars, meeting transcripts, project boards, documents, research questions, and existing procedures
  • Priority rules, participant preferences, due dates, access permissions, source standards, and escalation paths

Input quality determines output quality. Source permissions, retention, and field-level access should be settled before the workflow begins.

Core workflow

Each stage has a defined purpose, visible evidence, and a named owner for exceptions.

1

Frame the request

Collect the communication or coordination signal and identify the responsible owner

2

Gather context

Organize relevant context from permitted calendars, documents, projects, and conversations

3

Prepare the work

Prepare schedules, summaries, research, tasks, or procedure updates in the requested format

4

Review and hand off

Request approval before external commitments and route conflicts to the affected people

Actions it can perform

  • Triage inboxes, propose calendar changes, summarize meetings, track projects, and assemble research briefs
  • Draft follow-ups, capture decisions, maintain SOP changes, flag conflicts, and prepare executive work queues

Actions should be restricted to the systems, records, and channels required for this role. Broader access is not a substitute for a well-designed workflow.

Outputs

  • Prioritized messages, scheduling options, decision records, action lists, project summaries, and source-linked briefs
  • Draft correspondence, procedure updates, overdue-item alerts, and compact review packets for accountable owners

Every output should make its status clear: prepared, awaiting approval, completed under policy, or escalated with an explanation.

Role-specific configuration details

Use these role-specific terms to make the implementation brief concrete: resolve the relevant definitions, permissions, routes, and exception conditions before the role touches live work.

  • explore-productivity
  • productivity-roles
  • turn-communication
  • communication-schedules
  • schedules-meetings
  • meetings-research
  • research-requests
  • project-signals
  • approve-give
  • clearer-priorities
  • priorities-decisions
  • decisions-schedules
  • follow-through
  • through-without
  • without-allowing
  • make-commitments
  • commitments-outside
  • outside-delegated
  • delegated-authority
  • authority-messages
  • messages-calendars
  • calendars-meeting
  • meeting-transcripts
  • transcripts-project
  • project-boards
  • boards-documents
  • documents-research
  • research-questions
  • existing-procedures
  • procedures-priority
  • priority-rules
  • rules-participant
  • participant-preferences
  • dates-access
  • access-permissions
  • escalation-paths
  • paths-collect
  • coordination-signal
  • organize-relevant
  • permitted-calendars
  • calendars-documents
  • documents-projects
  • conversations-prepare
  • prepare-schedules
  • schedules-summaries
  • summaries-research
  • research-tasks
  • procedure-updates
  • requested-format
  • format-request
  • before-external
  • external-commitments
  • route-conflicts
  • triage-inboxes
  • inboxes-propose
  • propose-calendar

Human approval and escalation

Approval boundary

People approve messages sent in their name, calendar commitments, priority changes, task ownership, final research conclusions, and published procedures.

Escalation rule

Confidential material, conflicting instructions, sensitive relationships, unclear authority, and schedule tradeoffs are returned to the appropriate person.

What remains under human control

  • Individuals control access, priorities, communication style, scheduling preferences, and what may be shared
  • Managers assign ownership, resolve tradeoffs, approve commitments, and determine whether research or procedures are sufficient

Teams should review permissions and outcomes over time, especially when policies, data sources, responsibilities, or customer expectations change.

Recommended integrations

Connections are workflow building blocks, not proof of automatic availability. Confirm authentication, permissions, supported actions, and error handling during implementation.

Google WorkspaceReview integration scopeMicrosoft 365Review integration scopeNotionReview integration scopeSlackReview integration scope

Example workflow

After a recurring leadership meeting, specialist roles prepare decisions, project actions, calendar holds, and follow-up drafts; owners verify commitments before distribution.

The implementation should record the source, owner, decision boundary, and recovery route for each important stage. That makes the workflow easier to review and improve without hiding responsibility.

Related agents

Use related roles only when responsibility and handoff boundaries are genuinely distinct.

Email Assistant

See the responsibilities, controls, and handoffs for this related specialist role.

Explore Email Assistant

Related use cases

Explore outcome-led workflows that can combine this role with approved systems and human review.

Design a responsible AI Productivity Agent Roles workflow

Define the sources, controls, connected tools, exceptions, and owners before implementation.

Get Started