When a user submits a GoZen Form, create a ticket in Fluent Support

Each GoZen Forms submission opens a ticket in Fluent Support for the person who sent it, so help requests from your forms land in your WordPress help desk queue for an agent to pick up.

GoZen Forms

Fluent Support

Download this workflow Browse more workflows

2 steps Setup ~5 min Used on 1.4k sites Free to import

The When a user submits a GoZen Form, create a ticket in Fluent Support workflow on the FlowMattic canvas, with 2 steps across GoZen Forms, Fluent Support — The workflow as it appears in the builder after import. Each step opens for editing.

What this workflow does

A support form is only useful if the request reaches the people who answer it. When GoZen Forms entries arrive by email or sit in the form dashboard, agents copy them into the help desk by hand, and some get missed. This workflow turns each submission into a Fluent Support ticket.

The GoZen Forms trigger fires when a form is submitted. FlowMattic passes the answers to Fluent Support, where Create a New Ticket Using Customer opens a ticket for that person. Map the submitter's email so the ticket is tied to them, then map the subject and message fields into the ticket title and content.

Fluent Support runs on your WordPress site, so the ticket appears in the same queue as tickets customers open themselves. Every submission creates one ticket, with no check in between.

Help request form on a marketing site

Your landing pages use GoZen Forms for a Get Help form. Each request becomes a Fluent Support ticket that your agents answer from the WordPress dashboard.

Bug reports from beta users

Beta testers submit a GoZen bug report with steps and expected result. The ticket content carries those answers so a developer can triage from the help desk.

Refund and returns requests

Shoppers fill in a GoZen returns form with their order number. A ticket opens for each, keeping returns in the same queue as other support work.

How this workflow runs

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

Step 1Trigger
GoZen Forms On Form Submission
Fires when someone submits your GoZen Forms form. The submitted answers, such as name, email, subject and message, are passed to the Fluent Support step.
Step 2Action
Fluent Support Create a New Ticket Using Customer
Opens a new Fluent Support ticket for the person who submitted. Map their email to set the customer, and map the subject and message fields into the ticket. Run a test to see the other values the step takes.

What you need

FlowMatticCore
GoZen Forms AccountAccount
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.

Make email a required question in GoZen Forms. The ticket is created for a customer, and an entry without an email has nobody to attach it to.
If one form handles several kinds of request, add a Filter after the trigger so only the topics your support team handles become tickets.
Submit a test entry after import, then open the ticket in Fluent Support and check that the title, content and customer look right before you go live.

Questions about this workflow

Does the person who submits the GoZen form need a Fluent Support account first?

The step creates the ticket using customer details you map, such as the email. Test with a new address and an existing one, and check Task History and the ticket in Fluent Support for how each is handled.

Will the customer get Fluent Support's usual ticket emails?

Your Fluent Support notification setup decides that. The workflow only creates the ticket, and Fluent Support handles any notifications as it does for other new tickets.

Can GoZen Forms file uploads be added to the ticket?

The action supports file attachments, according to its description. Submit a test with a file and check what the trigger returns before you map it.

What if someone sends the form twice?

Two tickets are created. Nothing in the workflow checks for an open ticket from the same customer.