How to Reply to Client Feedback and Confirm the Next Revision
Thank the client, translate each comment into an action or clarification, and confirm what happens next. Keep included revisions separate from additional deliverables, and promise a date only after checking the work and dependencies.
By MailCat · Published
Show what you will change
“Thanks, I will make the changes” can sound cooperative while leaving the actual revision undefined. A useful reply identifies the edits you understood, asks about ambiguous comments, and explains any effect on the delivery plan. You do not need to defend every design choice or agree to every request.
Read the feedback for concrete edits, subjective direction, and new deliverables. A request to adjust a headline may be a revision; a request to create another page may be extra work. Check the agreed brief instead of deciding from the client's tone or the size of the email.
A mix of clear edits and open decisions
Fictional incoming feedback
Subject: Homepage draft feedback
Hi Adrian,
Thanks for the first draft. Please change the headline to “A simpler way to manage your projects” and remove the testimonial section. The hero still feels too busy; can you make it cleaner? We would also like a separate pricing page using the same design.
Can you send the next version Thursday?
Thanks,
Casey
The fictional project includes one homepage and one revision round. The requested headline and section removal are included. “Cleaner” needs clarification. A separate pricing page is outside the current scope. Adrian has checked capacity: Thursday is possible for the homepage if the client confirms hero direction by Tuesday noon. No price or delivery date has been assessed for the pricing page.
Build a feedback-to-action map
| Client comment | Treatment | Reply action |
|---|---|---|
| Replace headline | Included, specific edit | Confirm the exact supplied wording |
| Remove testimonials | Included, specific edit | Confirm removal |
| Make hero cleaner | Ambiguous direction | Offer a concrete interpretation and ask for confirmation |
| Add pricing page | Additional deliverable | Offer to assess separate scope, price, and timeline |
| Thursday next version | Conditional availability | State the Tuesday feedback dependency |
A complete reply that makes the revision concrete
Fictional reply: clarification needed
Hi Casey,
Thanks for the clear notes. In the next homepage revision, I will change the headline to “A simpler way to manage your projects” and remove the testimonial section.
For a cleaner hero, I suggest removing the decorative background shapes and keeping one main image with the primary button. Is that the direction you mean, or is the main concern the amount of text?
The separate pricing page is additional scope. I can prepare an estimate and timeline for that page if you would like; I have not included it in the next homepage revision.
I can send the revised homepage Thursday if you confirm the hero direction by Tuesday at noon. If confirmation comes later, I will check the schedule and confirm a revised delivery date.
Please confirm the hero direction and whether you want an estimate for the pricing page.
Thanks,
Adrian
The proposed design treatment is a question, not a claim that the client already approved it. The final paragraph makes the two decisions easy to find. The pricing page stays separate from the conditional Thursday commitment.
When the feedback is already specific
Sometimes there is no ambiguity to resolve. In this alternative fictional scenario, Casey has already asked for the background shapes to be removed and the single main image retained. Casey has also said to postpone the pricing page. Adrian has checked that Thursday delivery is feasible without another dependency.
Complete reply: all revision decisions supplied
Hi Casey,
Thanks for confirming the direction. I will update the homepage headline to “A simpler way to manage your projects,” remove the testimonial section and decorative hero shapes, and keep the single main image.
I will send the revised homepage Thursday. I have left the pricing page out of this revision as requested; we can discuss its scope separately when you are ready.
Thanks,
Adrian
Do not add a clarification question just to follow a template. When the facts and decisions are complete, a short confirmation is enough. Avoid calling a revision “final” unless that status has actually been agreed.
When comments conflict or arrive from several people
Describe the conflict neutrally: “One comment asks to retain the testimonials, while another asks to remove them. Which direction should I use?” Ask the client to identify the decision owner or supply one consolidated list. Do not choose an approver based on their job title or assume the latest message overrides earlier approval.
For subjective feedback, ask about the visible result: “Do you want fewer elements, shorter text, or a different image?” A focused choice is easier to answer than “Please clarify.” If you recommend keeping something, explain the reason and ask for the client's decision rather than writing as though agreement is automatic.
Check before sending
- Did you preserve supplied copy exactly where required?
- Does every comment lead to a change, question, or explicit decision?
- Are ambiguous directions still presented as open?
- Have you separated included revisions from added work?
- Is the delivery date supported by your workload and dependencies?
- Does the client know which approvals or inputs you need next?
In MailCat, use custom answers or instructions to supply the actual revision actions and approval conditions. Review the generated preview against the original feedback: AI may miss a comment or turn a suggestion into a promise. Explicitly insert the reviewed reply into Gmail, check the final message, and send it yourself.
Use the scope-change replies for new deliverables, the professional client examples for general communication, and the freelancer workflow when several project decisions arrive together.
Get MailCat
7 days free, no card. Then US$9.99/month plus applicable taxes.