tr Skip to content

Send agents a daily digest email for every open ticket

Once a day, FlowMattic pulls every open ticket from Fluent Support and emails a separate reminder for each one to the address you set, quoting the subject, ticket number and customer.

Schedule Fluent Support Iterator Email

4 steps Setup ~8 min Used on 1.6k sites Agentic Support Free to import

The Send agents a daily digest email for every open ticket workflow on the FlowMattic canvas, with 4 steps across Schedule, Fluent Support, Iterator, Email
The workflow as it appears in the builder after import. Each step opens for editing.

What this workflow does

Tickets that sit open for days are the ones customers complain about. A helpdesk dashboard only helps if someone opens it. This workflow puts the open queue into an inbox every day, one email per ticket, so each waiting request is in front of someone until it's closed.

Each day a Schedule trigger kicks off the reminder run. The Fluent Support step fetches all tickets with the open filter. An Iterator then takes that list and runs the Email step once for each ticket. Each email has the ticket subject in its subject line, and its body gives the ticket number and customer name with a request to follow up.

The emails go to one fixed address, set to [email protected] in the template. Change it to a real inbox or team list. They do not go to the agent assigned to each ticket. A ticket that stays open is emailed again on the next day's run, and once it's closed it drops out of the list. This is a separate message per ticket, not one combined summary, so a long queue means a long run of emails.

Two-person support team

You share one support inbox. A daily email per open ticket lands there, and whoever handles it replies in Fluent Support and closes it, which ends the reminders.

Manager checking the backlog

Point the emails at a manager's address. Each morning they see which tickets are still open without logging in to WordPress.

Freelancer handling client support

You support a few client sites from your own email. The reminders make sure no open ticket on a client's helpdesk is forgotten during a busy week.

How this workflow runs

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

  1. Step 1Trigger
    Schedule Every Day

    Starts the workflow once every day, with no input of its own. Each run begins a fresh pass over the open queue.

  2. Step 2Action
    Fluent Support Get All Tickets

    Fetches all tickets from Fluent Support using the open filter. The list of tickets is passed to the Iterator.

  3. Step 3Logic
    Iterator Loop Through Array

    Loops over the tickets from Fluent Support and runs the Email step once per ticket, with that ticket's subject, ID and customer name available to map.

  4. Step 4Action
    Email Send Email

    Sends a reminder for the current ticket to [email protected]. Change that to your own address. The subject names the ticket and the body asks for a follow-up.

What you need

  • FlowMatticCore
  • Fluent Support PluginPlugin

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.

  • Replace [email protected] in the Email step with a real inbox or a team list before you turn the workflow on, or every reminder goes to an address that doesn't exist.
  • Add a Filter after the Iterator if only some open tickets need a reminder. Run the workflow once and look in Task History to see which ticket fields Fluent Support returns before you build the condition.
  • Swap the Email step for a Slack or Telegram message if your team works from chat. The same ticket fields can be mapped into the message text.

Questions about this workflow

Is this one digest email or one email per Fluent Support ticket?

One email per open ticket. The Iterator runs the Email step for each ticket in the list, so ten open tickets mean ten emails on that day's run.

Does each reminder go to the agent assigned to the ticket?

No. Every email goes to the single address in the Email step. To reach assigned agents you would need to map an assignee email from the ticket data, if Fluent Support returns one, in place of the fixed address.

Will a ticket keep getting reminders every day?

Yes, for as long as it stays open. Each daily run fetches the open tickets again and emails each one. Closing the ticket in Fluent Support stops its reminders.

Which tickets count as open?

The ones Fluent Support returns for its open filter in the Get All Tickets step. Run the workflow once after import and check Task History to see which tickets came back.

Import this workflow into your WordPress site

Download the JSON, import it from the Workflows screen and connect your accounts. Every run stays on your server, with no per-task fees.

30-day money-back guarantee Unlimited workflows and runs Self-hosted

Customers who run it every day

Rated 4.8 out of 5 by customers
Read more reviews

Crafting bridges between my favorite apps, FlowMattic has truly impressed me with its ability to seamlessly automate workflows. This has noticeably accelerated the efficiency of my business processes, making everything run more smoothly and productively.

Janke

It's very straightforward, has a lot integrations and they work well. It is one thing to 'integrate' new external software, but integrating it well, with lots of options is where FlowMattic shines.