# Messaging and email workflows

When a messaging or email connection is available, Neo can help inspect relevant threads, draft replies, and perform approved communication workflows. Availability depends on your connected services and permissions.

## Read the right context

Identify the thread, recipient, account, and time period. Similar names, forwarded messages, and long threads can create ambiguity. Ask Neo to summarize the relevant context before drafting.

## A safe workflow

1. Identify the correct thread and recipient.
2. Read enough context to understand the request and prior commitments.
3. Draft the response without sending it.
4. Review recipients, content, links, and attachments.
5. Confirm the exact external action when consequential.
6. Report submission and delivery status separately.

## Draft in context

> Review the latest thread with the account team, summarize the open questions, and draft a reply that answers only the items covered by the attached brief. Mark anything else for my input. Do not send.

## Before sending

Check:

- To, Cc, Bcc, and reply-all behavior;
- the account or identity used to send;
- names, dates, amounts, and commitments;
- attachments and sharing permissions;
- links and personalization fields;
- sensitive or quoted material;
- whether the requested approval applies to this exact version.

## Status language

“Drafted,” “authorized,” “submitted,” and “delivered” describe different states. Neo should not claim a message was sent or delivered without confirmation from the connected service.

## Security

Never share passwords, API keys, recovery codes, or authentication codes in a conversation. Treat unexpected requests for credentials or urgent transfers as suspicious and verify them through an independent channel.