Reply-first: summarize inbound, then draft the reply.
Email Reply-first — summarize inbound email and attachments, then draft a strategic reply. Tone stays with the rep. History is available across tools.
Start from the inbound message and attachments. Summarize, then draft.
The draft answers the thread — not a cold-email template pasted into a reply.
Tone and cadence stay with the person sending. No generic AI sign-off.
Email threads sit in the same history surface as the rest of the suite.
Paste or load the email and attachments. The assistant reads the thread first.
Reply-first: understand the ask, then write the reply.
generateReply({ thread, attachments })Copy to Gmail or Outlook. Your mail client stays your mail client.
Custom timeline. Custom builds are scoped per project — not a white-label SKU. Your data stays in the Google Cloud project we agree on.