A little practice
Confidence grows
with a little practice.
Choose something familiar. Read the example, try the instruction in a tool your company allows, and take a moment to check the result.
Keep the care. Get help with the words.
A customer reply
A simple reply is a useful place to begin. You know the customer and the situation; AI can help you find a clear, considerate way to say it.
Help me draft a short WhatsApp reply to a customer. Keep it warm, clear and respectful. Use only the facts below. Do not add a discount, refund policy or delivery promise. Fictional example: The customer ordered 20 notebooks. They were due on Monday. Our supplier has confirmed that we will receive them on Wednesday. We still need to confirm delivery to the customer. Acknowledge the delay, explain what we know, and say we will confirm the delivery arrangement once it is checked. Keep it under 80 words.
See a worked example
The information we start with
20 notebooks ordered. Due Monday. Supplier arrival confirmed for Wednesday. Customer delivery arrangement still needs checking.
One possible draft
Hi, I’m sorry your 20 notebooks have been delayed. Our supplier has confirmed they will reach us on Wednesday. We’re checking the delivery arrangement and will update you once it is confirmed. Thank you for your patience.
This is an illustrative example, not a live AI response.
What to notice
The draft should separate the supplier arrival from delivery to the customer. A fluent sentence can easily turn an estimate into a promise.
Help everyone see the next step.
A team update
Turn a few facts into an update your team can follow. The useful part is a shared understanding of what is done, what is waiting, and who will follow up.
Turn these fictional notes into a short team update with three headings: Done, Waiting, Next step. Use plain English and only the details given. Do not invent a deadline or an owner. If a detail is missing, say what needs confirming. Notes: - Aina completed the stock count. - Two item quantities need checking against the delivery notes. - Kumar will check those quantities. - The customer price list has been drafted. - The owner still needs to approve the price list. - No approval date has been agreed. Keep the update short enough for our team WhatsApp group.
See a worked example
The information we start with
Stock count done by Aina. Two quantities still need checking by Kumar. Price list drafted, awaiting owner approval. Approval date not agreed.
One possible draft
Done • Aina completed the stock count. • The customer price list has been drafted. Waiting • Two item quantities need checking. • The price list needs the owner’s approval; the date is not yet agreed. Next step • Kumar to check the two quantities against the delivery notes. • Confirm when the owner can review the price list.
This is an illustrative example, not a live AI response.
What to notice
Useful structure should make uncertainty visible. It should not quietly turn “needs approval” into “approved”.
Make room for a clearer conversation.
Messy meeting notes
A few rough notes can become a useful action list. You and your team still decide whether it accurately reflects what was agreed.
Organise these fictional meeting notes into an action list. For each action, show the task, the owner and the due date. Use only the facts in the notes. Write 'To confirm' where an owner or date is missing. Finish with the questions we should ask the team. Notes: - Mei will check the packaging stock by Friday. - The product photos need updating; we did not decide who will do this. - Ravi will ask the supplier about smaller order quantities. No deadline was agreed. - We discussed opening on Sunday but made no decision. Do not turn a discussion into an agreed action.
See a worked example
The information we start with
Mei: check packaging stock by Friday. Product photos need updating; no owner. Ravi: ask supplier about smaller quantities; no deadline. Sunday opening discussed, no decision.
One possible draft
Action list • Check packaging stock — Mei — Friday. • Update product photos — Owner: To confirm — Due: To confirm. • Ask the supplier about smaller order quantities — Ravi — Due: To confirm. Questions for the team • Who will update the product photos, and by when? • When should Ravi report back? • When would we like to revisit the Sunday opening discussion? No decision was made about opening on Sunday.
This is an illustrative example, not a live AI response.
What to notice
“We discussed it” is different from “we agreed to do it”. This is a small distinction that helps a team avoid unnecessary work.
Learning is more than the instruction
The judgement is still yours.
A useful result is one you understand, can check, and can explain to someone else. That is what we practise together.
Explore learning with your team ↗