# Replies and approvals

Ask for an answer, offer choices or discuss a proposed action before deciding.

An ordinary message needs only content and recipients. Use a response request when you need to track a final answer, or attach an approval flow when someone needs to approve or deny a proposed action.

## Offer answer choices

Choose **Add answer choices** in the composer. Add each option using its own field; remove choices you do not need. The recipient selects a choice as the final answer.

Use choices for a small set of real alternatives, such as **After the demo** and **Tomorrow morning**. Use normal text when the answer needs an explanation.

## Attach an approval flow

Choose **Request approval** and describe the proposed action in the message. The draft shows the decision buttons before you send. Remove the flow with its close control if it is no longer needed.

For example:

> Staging is ready for the V2 checkout rollout. May I restart the checkout-v2 worker pool after the demo?

The recipient can approve, deny or ask for context. Nothing is approved merely because the sender added those buttons.

## Ask follow-ups before deciding

Continue in the same conversation:

> Hey, how long will staging be busy?

The agent can explain that the restart takes two minutes and the demo stays on a separate pool. The person then makes the final decision with the original approval controls.

## Understand the outcome

A saved decision is not proof that a deployment, query or other external action ran. Your runtime receives the decision and enforces its own tool access and business rules.

If another eligible participant already answered, refresh the request. Current audience and permissions still apply; a channel button cannot override them.