Answer in 2 sentences
To rewrite an email reply with AI, select the incoming message when you need help composing a response and use the Reply profile, or select your own draft and use the Email profile to polish it. The safest workflow is to identify the required action, preserve names, dates, numbers, and commitments, generate the rewrite, then compare every factual detail with the original before sending.
Reply and Email solve different steps
The Reply profile starts from context written by someone else. Select the relevant message or thread and ask the assistant to draft an appropriate response. This is useful when the hard part is deciding what to say.
The Email profile starts from your draft. Write the facts and intended outcome in plain language, even if the wording is rough. Select that draft and run Email to improve structure, tone, and clarity. This is useful when you know what to say but want it to sound professional.
Both profiles are part of PromptDC writing mode. PromptDC works on selected text across the web. In an editable field, the result can replace the selected draft in place. On read-only text, the result is copied so you can paste it into the reply box. It is not necessary to move the whole conversation into a separate editor.
Step 1: extract the decision before rewriting
Do not begin with tone. Begin with the decision the email requires. Most messages ask for one or more of the following:
- Confirm receipt.
- Approve or reject a request.
- Provide a date, file, price, or status.
- Ask a clarifying question.
- Correct an error.
- Set a boundary.
- Escalate to another person.
Write the required action in one sentence. For example: “Confirm that I received the proposal, say I will review it by Thursday, and ask whether the price includes support.” This sentence becomes the factual spine of the reply.
If the source email contains several topics, list them before generating. AI can produce a smooth reply that accidentally answers only the easiest question. A simple checklist prevents that failure.
Step 2: protect fixed facts
Create a short set of details that must not change:
- Names and company names
- Dates and time zones
- Prices, quantities, and percentages
- File names and document versions
- Deadlines and commitments
- Legal or policy language
- Links and contact details
Never ask a rewriting tool to infer missing facts. If you do not know whether Tuesday works, say that confirmation is pending. If a price is unclear, ask a question. An invented detail can be more damaging than an awkward sentence.
For confidential communication, remove unnecessary personal or business information before sending text to any hosted AI service. Follow your employer’s data policy. A rewrite assistant is not permission to disclose a customer record, health detail, credential, contract, or private attachment.
Step 3: choose Reply or Email
Use Reply when the incoming text provides enough context and you want a response draft. Select only the relevant part of a long thread. Including five pages of signatures and old replies adds noise and can increase model cost.
Use Email when you already have a draft such as:
> got it thanks, i can look thursday, does the quote include support?
The desired rewrite might be:
> Hi Maya, > > Thanks, I received the proposal. I can review it by Thursday. Could you also confirm whether the quoted price includes ongoing support? > > Best, > Alex
The improved version is clearer, but the facts are unchanged. It does not promise approval, invent a meeting, or add urgency.
Step 4: specify tone with observable language
“Make it better” is not a useful quality standard. Define tone through behavior:
- Warm: acknowledge the person and use courteous phrasing.
- Direct: put the decision in the first sentence.
- Firm: state the boundary without apology or accusation.
- Concise: remove background that does not affect the action.
- Executive: lead with outcome, owner, and deadline.
Avoid asking for vague extremes such as “very persuasive” or “extremely professional.” Those instructions can produce inflated language. A good business email sounds like a capable person, not a brochure.
Step 5: run a four-pass review
Before sending, inspect the draft in this order.
Accuracy pass
Compare every proper noun, date, number, and commitment with the source. Check that the message answers all questions.
Relationship pass
Ask whether the tone fits the relationship. A customer escalation, manager update, colleague request, and cold sales reply require different levels of formality.
Action pass
The recipient should know what happens next. If action is required, name the owner and deadline. If no action is required, avoid creating one accidentally.
Brevity pass
Delete repeated thanks, generic openings, and summaries the recipient already knows. Keep context only when it helps the decision.
Common email workflows
Following up without sounding aggressive
State what you are following up on, why timing matters, and the next useful action. Do not imply that the recipient ignored you unless that fact is necessary.
Declining a request
Give the answer early. Add a brief reason if appropriate, then offer a realistic alternative. Do not let AI invent a policy to make the refusal sound stronger.
Correcting a mistake
Name the error, provide the correct information, and state the impact. Avoid defensive explanations. If the mistake changed a deadline or amount, repeat the corrected fact clearly.
Replying to a long thread
Select the decision-bearing paragraphs, then ask for a response organized by topic. If the thread contains conflict, manually verify who made each claim. Summaries can collapse disagreement into false consensus.
PromptDC pricing for this workflow
PromptDC has no free tier. Pro costs $9 per month. Lifetime starts at $69 one time and uses your own API key, with typical model usage of about $1 to $3 per month. Actual usage depends on the selected model, volume, and input length.
If you want continuous inline grammar suggestions and plagiarism checking, Grammarly may be the better product. If you want profile-based email, reply, summary, social, and prompt rewrites from selected text, read PromptDC vs Grammarly.
A reusable reply checklist
Before generation:
- What is the recipient asking?
- What decision can I make now?
- Which facts must remain exact?
- What tone fits the relationship?
- What is the next action?
Before sending:
- Are all names, dates, and numbers correct?
- Did the draft add a promise?
- Did it answer every material question?
- Is the requested action clear?
- Would I be comfortable defending every sentence?
Bottom line
Use Reply to compose from incoming context and Email to polish a draft you already wrote. The AI should improve expression, not make decisions on your behalf. A reliable email workflow separates facts from style, gives the model only necessary context, and ends with a human accuracy check.
FAQ
Can AI send the reply automatically?
This workflow is intentionally review-first. Generate and inspect the message before sending. Automatic sending creates avoidable risk when a model changes a fact or commitment.
Should I select an entire email thread?
Usually no. Select the current message and only the earlier context required to answer it. Remove signatures, disclaimers, and repeated history.
Which profile should I use for a rough draft?
Use Email when the draft contains your intended facts. Use Reply when the incoming message is the main source and you need help composing a response.