How Coco proposes replies and how to send them

One of the most useful things Coco does is take a thread that needs an answer and hand you a draft that is already most of the way there. The rule that makes this safe is simple: Coco drafts, you send. Nothing is ever sent on its own.

How a draft appears

When Coco sees a message that looks like it needs a reply, it surfaces a ready-to-go draft alongside it — in the brief, or when you open the thread, or when you ask in the chat. The draft is written in your voice, using what Coco knows about the people and the topic, so it reads like something you would actually send rather than a generic template.

Reviewing and editing

The draft is a starting point, not a final answer. You can read it, edit any part of it, tighten the tone, or rewrite it entirely. You can also ask the chat to redo it — "make it warmer," "shorter," "say I can do Thursday instead." Coco will revise and hand you the new version. Nothing happens to the draft until you act on it.

Sending

When you are happy with it, you send with a single tap. That tap is the approval — it is the only thing that authorizes Coco to actually send mail. Coco asked Google for the ability to send a reply precisely so that this one-tap send works; it only ever uses that permission on the exact draft you approved. See what Coco can do.

Saving instead of sending

If you are not ready, you do not have to send. Coco saves the draft into your account so it is waiting whenever you come back — there is no pressure to act in the moment, and an unsent draft never leaks out.

What Coco will not do

Coco will never send a reply you did not approve, never send to people you did not intend, and never auto-respond on your behalf while you are away. The whole point is that the send button stays in your hands. For the full list, see what Coco will never do.