Does your business use Freshdesk to manage support?
If so, you can use Zingtree decision trees to reduce your support team’s workload. Customers can either self-solve their issue, or you can get a new ticket in your Freshdesk that includes all the information from their decision tree session. By effortlessly gathering background information from the customer via the decision tree, you save a lot of time by reducing back-and-forth messages.
Here’s how a ticket generated by Zingtree appears in Freshdesk:
Note how the ticket includes a transcript of the Zingtree session.
Click the link if you’d like to try a demo tree that generates a ticket in our Freshdesk sandbox.
This short video shows how it works:
It’s easy to set this up – here’s an overview of the process:
- Add a new Application to Zingtree for creating Freshdesk Tickets.
- Create a “Ticket Submitted” node.
- Create a “New Ticket” node to obtain the customer’s name, email, ticket subject, description, and optional custom fields.
Add a new Application to Zingtree for creating Freshdesk Tickets.
A Zingtree application can be called from any node. You’ll need to add the Freshdesk App first as follows:
- Log into your Zingtree account.
- Go to Apps & Integrations.
- Select the Freshdesk: New Ticket App.
- Enter your Freshdesk API key and domain name. (Instructions are on the page.)
- Click Add Freshdesk App to save the new App.
Create a “Ticket Submitted” Node
A new ticket is added to your Freshdesk installation when this node appears. This is the end result of pressing a “Submit Ticket” button inside the decision tree. You can create this node as follows:
- Add a new Content Node.
- Give the node a title, and any text you want to appear in the content area – like “Thanks for submitting a ticket” etc.
- Go to the Apps/Webhooks tab.
- Click Add App/Webhook.
- Select the Freshdesk App you just created. You should see something like this:
Now we’re ready to link a ticket entry page to this “Ticket Submitted” node.
Create a “New Ticket” node
After your customer goes through the troubleshooting session, if they haven’t been able to resolve the issue, you can direct them to a node that collects the following info:
- Subject for the Ticket
- Description of the problem.
You use Zingtree’s Data Entry Fields to get this info. The field variables need to be named as follows:
name = fd_name
email = fd_email
subject = fd_subject
description = fd_description
- Edit the node where you want the customer to submit the ticket.
- Click the Data Entry Fields tab.
- Add fields for fd_name, fd_email, fd_subject, fd_description. When you are done, your Data Entry Fields will look something like this:
- You can also optionally add Custom Fields to the ticket. In the above example, we have a custom field named product in our Freshdesk installation. So the Zingtree equivalent is fd_cf_product.
- If you want to set the ticket status and priority, you can also use variables named fd_status and fd_priority. This is optional.
- Another option: Make a variable named fd_type for the ticket type. It can have text exactly matching one of these: Question, Incident, Problem, or Feature Request.
- In the Action Buttons section, add a “Submit” button to go to your submit ticket page.
- Save the changes to this node.
Examine this tree from the Demo Gallery to see a real live setup.