AI Email Forwarding: Summaries, Original Attachments and Limits

AI forwarding can add a generated summary to an outgoing email. The original message is also attached. It is a convenient way to give a recipient a shorter introduction, not a way to share only selected information from the source.

Configure a category’s forwarding action

Choose the recipient and an optional instruction, such as “summarize the vendor update in two sentences and mention any stated deadline.” Test on non-sensitive messages first. Summary accuracy and length depend on the input, instruction and model; check dates and omissions against the original.

The forwarding action can be combined with other category actions. Forwarding itself does not remove the source message, but another configured action can move or delete it. Inspect the complete action list.

What the recipient receives

An instruction like “include only the deadline” does not redact the attachment. Verify that the recipient may receive the complete source, including any content or attachments within that original message.

Model processing and recovery

Generating the summary involves sending message information to the configured model endpoint. This is a different operation from category classification and can involve more text than its limited preview. Review your model setup and the recipient before enabling forwarding.

The action record can indicate AI use or a fallback reason. It is not proof that every outgoing message contains a generated summary. SMTP or message-fetch failures can also stop the action.

A delivered copy cannot be recalled by undoing a folder move. See action-history limits. For a lower-risk start, organize newsletters into a folder and inspect them before sharing. Pricing explains the plans.