Convert Fluent Support agent replies into speech and email the audio link

Each time an agent replies to a Fluent Support ticket, Deepgram reads the reply aloud as speech and FlowMattic emails a link to the audio, with a ready-written subject and message.

Fluent Support

Deepgram

Download this workflow Browse more workflows

3 steps Setup ~5 min Used on 1.7k sites Free to import

The Convert Fluent Support agent replies into speech and email the audio link workflow on the FlowMattic canvas, with 3 steps across Fluent Support, Deepgram, Email — The workflow as it appears in the builder after import. Each step opens for editing.

What this workflow does

Some customers would rather listen than read: people on the move, people with low vision, or anyone who finds long written answers hard to follow. This workflow gives each agent reply in Fluent Support a spoken version and sends a link to it by email.

The Fluent Support trigger fires whenever an agent adds a reply to a ticket, on your WordPress site. The reply text and the ticket's details, such as the customer, pass on to the next steps.

The Deepgram Transform Text-to-Speech step converts text to speech. It ships unmapped, so after import you connect Deepgram and map the agent's reply text into it. Delivery is handled by FlowMattic's Email module, using WordPress mail or an SMTP account you set up. Its subject, "Audio version of a support reply", and its body, which puts an audio link from the Deepgram step after "Listen to the reply here", are already written.

Two things are left for you. Set the recipient, for example the customer's email from the ticket, and run a test to confirm the Deepgram step returns the audio link under the name the email expects. Every agent reply starts a run, including short ones, so check Task History after your first few tickets.

Accessible answers for visually impaired users

A software vendor whose customers include screen-reader users sends each support reply as audio too, so customers can choose how to take in the answer.

Support for customers on the road

A field equipment supplier's technicians read replies poorly on a small screen at a job site, and listen to the audio link instead.

Reviewing how replies sound

A support lead sends the audio to an internal address to hear how replies come across when spoken, as part of tone and quality checks.

How this workflow runs

What happens at each step once the workflow is on, and what you need before you import it.

Step 1Trigger
Fluent Support Agent Replies to a Ticket
Fires each time an agent adds a reply to a Fluent Support ticket. The reply's content and the ticket's details, including the customer, are passed on to Deepgram and the email.
Step 2Action
Deepgram Transform Text-to-Speech
Turns text into speech with Deepgram. Nothing is mapped in the template, so connect Deepgram and map the agent's reply text into the step, then check a test run for the audio link it returns.
Step 3Action
Email Send Email
Sends the email through WordPress mail or your SMTP settings. Subject and body are pre-written, with the Deepgram audio link mapped into the body. Add the recipient, such as the customer's email from the ticket.

What you need

FlowMatticCore
Fluent Support PluginPlugin
Deepgram AccountAccount

After importing, map your own data. To keep the template universal, not every step is pre-filled. Open each step in the builder and connect your accounts and fields (channels, lists, sheets, recipients) before you switch the workflow on.

Make it yours

Changes worth making after you import it.

Fluent Support replies can contain HTML formatting. If the speech reads out tags or symbols, put a Text Formatter step between the Fluent Support trigger and the Deepgram step that removes HTML tags, and map its output into Deepgram.
Rewrite the email body to explain why the customer is getting an audio version, and mention that the written reply is in their ticket as usual.
To offer audio only on some tickets, put a Filter between the Fluent Support trigger and the Deepgram step on a ticket value such as its product or a tag you add for customers who asked for audio.

Questions about this workflow

Who receives the Fluent Support audio email?

The address you enter after import. The template leaves the recipient empty, so map the customer's email from the ticket, or enter an internal address if the audio is for your team.

Is the audio link in the email guaranteed to work?

The body maps an audio link value from the Deepgram step. Run a test reply and check in Task History that Deepgram returned a link under that name. If the output looks different, remap the link in the email body.

Does the email go through Gmail or my SMTP provider?

It uses FlowMattic's Email module, which sends with WordPress mail or the SMTP account you configure. Enter your provider's SMTP details there if you want mail to go out through it.

Does a long Fluent Support thread send an audio email for every reply?

Yes. Each agent reply on the ticket starts its own run, so a customer in a long back-and-forth gets one audio email per reply. A Filter between the trigger and the Deepgram step can limit this.