Agent setup
Set up Inbox & Calendar Operator.
Read-only assistant that turns email and calendar context into drafts, prep notes, reminders, and approvals.
First proof
Morning action brief with drafted replies, meeting prep, and follow-up tasks waiting for approval.
Queued job
Intake-to-first-proof packet with source manifest, first run steps, acceptance tests, and approval boundary.
Kickoff pack
Client-ready kickoff message, source request, 48-hour plan, and operator checklist.
What we need
- Gmail scope
- Calendar scope
- Reply examples
- Important contacts
- Escalation rules
Accepted samples
- Gmail labels
- calendar categories
- reply examples
- VIP contact list
Role playbook
Choose owner, operator, or technical admin mode above. The selected role is added to this setup request as a routing hint.
Owner
- First action: Approve the first proof target: Morning action brief with drafted replies, meeting prep, and follow-up tasks waiting for approval.
- Approval focus: Scope, price, payment route, external sends, connector writes, and first production run.
- Success signal: Owner can decide whether the worker saves time, reduces risk, or moves revenue before any recurring claim.
Operator
- First action: Collect the starting source pack: Gmail labels, calendar categories, reply examples.
- Approval focus: Confirm sample quality, missing fields, edge cases, and whether the first proof matches daily work.
- Success signal: Operator can repeat the workflow with less manual checking and fewer missed follow-ups.
Technical admin
- First action: Map the approved source boundary for clinic data before any connector access.
- Approval focus: Accounts, permissions, API/export path, audit logs, vaulting, and rollback plan.
- Success signal: Technical admin can explain what the worker can read, what it cannot do, and how every action is logged.