Send a voice reminder your client can act on


Record a short follow-up, share the link and include the decision or action you need in the accompanying text.

VocalJet recording and voice sharing interface
VocalJet app preview

Build the reminder around one next step

A useful follow-up identifies the request, its owner and the date to confirm.

  1. State the context: name the project and the item waiting for a response.
  2. Ask one clear question: say what you need from the recipient.
  3. Explain the dependency: describe what cannot progress until they answer.
  4. Propose a next step: ask them to confirm a date or decision.
  5. 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?
A practical review method

Know what is holding up the reply

Write and send a focused voice reminder for approvals, missing assets or clarification. Keep the requested action visible in the accompanying text.

Check the earlier request before chasing it

Find the original question, the agreed response timing and the person expected to answer. A delay may mean the client never received a clear request or is waiting for someone else. Repeat only the context needed to make the next decision.

Record a short message that names the item, explains what depends on it and asks for a response or revised date. The scripts above are fictional examples to adapt. Do not claim that a missed feedback deadline automatically changes the agreed delivery date.

Send it yourself and keep a written next step

Save and review the recording, then share its link through the email or project channel you already use. Put the essential question in writing so the recipient can act without listening immediately. This process does not schedule reminders or send automatic chasers.

If the response still does not arrive, follow your agreed escalation process and record the delivery dependency. A voice reminder adds explanation; it does not replace a decision owner or an explicit agreement about what happens next.

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.