Build the reminder around one next step
A useful follow-up identifies the request, its owner and the date to confirm.
- State the context: name the project and the item waiting for a response.
- Ask one clear question: say what you need from the recipient.
- Explain the dependency: describe what cannot progress until they answer.
- Propose a next step: ask them to confirm a date or decision.
- Share the voice link: repeat the essential request in the written introduction.
This is a manually sent voice reminder. It does not describe a scheduled-notification or automatic chasing feature.
Three voice reminder examples
Fictional scripts to adapt to your actual project and agreement.
Approval needed
Hi Alex, could you confirm whether the latest homepage copy is approved? We need that decision before preparing the final layout. Please reply with approval or the specific changes you need.
Missing assets
We are still waiting for the approved product images. Could you confirm who will supply them and when? If the date has changed, we can review the launch plan together.
Feedback clarification
Thanks for the comments. Before we update the estimate, could you explain whether the extra page is part of this release or a separate request?
Keep the follow-up connected to the project
Let the audio add context while the written message makes the request easy to scan.
Use voice messages by email to send the listening link, or review the record-and-reply workflow. For wording after a review, read the client follow-up email guide.
If the client still has not replied, use the client feedback follow-up checklist to check the deadline, owner and impact on delivery.