Skip to main content
In ChatSyncs, an Audio Message plays a voice recording to the customer inside a Keyword Replies flow — see Keyword Replies for how to drag it onto the canvas alongside the other flow components. Unlike a text message, audio lets a business explain something in its own voice, which reads as more personal for greetings, walkthroughs, and instructions.
Keyword Replies flow titled Real Estate - Property Introduction Audio, with a welcome Text message connected to an Audio block being selected from the flow blocks panel
Example: a “Property Introduction Audio” flow sends a welcome text — “We’ve prepared a short audio to help you understand the project highlights before exploring further” — then plays a voice recording covering the apartment, amenities, pricing, and lifestyle.

​
Where it can go in a flow

An Audio Message can connect after almost any other block, so it fits wherever a spoken explanation adds value:

​
Common use cases

The real estate Property Introduction example above is one instance of this same pattern — see Keyword Replies: Real Estate Property Showcase for a full worked flow it could extend.

​
Best practices

  • Keep audio between 30–60 seconds whenever possible — long recordings lose customers.
  • Speak clearly, in a friendly tone, with background noise removed.
  • Cover one topic per audio message rather than combining several ideas.
  • End with a clear call to action — explore products, contact support, or book a service.

​
Frequently asked

AAC, MP3, AMR, or OGG, up to 16 MB — see the component table in Keyword Replies. An OGG file encoded with the Opus codec renders as a native WhatsApp voice note with a waveform; other formats play as a regular audio file — see Audio Messages.
Almost any of them — Text, Image, Video, Document, Interactive Message, CTA URL Button, User Input Flow, AI Reply, Condition, WhatsApp Flow, HTTP API, and Template Message — see Where it can go in a flow above.
30–60 seconds is the sweet spot — long enough to explain one thing clearly, short enough that customers actually listen to the end.
Yes, but the common pattern pairs it with a short lead-in Text or Image message first (e.g. Hi → Welcome Text → Welcome Audio) so the customer has context before the recording plays.