Freshdesk: How to Integrate with Freshdesk Tickets and Portal Pages

  • Updated

 

  • Zingtree and Freshdesk work well together. You can integrate both products in two ways:

    For Call Centers or Live Support:

    Your agents can open a Zingtree within the customer's Freshdesk ticket, and this script can guide an agent to the proper solution.  If another agent takes over the call, he/she can resume the session at the last stopping point, and see the steps the caller took with the previous agent.

    This is how the Agent script appears in Freshdesk:

     

     

    If you’re running live support or a contact center with Freshdesk, you’ll want to use the latest Zingtree Freshdesk app for Agent Scripting. This update supports the new Freshdesk Mint interface and helps guide live agents to solve problems and follow processes.

     

    Get Started

    Install this custom app from the Freshdesk App Marketplace as follows:

    1. Go to your Freshdesk Admin, and click on Apps (under Support Operations).
    2. Search for “Zingtree”, and click the Zingtree App.
    3. Click Install.

    Freshdesk may take up to 30 minutes for your app to be available.

    Configure your App

    There are two settings for your app:

    • The tree ID of the tree you want to appear first (required). The default just shows all the data variables passed into Zingtree.
    • An option to send data from your Freshdesk ticket to Zingtree. If you enable this, you’ll be able to show information from the ticket in your decision tree or do automatic branching using Logic Nodes.

    Using the Agent Scripting App

    When viewing a ticket, click the Zingtree button at the top:

    The decision tree you configured will appear.

    Features

    Zingtree decision trees are easy for anyone to use immediately. But there are a couple of bonuses under the hood you will appreciate:

    • Pause and Resume: When you reload a ticket and click the app button, the decision tree will return to the last place visited. In addition, you can click the History link to see what transpired previously. This is really helpful if a call is dropped, or if a ticket is transferred to a new agent.
    • Instant Notes: With a single click, agents can add internal notes to a ticket from a template you provide. This can include the transcript of the session, any data gathered, or anything else you like. These notes can then be edited before they are saved. This is a HUGE timesaver for your agents. Learn more here.
    • Agent Feedback: At the bottom right, you’ll see the Agent Feedback button.

    Your agents can click this to send comments back to the authors of the tree. This is a great way to continue to improve your knowledge base, and also involve your agents in the publishing process.

     

    For Customer Support: 

    Have your end-users try to solve their problem by showing them a Zingtree. If the customer is unable to find a solution,  they can submit a ticket to Freshdesk, which automatically includes the Q&A transcript of their session with Zingtree.

    You can submit a new ticket to your Freshdesk system right from inside Zingtree. This will include the transcript of the Zingtree session, and looks like this:

    Note how the ticket includes a transcript of the Zingtree session.

    Click the link below if you’d like to try a demo tree that generates a ticket in our Freshdesk sandbox:

    Demo

    Setup Overview

    It’s easy to set this up – here’s an overview of the process:

    1. Add a new Application to Zingtree for creating Freshdesk Tickets.
    2. Create a “Ticket Submitted” node.
    3. Create a “New Ticket” node to obtain the customer’s name, email, ticket subject, a 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:

    1. Log into your Zingtree account.
    2. Go to Account > My Apps.
    3. Select the Freshdesk: New Ticket App.
    4. Enter your Freshdesk API key and domain name. (Instructions are on the page.)

    5. Click Add Freshdesk App to save the new App.


    Create a “Ticket Submitted” Node

    When this node appears, a new ticket is added to your Freshdesk installation. This is the end result of pressing a “Submit Ticket” button inside the decision tree. You can create this node as follows:

    1. Go to Tools > Add Node.
    2. Add a new Content Node.
    3. Give the node a title, and any text you want to appear in the content area – like “Thanks for submitting a ticket” etc.
    4. Click the Apps/Webhooks tab.
    5. Click Add App/Webhook.
    6. 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:

    • Name
    • Email
    • 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

    1. Edit the node where you want the customer to submit the ticket.
    2. Click the Data Entry Fields tab.
    3. Add fields for fd_name, fd_email, fd_subject, fd_description. When you are done, your Data Entry Fields will look something like this:

    4. You can also optionally add Custom Fields into 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. *See below for a note on best practices when building trees for Freshdesk. 
    5. If you want to set the ticket status and priority, you can also use variables named fd_status and fd_priority. This is optional.
    6. 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.
    7. Click the Action Buttons tab, and add a “Submit” button to go to your submit ticket page.
    8. Save the changes to this node.

    Best Practices

    When building and testing trees that utilize custom field names from Freshdesk we recommend using a persistent button with the ##ALL DATA## variable. This will allow you to see the custom field names that Freshdesk is passing to Zingtree in your Freshdesk interface. Once you've added these variable names to your Zingtree you can remove the ##ALL DATA## persistent button.

    Summary

    Examine this tree from the Demo Gallery to see a real live setup.

     

    Adding Your Zingtree Troubleshooters to Your Freshdesk Portal:

    The best way to decrease the number of tickets your Agents receive in Freshdesk is to display your Troubleshooters directly on your Freshdesk Portal page. This will encourage your customers to step through the Zingtree Troubleshooter before submitting a ticket. Here's how to add your Troubleshooters to your portal pages in Freshdesk:

    • First copy the embed code of the tree you'd like to display:

      1. Click the My Trees button at the top of the screen.
      2. Choose the tree to embed.
      3. Select Publishing Links.
      4. Click Embed your tree into any web page. See this article if you'd like to configure advanced options.
      5. Copy the embed code.

      Now paste the embed code into your Freshdesk portal page. Here's how:

      1. In your Freshdesk Admin, select Portals in the Support Channels section.
      2. Click the Customize Portal button for the portal that you'd like to display your Troubleshooter.
      3. Choose the Layout & Pages tab at the top. Then choose Portal Pages.
      4. You can place your Troubleshooter on any page of your portal. We recommend the Portal Home page.
      5. Paste your embed code wherever you would like the Troubleshooter to appear. 

       

       

      The example above would place your Troubleshooter at the top of the Portal Home page. Like this:

       

       

       

  • Zingtree and Freshdesk work well together. You can integrate both products in two ways:

    For Call Centers or Live Support:

    Your agents can open a Zingtree within the customer's Freshdesk ticket, and this script can guide an agent to the proper solution.  If another agent takes over the call, he/she can resume the session at the last stopping point, and see the steps the caller took with the previous agent.

    This is how the Agent script appears in Freshdesk:

     




    If you’re running live support or a contact center with Freshdesk, you’ll want to use the latest Zingtree Freshdesk app for Agent Scripting. This update supports the new Freshdesk Mint interface and helps guide live agents to solve problems and follow processes.


    Get Started

    Install this custom app from the Freshdesk App Marketplace as follows:

    1. Go to your Freshdesk Admin, and click on Apps (under Helpdesk productivity).
    2. Click Get More Apps.
    3. Search for “Zingtree”, and click the Zingtree App.
    4. Click Install.

    Freshdesk may take up to 30 minutes for your app to be available.

    Configure your App

    There are two settings for your app:

    • The tree ID of the tree you want to appear first (required). The default just shows all the data variables passed into Zingtree.
    • An option to send data from your Freshdesk ticket to Zingtree. If you enable this, you’ll be able to show information from the ticket in your decision tree or do automatic branching using Logic Nodes.


    Using the Agent Scripting App

    When viewing a ticket, click the Zingtree button at the top:

    The decision tree you configured will appear.

    Features

    Zingtree decision trees are easy for anyone to use immediately. But there are a couple of bonuses under the hood you will appreciate:

    • Pause and Resume: When you reload a ticket and click the app button, the decision tree will return to the last place visited. In addition, you can click the History link to see what transpired previously. This is really helpful if a call is dropped, or if a ticket is transferred to a new agent.
    • Instant Notes: With a single click, agents can add internal notes to a ticket from a template you provide. This can include the transcript of the session, any data gathered, or anything else you like. These notes can then be edited before they are saved. This is a HUGE timesaver for your agents. Learn more here.
    • Agent Feedback: At the bottom right, you’ll see the Agent Feedback button.

    Your agents can click this to send comments back to the authors of the tree. This is a great way to continue to improve your knowledge base, and also involve your agents in the publishing process.

     

    For Customer Support: 

    Have your end-users try to solve their problem by showing them a Zingtree. If the customer is unable to find a solution,  they can submit a ticket to Freshdesk, which automatically includes the Q&A transcript of their session with Zingtree.

    You can submit a new ticket to your Freshdesk system right from inside Zingtree. This will include the transcript of the Zingtree session, and looks like this:


    Note how the ticket includes a transcript of the Zingtree session.

    Click the link below if you’d like to try a demo tree that generates a ticket in our Freshdesk sandbox:

    Demo

    Setup Overview

    It’s easy to set this up – here’s an overview of the process:

    1. Add a new Application to Zingtree for creating Freshdesk Tickets.
    2. Create a “Ticket Submitted” node.
    3. Create a “New Ticket” node to obtain the customer’s name, email, a ticket subject, a 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:

    1. Log into your Zingtree account.
    2. Go to Account > My Apps.
    3. Select the Freshdesk: New Ticket App.
    4. Enter your Freshdesk API key and domain name. (Instructions are on the page.)

    5. Click Add Freshdesk App to save the new App.


    Create a “Ticket Submitted” Node

    When this node appears, a new ticket is added to your Freshdesk installation. This is the end result of pressing a “Submit Ticket” button inside the decision tree. You can create this node as follows:

    1. Go to Tools > Add Node.
    2. Add a new Content Node.
    3. Give the node a title, and any text you want to appear in the content area – like “Thanks for submitting a ticket” etc.
    4. Click the Apps/Webhooks tab.
    5. Click Add App.
    6. Select the Freshdesk App you just created. You should see something like this:2022-05-31_10-53-15.png

       

    7. Click Save Changes to save this node.

    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:

    • Name
    • Email
    • 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

    1. Edit the node where you want the customer to submit the ticket.
    2. Click the Data Entry Fields tab.
    3. Add fields for fd_name, fd_email, fd_subject, fd_description. When you are done, your Data Entry Fields will look something like this:

      2022-05-18_12-45-23.png

    4. You can also optionally add Custom Fields into 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.
    5. If you want to set the ticket status and priority, you can also use variables named fd_status and fd_priority. This is optional.
    6. 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.
    7. Click the Action Buttons tab, and add a “Submit” button to go to your submit ticket page.
    8. Save the changes to this node.

      Best Practices
      When building and testing trees that utilize custom field names from Freshdesk we recommend using a persistent button with the ##ALL DATA## variable. This will allow you to see the custom field names that Freshdesk is passing to Zingtree in your Freshdesk interface. Once you've added these variable names to your Zingtree you can remove the ##ALL DATA## persistent button.


    Summary

    Adding Your Zingtree Troubleshooters to Your Freshdesk Portal:

    The best way to decrease the number of tickets your Agents receive in Freshdesk is to display your Troubleshooters directly on your Freshdesk Portal page. This will encourage your customers to step through the Zingtree Troubleshooter before submitting a ticket. Here's how to add your Troubleshooters to your portal pages in Freshdesk:

    First copy the embed code of the tree you'd like to display:

    1. Click the My Trees button at the top of the screen.
    2. Choose the tree to embed.
    3. Select Publishing Links.
    4. Click Embed your tree into any web page. See this article if you'd like to configure advanced options.
    5. Copy the embed code.

    Now paste the embed code into your Freshdesk portal page. Here's how:

    1. In your Freshdesk Admin, select Portals in the Support Channels section.
    2. Click the Customize Portal button for the portal that you'd like to display your Troubleshooter.
    3. Choose the Layout & Pages tab at the top. Then choose Portal Pages.
    4. You can place your Troubleshooter on any page of your portal. We recommend the Portal Home page.
    5. Paste your embed code wherever you would like the Troubleshooter to appear. 

     

     

    The example above would place your Troubleshooter at the top of the Portal Home page. Like this:

     

    • Zingtree and Freshdesk work well together. You can integrate both products in two ways:

      For Call Centers or Live Support:

      Your agents can open a Zingtree within the customer's Freshdesk ticket, and this script can guide an agent to the proper solution.  If another agent takes over the call, he/she can resume the session at the last stopping point, and see the steps the caller took with the previous agent.

      This is how the Agent script appears in Freshdesk:

       

       

      If you’re running live support or a contact center with Freshdesk, you’ll want to use the latest Zingtree Freshdesk app for Agent Scripting. This update supports the new Freshdesk Mint interface and helps guide live agents to solve problems and follow processes.

       

      Get Started

      Install this custom app from the Freshdesk App Marketplace as follows:

      1. Go to your Freshdesk Admin, and click on Apps (under Support Operations).
      2. Search for “Zingtree”, and click the Zingtree App.
      3. Click Install.

      Freshdesk may take up to 30 minutes for your app to be available.

      Configure your App

      There are two settings for your app:

      • The tree ID of the tree you want to appear first (required). The default just shows all the data variables passed into Zingtree.
      • An option to send data from your Freshdesk ticket to Zingtree. If you enable this, you’ll be able to show information from the ticket in your decision tree or do automatic branching using Logic Nodes.

      Using the Agent Scripting App

      When viewing a ticket, click the Zingtree button at the top:

      The decision tree you configured will appear.

      Features

      Zingtree decision trees are easy for anyone to use immediately. But there are a couple of bonuses under the hood you will appreciate:

      • Pause and Resume: When you reload a ticket and click the app button, the decision tree will return to the last place visited. In addition, you can click the History link to see what transpired previously. This is really helpful if a call is dropped, or if a ticket is transferred to a new agent.
      • Instant Notes: With a single click, agents can add internal notes to a ticket from a template you provide. This can include the transcript of the session, any data gathered, or anything else you like. These notes can then be edited before they are saved. This is a HUGE timesaver for your agents. Learn more here.
      • Agent Feedback: At the bottom right, you’ll see the Agent Feedback button.

      Your agents can click this to send comments back to the authors of the tree. This is a great way to continue to improve your knowledge base, and also involve your agents in the publishing process.

       

      For Customer Support: 

      Have your end-users try to solve their problem by showing them a Zingtree. If the customer is unable to find a solution,  they can submit a ticket to Freshdesk, which automatically includes the Q&A transcript of their session with Zingtree.

      You can submit a new ticket to your Freshdesk system right from inside Zingtree. This will include the transcript of the Zingtree session, and looks like this:

      Note how the ticket includes a transcript of the Zingtree session.

      Click the link below if you’d like to try a demo tree that generates a ticket in our Freshdesk sandbox:

      Demo

      Setup Overview

      It’s easy to set this up – here’s an overview of the process:

      1. Add a new Application to Zingtree for creating Freshdesk Tickets.
      2. Create a “Ticket Submitted” node.
      3. Create a “New Ticket” node to obtain the customer’s name, email, ticket subject, a 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:

      1. Log into your Zingtree account.
      2. Go to Account > My Apps.
      3. Select the Freshdesk: New Ticket App.
      4. Enter your Freshdesk API key and domain name. (Instructions are on the page.)

      5. Click Add Freshdesk App to save the new App.


      Create a “Ticket Submitted” Node

      When this node appears, a new ticket is added to your Freshdesk installation. This is the end result of pressing a “Submit Ticket” button inside the decision tree. You can create this node as follows:

      1. Go to Tools > Add Node.
      2. Add a new Content Node.
      3. Give the node a title, and any text you want to appear in the content area – like “Thanks for submitting a ticket” etc.
      4. Click the Apps/Webhooks tab.
      5. Click Add App/Webhook.
      6. 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:

      • Name
      • Email
      • 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

      1. Edit the node where you want the customer to submit the ticket.
      2. Click the Data Entry Fields tab.
      3. Add fields for fd_name, fd_email, fd_subject, fd_description. When you are done, your Data Entry Fields will look something like this:

      4. You can also optionally add Custom Fields into 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. *See below for a note on best practices when building trees for Freshdesk. 
      5. If you want to set the ticket status and priority, you can also use variables named fd_status and fd_priority. This is optional.
      6. 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.
      7. Click the Action Buttons tab, and add a “Submit” button to go to your submit ticket page.
      8. Save the changes to this node.

      Best Practices

      When building and testing trees that utilize custom field names from Freshdesk we recommend using a persistent button with the ##ALL DATA## variable. This will allow you to see the custom field names that Freshdesk is passing to Zingtree in your Freshdesk interface. Once you've added these variable names to your Zingtree you can remove the ##ALL DATA## persistent button.

      Summary

      Examine this tree from the Demo Gallery to see a real live setup.

       

      Adding Your Zingtree Troubleshooters to Your Freshdesk Portal:

      The best way to decrease the number of tickets your Agents receive in Freshdesk is to display your Troubleshooters directly on your Freshdesk Portal page. This will encourage your customers to step through the Zingtree Troubleshooter before submitting a ticket. Here's how to add your Troubleshooters to your portal pages in Freshdesk:

      • First copy the embed code of the tree you'd like to display:

        1. Click the My Trees button at the top of the screen.
        2. Choose the tree to embed.
        3. Select Publishing Links.
        4. Click Embed your tree into any web page. See this article if you'd like to configure advanced options.
        5. Copy the embed code.

        Now paste the embed code into your Freshdesk portal page. Here's how:

        1. In your Freshdesk Admin, select Portals in the Support Channels section.
        2. Click the Customize Portal button for the portal that you'd like to display your Troubleshooter.
        3. Choose the Layout & Pages tab at the top. Then choose Portal Pages.
        4. You can place your Troubleshooter on any page of your portal. We recommend the Portal Home page.
        5. Paste your embed code wherever you would like the Troubleshooter to appear. 

         

         

        The example above would place your Troubleshooter at the top of the Portal Home page. Like this:

         

         

         

    • Zingtree and Freshdesk work well together. You can integrate both products in two ways:

      For Call Centers or Live Support:

      Your agents can open a Zingtree within the customer's Freshdesk ticket, and this script can guide an agent to the proper solution.  If another agent takes over the call, he/she can resume the session at the last stopping point, and see the steps the caller took with the previous agent.

      This is how the Agent script appears in Freshdesk:

       




      If you’re running live support or a contact center with Freshdesk, you’ll want to use the latest Zingtree Freshdesk app for Agent Scripting. This update supports the new Freshdesk Mint interface and helps guide live agents to solve problems and follow processes.


      Get Started

      Install this custom app from the Freshdesk App Marketplace as follows:

      1. Go to your Freshdesk Admin, and click on Apps (under Helpdesk productivity).
      2. Click Get More Apps.
      3. Search for “Zingtree”, and click the Zingtree App.
      4. Click Install.

      Freshdesk may take up to 30 minutes for your app to be available.

      Configure your App

      There are two settings for your app:

      • The tree ID of the tree you want to appear first (required). The default just shows all the data variables passed into Zingtree.
      • An option to send data from your Freshdesk ticket to Zingtree. If you enable this, you’ll be able to show information from the ticket in your decision tree or do automatic branching using Logic Nodes.


      Using the Agent Scripting App

      When viewing a ticket, click the Zingtree button at the top:

      The decision tree you configured will appear.

      Features

      Zingtree decision trees are easy for anyone to use immediately. But there are a couple of bonuses under the hood you will appreciate:

      • Pause and Resume: When you reload a ticket and click the app button, the decision tree will return to the last place visited. In addition, you can click the History link to see what transpired previously. This is really helpful if a call is dropped, or if a ticket is transferred to a new agent.
      • Instant Notes: With a single click, agents can add internal notes to a ticket from a template you provide. This can include the transcript of the session, any data gathered, or anything else you like. These notes can then be edited before they are saved. This is a HUGE timesaver for your agents. Learn more here.
      • Agent Feedback: At the bottom right, you’ll see the Agent Feedback button.

      Your agents can click this to send comments back to the authors of the tree. This is a great way to continue to improve your knowledge base, and also involve your agents in the publishing process.

       

      For Customer Support: 

      Have your end-users try to solve their problem by showing them a Zingtree. If the customer is unable to find a solution,  they can submit a ticket to Freshdesk, which automatically includes the Q&A transcript of their session with Zingtree.

      You can submit a new ticket to your Freshdesk system right from inside Zingtree. This will include the transcript of the Zingtree session, and looks like this:


      Note how the ticket includes a transcript of the Zingtree session.

      Click the link below if you’d like to try a demo tree that generates a ticket in our Freshdesk sandbox:

      Demo

      Setup Overview

      It’s easy to set this up – here’s an overview of the process:

      1. Add a new Application to Zingtree for creating Freshdesk Tickets.
      2. Create a “Ticket Submitted” node.
      3. Create a “New Ticket” node to obtain the customer’s name, email, a ticket subject, a 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:

      1. Log into your Zingtree account.
      2. Go to Account > My Apps.
      3. Select the Freshdesk: New Ticket App.
      4. Enter your Freshdesk API key and domain name. (Instructions are on the page.)

      5. Click Add Freshdesk App to save the new App.


      Create a “Ticket Submitted” Node

      When this node appears, a new ticket is added to your Freshdesk installation. This is the end result of pressing a “Submit Ticket” button inside the decision tree. You can create this node as follows:

      1. Go to Tools > Add Node.
      2. Add a new Content Node.
      3. Give the node a title, and any text you want to appear in the content area – like “Thanks for submitting a ticket” etc.
      4. Click the Apps/Webhooks tab.
      5. Click Add App.
      6. Select the Freshdesk App you just created. You should see something like this:2022-05-31_10-53-15.png

         

      7. Click Save Changes to save this node.

      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:

      • Name
      • Email
      • 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

      1. Edit the node where you want the customer to submit the ticket.
      2. Click the Data Entry Fields tab.
      3. Add fields for fd_name, fd_email, fd_subject, fd_description. When you are done, your Data Entry Fields will look something like this:

        2022-05-18_12-45-23.png

      4. You can also optionally add Custom Fields into 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.
      5. If you want to set the ticket status and priority, you can also use variables named fd_status and fd_priority. This is optional.
      6. 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.
      7. Click the Action Buttons tab, and add a “Submit” button to go to your submit ticket page.
      8. Save the changes to this node.

        Best Practices
        When building and testing trees that utilize custom field names from Freshdesk we recommend using a persistent button with the ##ALL DATA## variable. This will allow you to see the custom field names that Freshdesk is passing to Zingtree in your Freshdesk interface. Once you've added these variable names to your Zingtree you can remove the ##ALL DATA## persistent button.


      Summary

      Adding Your Zingtree Troubleshooters to Your Freshdesk Portal:

      The best way to decrease the number of tickets your Agents receive in Freshdesk is to display your Troubleshooters directly on your Freshdesk Portal page. This will encourage your customers to step through the Zingtree Troubleshooter before submitting a ticket. Here's how to add your Troubleshooters to your portal pages in Freshdesk:

      First copy the embed code of the tree you'd like to display:

      1. Click the My Trees button at the top of the screen.
      2. Choose the tree to embed.
      3. Select Publishing Links.
      4. Click Embed your tree into any web page. See this article if you'd like to configure advanced options.
      5. Copy the embed code.

      Now paste the embed code into your Freshdesk portal page. Here's how:

      1. In your Freshdesk Admin, select Portals in the Support Channels section.
      2. Click the Customize Portal button for the portal that you'd like to display your Troubleshooter.
      3. Choose the Layout & Pages tab at the top. Then choose Portal Pages.
      4. You can place your Troubleshooter on any page of your portal. We recommend the Portal Home page.
      5. Paste your embed code wherever you would like the Troubleshooter to appear. 

       

       

      The example above would place your Troubleshooter at the top of the Portal Home page. Like this:

  • Throughout 2022 Zingtree will be upgrading customers to our new faster and more modern user experience! Here's how to tell which experience your Zingtree Authors are currently using.

    Log in to your Zingtree Author account and navigate to My Trees. How does your current My Trees page look?

    Zingtree Classic

    2022-02-25_12-24-51.png

    New User Experience

    mceclip0.png

Was this article helpful?

0 out of 0 found this helpful

Have more questions? Submit a request