> ## Documentation Index
>
> Fetch the complete documentation index at: https://lithi.ai/llms.txt
>
> Use this file to discover all available pages before exploring further.

EmailOS prepares a reply draft from an eligible message and approved context, then leaves review, editing, skipping, and sending to you.

## Start with the message

The flow begins with a message in the account you chose. It does not start a new conversation or decide which account you meant.

Check the account and thread before relying on a draft. Keep high-stakes or out-of-scope work outside the preparation flow.

## Choose useful context

EmailOS uses the sources and resources you approve for the local workflow. Context means information that helps explain the message, such as a project item or scheduling detail.

Choose the smallest context that can support the reply. A wider source list does not make an answer more reliable.

Rules set the preparation boundary. They can identify which messages may receive drafts and what the wording should include or avoid.

When you change a source or rule, treat the next draft as a fresh review. Check that the new scope matches the message and purpose.

## Check the draft evidence

Read the draft with the message and visible source details beside it. Ask which message produced the draft and whether the context is current.

A source reference tells you where to look. It does not make incomplete information complete or support a claim beyond the selected scope.

If the evidence is missing, pause. Add only the context that answers the open question, then check the result again.

## Review before saving

Read the complete reply before taking an action. Check the recipient, answer, tone, factual details, and anything your rules say to leave out.

Edit a near match, skip an irrelevant draft, or set it aside when the context needs attention. Approval records your review choice; it is not the same as sending.

Keep the review decision close to the draft. Another person should be able to see why the item continued, changed, or stopped.

## Choose Send yourself

Use the explicit **Send** action in your email workflow when the final reply is ready. EmailOS prepares wording; you decide whether it leaves your account.

If you save a checked draft, confirm the saved state in Mail. A saved draft still needs your final send decision.

## Recover a blocked draft

Incomplete context, changed source data, or an unavailable account can block a draft. Refresh the source and recheck the message before trying again.

If Mail may already have saved a draft, check the Drafts folder before retrying. This avoids duplicate or unverified changes.

For the shorter review path, read [Review and send](/docs/emailos/review-and-send). For setup questions, open [the current setup guide](/docs/get-started).