Separate what has happened, what is uncertain and what you need from the client. Ask AI for a short update that makes the next action easy to see.
A clear client message can reduce avoidable confusion. It should reflect confirmed progress and commitments, not make an incomplete project sound finished.
A practical workflow.
Define the message type
Choose a progress update, proposal brief, reply or request for a decision. Name the reader and what they need to know at this moment.
List confirmed progress
Supply completed work, outstanding tasks and any agreed dates. Put possible delays or dependencies in a separate list.
Make the request explicit
Say what decision, information or approval you need and why it matters. Do not invent a deadline merely to make the message feel urgent.
Review the commercial details
Check scope, price, dates and any contractual language against your actual agreement. Remove claims that go beyond what you can confirm.
READY TO MAKE YOURS
Start with this prompt.
Draft a client update using only these approved notes: [notes]. Use a [tone] tone. Separate completed work, next steps, blockers and decisions needed. Do not invent progress, prices or delivery dates. Mark unknowns clearly and list commitments I must verify before sharing.
Replace the brackets. Leave out private details. Check the response.
ILLUSTRATIVE EXAMPLE
A clearer request.
A VAGUE STARTTell the client everything is going well.
A CLEARER BRIEFDraft a concise update: two pages are complete, feedback is still needed on the third and the launch date is not confirmed. Ask for feedback without implying approval already happened.
The draft can be positive while staying accurate.
Before you use the result.
- Progress claims are supported.
- Dates and scope match the agreement.
- Dependencies are understandable.
- The client knows what response is needed.
A few useful answers.
How do I mention a delay?
Explain the confirmed situation, its practical effect and the next step. Avoid blame or an unverified promise about when the issue will be resolved.
Can AI write a proposal?
It can structure a draft using scope, deliverables and terms you supply. Review the commercial and legal details through your normal process before sending.
PUT THE GUIDE TO WORK
Client conversations with clear next steps
An enquiry, a change request and a handover need different messages. These templates keep the decision, deliverable and next step visible. Use the terms you actually agreed; do not ask AI to invent a contract or promise.
ChatGPT prompts for freelance business conversations need clear boundaries
Client communication works best when the draft distinguishes a request, an estimate and an agreed commitment. Supply the actual scope, the current status and the decision you need from the client. Do not let a friendly rewrite imply that extra work is included or that a delivery date has been accepted.
Keep the business record outside the chat
Once the client confirms a decision, record it in your project notes or agreed working system. A generated draft is not proof of approval. Link the message to the relevant deliverable, scope version or feedback round so both sides can find what was agreed later.
Open a card, copy the prompt and replace the brackets with your own details. Each card includes a follow-up and a check before you use the answer.
SITUATION 01 ↗
Clarify an enquiry
Turn a vague request into a useful first conversation.
Open the prompt +
Using this client enquiry [message] and my actual service [service], write a short reply with no more than four clarification questions. Focus on the desired output, audience, timing and approval process. Do not quote a price or promise a delivery date. Explain the next step once the questions are answered.
Refine the next draft
Remove any question already answered in the enquiry. Put the one decision that changes the project most first.
Before you use it
Check that your questions fit the service. A simple enquiry should not receive an unnecessary questionnaire.
SITUATION 02 ↗
Respond to an extra request
Separate the existing deliverable from proposed additional work.
Open the prompt +
Draft a reply to this additional request [request]. Agreed deliverables: [scope]. Confirmed timeline and review allowance: [terms]. Explain which part is already included and which part needs a separate decision. Do not invent fees, a revised deadline or a contract clause. Ask whether the client wants an estimate for the additional work.
Refine the next draft
Give me a concise version that sounds collaborative and keeps the scope distinction clear.
Before you use it
Read the actual agreement. If scope is ambiguous, describe the question rather than asserting that the client is wrong.
SITUATION 03 ↗
Get actionable feedback
Ask the reviewer to identify what needs changing.
Open the prompt +
Write a request for feedback on [draft]. The decision-maker is [person or unknown]. I need feedback on [specific areas] by [requested date]. Distinguish the requested date from an agreed deadline. Ask the reviewer to separate necessary changes from preferences and to identify the final approver if unknown.
Refine the next draft
Add a simple reply format: keep, change, question. Do not make the client fill in more than is needed.
Before you use it
Confirm the reviewer has the correct version and access. Do not imply silence counts as approval unless that is actually agreed.
SITUATION 04 ↗
Hand over completed work
Make the file, status and next action unambiguous.
Open the prompt +
Draft a handover email for [deliverables with real links]. Current approval status: [status]. Remaining tasks: [tasks or none]. Explain what is included, where to find it and what the client should do next. Do not call an unapproved draft final or claim an attachment exists when I supplied a link.
Refine the next draft
Shorten the handover to five useful sentences while keeping the version, status and next step.
Before you use it
Open the supplied links and verify permissions yourself. Check that the file names match the message.
The examples below are original, illustrative edits using fictional situations. They show the checks to make, rather than promising what an AI tool will produce.
WORKED EXAMPLE
An extra page is a decision, not a silent yes
Fictional scenario: a designer agreed to three website pages. The client asks for an additional landing page. No price or new timeline has been approved.
FIRST DRAFTAbsolutely, I will add the landing page at no extra cost and keep the Friday deadline.
AFTER CHECKINGThanks for the idea. The current scope covers three pages; the new landing page would be an additional deliverable. Would you like me to estimate the extra work and its effect on timing before we decide? I will keep the current three-page work moving meanwhile.
What changed
The first reply creates two commitments the brief never authorized. The revision acknowledges the request and names the decision needed. The scope statement is appropriate only if it matches the actual agreement; the example is not contract advice.
WORKED EXAMPLE
Ask for a decision instead of 'thoughts'
Fictional scenario: a client has a draft homepage and needs to choose between two approved headline options. The final approver is unknown.
FIRST DRAFTPlease send your thoughts on the homepage as soon as possible.
AFTER CHECKINGCould you choose headline A or B for the homepage, and flag any factual errors in the draft? If someone else gives final approval, please include them in the reply. Could you send this by Thursday so I can plan the next revision?
What changed
The edited request narrows the response to a decision and a useful check. Thursday is framed as a request, not an invented deadline. Confirming the final approver can prevent polishing a version that the decision-maker has not seen.
Try it with your own task.
Keep the latest agreed scope, version and approval decision in one place. Clear records matter more than making every message sound formal.
GO DEEPER / 2 FREE TEMPLATES
Prompts for this part of the task.
Use a template for the step you are working on. Add the required inputs, then check the result against your source material.
Browse the task-guide directory ↗
Use a small workflow that you can repeat.
- Choose the decision or action the output should support.
- Remove confidential details and provide the approved source material.
- Ask for a draft with uncertainties separated from confirmed facts.
- Review owners, dates, calculations and commitments before sharing or acting.
Keep in mind: Do not paste client secrets, credentials or restricted internal documents. A clear-looking table does not make its numbers or ownership assignments correct.
A customer reply with clear limits
Offer the next step without making unauthorised promises.You get: Customer reply with approved options+
COPY. PERSONALISE. CHECK.
Draft a reply to this anonymised customer message: [message]. Confirmed order details: [facts]. Approved policy: [policy]. Options I can offer: [options]. Acknowledge the issue, explain the next step and ask only essential questions. Do not promise a refund, delivery date or exception unless I explicitly authorise it. Flag where the policy or facts are missing.
Example input
A parcel is late; tracking shows a delay but the delivery date is unknown.
Illustrative scenario, not a generated or verified AI result.
Then ask
Make the reply more human without weakening the limits or adding promises.
Before using the answer
Check the order facts, actual policy and authority to offer each option.
Respond to an out-of-scope request
Explain a trade-off without making an unwanted promise.You get: Short reply explaining the trade-off+
COPY. PERSONALISE. CHECK.
Draft a reply to this additional request: [request]. Our agreed scope is [scope], existing commitments are [commitments], and the options I am authorised to offer are [options]. State the requested change neutrally, explain its effect using only supplied facts and ask the recipient to choose one option. Keep it under 130 words. Do not invent fees, contractual terms, dates or approval. Leave a visible placeholder for any essential missing detail.
Example input
The client asks for three extra slides. The agreed deck has ten. I can replace three existing slides or ask the project lead to assess extra work.
Illustrative scenario, not a generated or verified AI result.
Then ask
Make the reply warmer while keeping the same boundary and decision.
Before using the answer
Confirm that every option is within your authority before sending.
Keep learning from original sources.
These sources inform the workflow and checks; the templates above are original LifestyleGlide prompts.
