Draft a reply that answers the incoming message and states your intended response. Keep the conversation focused on the decision or next step.
How to use
Sign in and paste the received message. Add what you want to accept, decline, or clarify in context. Check the reply before sending it yourself.
Example
For an invitation you cannot accept, state that you are unavailable and offer another date only if you can attend then.
FAQ
Does it send the reply?
No. It generates text for you to review and copy. Confirm dates and commitments instead of accepting them from the draft automatically.
Related tools
A practical task
State your actual decision in context before asking for a reply. For a request you cannot fulfill, provide the limit and any genuine alternative. Without that decision, polished wording can imply acceptance that you never intended.
Another useful question
How do I respond to several questions?
List the questions and your answer to each. Check that the draft does not answer only the easiest one and leave the important request unresolved.
Details for interpreting the result
| Detail | Explanation |
|---|---|
| Context and audience | The same fact needs different explanation for a specialist and a first time reader. State the audience, purpose, and terms they already know. Relevant context guides wording more effectively than broad requests to make a text impressive. |
| Tone and commitments | Tone changes the way a message sounds, not the obligations it contains. A friendly version must not invent permission, and a formal version must not invent a promise. Compare commitments as well as style. |
| Supplied facts | A writing request needs the facts the finished draft must preserve. Names, dates, quantities, and policies should come from your source. Missing information is a question to resolve rather than a blank to fill with a plausible invention. |
| A clear next action | A message should make the next action easy to identify: approve a choice, send a file, confirm a time, or answer a question. State the action directly and keep supporting background separate from the request. |
| The recipient's knowledge | A recipient cannot act on references they cannot identify. Replace an unexplained “that file” with a real document name and include the needed context. Omit background they already know when it does not help the decision. |
| Real deadlines | Give an exact date or time only when it is known and needed. Relative phrases such as next Friday can be ambiguous across timezones or a delayed reading. Keep the deadline consistent with the action the message requests. |
| Editorial review | Review facts, names, omissions, and implications before approving a draft. A smooth sentence can still change a condition or attribute a statement to the wrong person. Compare meaning with the source instead of judging fluency alone. |