Gmail / Outlook Drafts folder
The agent creates a draft reply that sits in your normal Drafts folder. You open Gmail like any other morning, see "Drafts (4)", click in, read, edit, hit send.
An agent doesn't have its own magic UI. It writes the draft into a tool you already use. When you saw "the agent drafts a reply" on the previous page, here's the physical mechanism: which tool, which surface, what the human actually sees and clicks.
Every agent has the same plumbing. It talks to a destination tool over an API, the tool stores the draft, and you review it in the normal interface of that tool. No new app to log into.
Each one is a real surface in a tool you already have. The left side shows roughly what you see. The right side shows the plumbing underneath.
The agent creates a draft reply that sits in your normal Drafts folder. You open Gmail like any other morning, see "Drafts (4)", click in, read, edit, hit send.
The agent authenticates to Gmail via OAuth (one-time setup, you click "allow") and calls users.drafts.create with the recipient, subject, and body it generated.
Gmail stores it in the same Drafts folder you've always used. The agent never sends; it can only create the draft.
Open Gmail like normal. Drafts folder shows a number. Click, scan, edit, send. Or trash it.
Every modern helpdesk has a "draft reply" API. The agent attaches a suggested response to the ticket, your support team sees a yellow banner that says "AI suggested reply" with approve / edit / discard buttons.
The agent listens for new tickets via webhook, looks up the order in your e-commerce system, generates a reply, and calls something like POST /tickets/{id}/draft_reply.
It never auto-sends in the first version. The reply sits in the ticket as a draft until a human approves.
Support team opens the ticket in their normal queue. The draft is already there. One click sends, one click discards.
The simplest setup of all. The agent posts to a dedicated Slack channel like #agent-review with the draft and two buttons. You tap "approve" from your phone in line at the supermarket. The agent then does the action.
The agent posts to Slack using chat.postMessage with "interactive blocks" (Slack's name for buttons). When you tap a button, Slack sends a webhook back to the agent telling it what you chose.
This is the lowest-friction setup for a first agent. Slack is free, the API is mature, your phone notifies you.
Tap the button. Slack tells the agent your choice. The agent then sends the email (or whatever the next step is) and posts back "✓ sent at 07:15".
For higher volume or more structured work, you don't want 200 individual Slack messages. The agent writes each pending item to a table. You open the table once a day, scan the rows, batch approve.
The agent writes each item to an Airtable base, a Notion database, or a small custom page. Each row has the agent's draft plus an "approve" and "reject" column you tick.
A second small job watches the "approved" rows and executes them. Or the agent polls the table itself every few minutes.
Once or twice a day, scan the queue, tick the boxes. Five minutes total for what used to take an hour.
For agents reviewing written work (compliance checker, brand voice editor, copy reviewer) the natural place is the document itself. The agent leaves a comment on the relevant paragraph with a suggested rewrite.
Whey Protein 2kg is our flagship product.
It boosts your immune system and supports lean muscle growth after every workout.
Trusted by 12,000 athletes.
The agent reads the doc via the Google Docs or Notion API, runs its check, and posts comments using the same API.
Suggestions appear as native Google Docs suggestions, which the doc owner can accept or reject with one click.
Open the doc. Comments sit in the margin like a colleague's review. Click "accept" to apply the rewrite, or reply to push back.
For agents that produce work for a person to do later (meeting action items, lead followups, reorder requests), the draft becomes a task assigned to the right person with all context attached.
The agent calls the task system's API (ClickUp create_task, Asana POST /tasks, Linear issueCreate) with the title, owner, due date, and a description that includes the source.
You can also use this pattern for CRM updates: the agent writes a "next action" field on a deal record rather than creating a separate task.
The task appears in your normal task list. You see it during your morning planning, do it, mark it done. No new place to check.
Match the destination to the kind of decision the agent is making and how often it happens. The single most common mistake is putting high-volume work in a Slack channel, where it drowns.
| Destination | Best for | Volume tolerance | Setup difficulty |
|---|---|---|---|
| Gmail / Outlook draft | Outbound emails: AR chasing, follow-ups, replies | Low to medium (under 50/day) | Easy |
| Helpdesk draft reply | Support tickets | High (built for it) | Medium |
| Slack channel + buttons | Alerts, single decisions, urgent stuff | Low (under 20/day or it gets noisy) | Easy |
| Approval queue (Airtable etc.) | High-volume routine decisions | High (hundreds/day) | Medium |
| Doc / Notion comment | Reviewing written content | Medium | Medium |
| Task / CRM field | Work that becomes someone's next action | High | Easy |
If you've never built one of these, here's the path of least resistance.
Create a channel called #agent-review. Have your first agent post drafts there with two buttons: approve and skip. That's it. You'll have it running in a day. When approve is tapped, the agent goes and does the thing (sends the email, creates the task, updates the record).
Live with this for two weeks. You'll learn three things: which decisions you always approve (those can later be automatic), which the agent gets wrong (the prompt needs work), and how many items per day is the right volume.
Once you know the volume, pick a more permanent home: helpdesk for support, an approval queue for high-volume routine work, Gmail drafts for outbound emails. The Slack channel stays as the "anything new" home for any future agent's first month.
boosts your immune systemcontributes to normal immune system function*