The result you are working toward

A relevant reply with a clear next step, ready for a person to inspect. This guide follows a client asking for a proposal review. The names, message and project are examples; the permission boundaries come from the documented Astra workflow.

Start with access to Email Agent and a supported mailbox connection. Google and Outlook sources depend on your account configuration. Confirm which mailbox the agent is using before you bring a real client into the workflow.

Give the agent useful context

An email rarely contains the whole job. A request to “review the proposal” might depend on a project brief, a prior discussion and a project deadline. Choose the relevant knowledge and sources the agent can actually read.

Keep the initial scope small: one project and the documents that explain its direction. A focused knowledge set makes it easier to see whether the reply reflects the work. A tool being available does not establish that the agent has already read a file or checked a calendar.

Set tool permissions and reply delivery separately

Astra separates permission to perform tool actions from the controls for delivering a reply. Review both. A sensible first workflow prepares a draft and leaves delivery for review.

If the agent can use a calendar tool, define the allowed operation and calendar. Do not infer permission to create an appointment from permission to read availability. Similarly, a useful draft does not mean it has been sent.

Review the exact email

In the documented approval workflow, inspect the recipient, subject and complete body before approving the send. Check whether every promise in the draft is supported: a date, a deliverable, a price, a booking or a file that will be supplied.

Read the reply once from the client’s perspective. Does it answer the actual question? Does it state a next step? Is anything described as completed when it is only proposed? Fix those details before delivery.

Verify delivery as a separate outcome

For an authorized test, use an address and message you control. Verify the actual sent message and its destination. Check how the configured provider reports errors or a failed action; do not treat the presence of a draft as proof of delivery.

Keep a narrow workflow until you understand it. The useful outcome is a clear, accurate communication with a known delivery state—not simply a fluent paragraph.

Based on earlier Astra product documentation and app captures. Check current controls and availability in your workspace.