A client sends a voice note halfway through a project. They mention a different audience, an extra deliverable and an earlier launch. Do not reply only with “noted.” Treat the audio as a request, make a short written record and ask the client to confirm it before changed work begins.
The client can see what the team understood, while the team checks scope, price, timing and ownership without treating an informal message as approval.
Treat the voice note as a request
A voice note is useful context, but a poor final record when several decisions are packed into natural speech. “Could we” may be an idea rather than an instruction. A date may mean review, delivery or launch.
Listen once for the whole story, then again for decisions. Keep the original message in context. Do not rely on memory. The WhatsApp channel explains the channel, while a professional-services team still needs its own change process.
Do not ask the client to repeat everything in a form. Reply with the concise version you understood and isolate only the open questions.
Turn the message into a change record
Write a record that identifies the current agreement, requested change and open questions.
| What you heard | What to record | What to ask |
|---|---|---|
| An extra deliverable | Name the item and its expected format | Is it added or replacing something? |
| A new date | Label review, delivery or launch | Which date is fixed? |
| A different audience | State who the work is now for | Does the brief or approval route change? |
| A broad “go ahead” | List the exact items it could cover | Which version is approved? |
Include the person checking effort, the response deadline and the status. “Change requested” is different from “change approved.” The shared inbox makes the next owner visible, while the contact record holds the latest operational state.
Check impact before asking for approval
Do not promise a date or fee before the delivery owner checks the effect. Identify the changed deliverable, check dependencies, calculate the effect on price and timing, then name who may approve the revised plan on each side.
If the impact is unknown, say what is being checked and when the client will receive an answer. A precise holding reply beats a commitment the team later retracts. The professional services workspace centres visible ownership, not implied authority.
Let AI draft without letting it decide
AI can turn a team member's notes into a compact summary, surface missing fields or draft a confirmation. A human must listen to the source, check the draft and decide whether commercial or delivery review is required.
Do not let automation invent a transcript, infer approval or calculate an unverified fee. If audio is unclear, ask one focused question. Workflow automation can handle assignment and reminders after rules are defined. It does not own the commercial decision.
Confirm the change before work continues
Send one confirmation with the revised deliverable, price effect, timing effect and next owner. Ask the client to approve, decline or correct it. A thumbs-up or “thanks” may acknowledge receipt without identifying which version is accepted.
For example: “We understood that the launch checklist is added to phase two, the review moves to 22 October and the fee changes by the quoted amount. Please approve or correct this summary.” Adapt it to your contract and policy.
WhatsApp's current Business Messaging Policy requires accurate communication, respect for opt-outs and a clear human escalation path when automation is used. Its channel rules do not replace a contract or professional obligation.
Keep one source of truth
After confirmation, update the project record and mark the earlier version as superseded. Tell delivery what changed, who approved it and when the commitment starts. If the client corrects the summary, issue a clean new version.
The sales workflow can connect the commercial next step. Avoid copying confidential audio or client detail into unnecessary tools.
Meta's voice message feature update describes preview and variable playback speeds. Useful controls still do not turn speech into a confirmed project instruction.
Frequently asked questions
Does a voice note count as client approval?
That depends on the contract and the firm's approval policy. Operationally, convert the message into a written summary and ask the authorised person to confirm the exact version, cost and timing before changed work begins.
Should the team transcribe every voice note?
Not necessarily. Record the decisions, constraints and open questions needed for the project. Keep the original message according to your retention rules, and avoid creating extra copies of sensitive content.
What if the client asks the team to start immediately?
Acknowledge the urgency, state what must be checked and give a realistic answer time. Do not let urgency erase the distinction between a request and an approved change.
Want help applying this guide?Ask the DripTell team
From reading to action
Want help applying this to your business?
Share your details. We will read the article you are on and start with a useful answer for your team.
DripTell Editorial
Practical guidance reviewed by the DripTell product and customer workflow team.
See how DripTell checks product claims, uses primary sources and handles corrections.
Editorial and source policy
