Category Archives: Zingtree News

Freshdesk Agent Scripting App

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.

With a single button click, your decision trees appear like this in Freshdesk:

Note: This app will appear in the Freshdesk App Marketplace soon, but here’s how to install it today.

Get Started

Install this custom app in Freshdesk as follows:

  1. Go to your Freshdesk Admin, and click on Apps (under Helpdesk productivity).
  2. Click the Custom Apps tab, then New Custom App.
  3. Click Add New App. Then choose Custom App.

  4. Download the app from here.
  5. Now, choose the file you just downloaded, and click Upload App File.
  6. Enter a name for the app, and any other required information. Then click Publish.

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

Install and Configure your App

Once uploaded, you can install your new app as follows:

  1. Click the Admin icon, then Apps.
  2. Click the Custom Apps tab.
  3. Click Get Custom Apps.
  4. Choose the app you just uploaded.
  5. Click Install.
  6. Configure your app (see below) and click Install.

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.

  • 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.

 

 

Streamlining HR with More Automated Business Processes

The global shift into utilizing automated processes in business is well underway; optimizing procedures for every department of your business is a highly critical factor of success. Streamlining business processes in a way that can reduce steps, lessen mistakes, and help guide employees on the correct path every single time is an investment that’s well worth it – this is exactly why we created our own Task Manager tool to help enhance these daily, repetitive business processes.

Human Resources is one such department within organizations that should always be included in the shift to greater, more involved automation. Because these roles so heavily rely on following strict procedures, enacting the correct protocols, and ensuring that every detail is in place, HR is the perfect candidate for benefitting from a more streamlined way of doing things. In this article from Forbes, the author dives into how automation and streamlining of business processes can solve some of HR’s biggest challenges today.

Attracting and retaining top-notch talent is one of the top factors influencing success for organizations in the 21st century. As a result, HR has become your most important departments, and it’s crucial to ensure that it’s properly resourced. Unfortunately, most business can neither afford nor find a well-staffed HR department.

The fact is that most HR processes are still very manual and document-driven, and HR specialists waste too much time on administrative paperwork. By automating these processes, streamlining operations, optimizing workflows and cutting out waste, your HR employees can spend more time focusing on what they’re passionate about: people.

The good news is that with its administrative processes like employee onboarding and time tracking, HR is particularly ripe for automation.

The main idea we’re trying to emphasize here, with help from this piece, is that HR is a perfect department to be optimized through more automated and streamlined processes via interactive decision trees. With repeated tasks like onboarding new hires, time-tracking, approvals, and more, almost every facet of the job can be improved.

There are several main benefits of automating these business processes for HR, as explained in the article, such as:

  1. Driving better employee engagement
  2. Reducing paper
  3. Closing communication gaps
  4. Collaborating to enhance productivity
  5. Reducing manual work
  6. Reducing email for speedier approvals
  7. Increasing focus on what matters — people

Attracting and retaining top-notch talent is a critical HR challenge in today’s workplace. HR automation has a lot to offer, yet many organizations have been too slow to adopt it. Will your HR department in 2020 still be mired in paper-intensive, error-prone and time-consuming manual processes? Or, will you use modern, low-cost platforms to automate and free the HR department to focus on what’s important: talent?

Read the rest of the article on Forbes. 

We’ve been providing HR, customer support, and other key organizational departments with the interactive tools needed to streamline procedures. With Zingtree decision trees for internal uses, teams can follow the most standardized and perfected processes in order to get more done with less energy, money, and zero error. And, with Zingtree task manager, you can streamline every repetitive process and task within one easy-to-use platform.

Try a working version of the Task Manager here and check out our demo video right here to see exactly how it works:

More articles about how to streamline and automate business processes:

Any questions? Get in touch with our team anytime!

Updating Salesforce Cases from Decision Trees

salesforce and zingtree

If you are launching Zingtree decision trees from within Salesforce, you have the ability to update the case record from any node of your tree. Here’s a summary of how to do it:

  1. Make sure your Agent Script button or link is set up according to this article.
  2. Add a Connected App to your Salesforce.
  3. Add the Salesforce Object Updater app to your organization within Zingtree.
  4. On any node in your tree, have the app trigger to update the case.
  5. Any Zingtree variables that begin with sf_ will update the corresponding field in Salesforce.

Adding a Connected App in Salesforce

To set up your Salesforce Connected App:

  1. Login into Salesforce and navigate to Setup, Create, Apps.
  2. Under Connected Apps, click New.
  3. Fill in the mandatory fields.
  4. Check the Enable OAuth Settings box.
  5. In the Callback URL field, enter this URL:
    https://zingtree.com/apps/salesforce/auth.php
  6. Under Available OAuth Scopes select:
    Perform requests on your behalf at any time (refresh_token, offline_access)
    Access your Basic Information (id, profile, email, address, phone)
  7. Your OAuth configuration should look like this when finished:

  8. Click Save and make a note of the generated Consumer Key and Consumer Secret. These need to be entered in the next step.

Adding the Salesforce Updater App

To add the App, do the following:

  1. Make sure you are logged into your Zingtree account.
  2. In Zingtree, go to Account, My Apps.
  3. Select the Salesforce Object Updater app.
  4. Enter your Consumer Key and Consumer Secret from the previous task.

    Click Continue.

  5. Allow access to your Salesforce account. (You may need to log into the account first.)

The Salesforce: Object Updater App will now appear in the list of Apps in My Apps.

Triggering a Salesforce Object Update

Once the App is installed in your organization, you can trigger a Salesforce update from any node in your tree.

  1. Edit the node in Zingtree where you want the update to occur. When this node is reached by an end user, the updater app will trigger.
  2. Under Apps/Webhooks, select your new app Salesforce: Object Updater.

     

  3. Click Save Changes.

 

Setting up Variable Names

As a part of your Zingtree session, you can collect data variables. Any variable that starts with sf_ will be used to update the corresponding field in Salesforce. For example, if you have a Salesforce field named description, a Zingtree variable named sf_description will be used to update that field.

Adding a Session Transcript

To include the Q&A history of the Zingtree session in a case field, you need to add a special field named Zingtree_Transcript to your Salesforce Cases.

In Salesforce:

  1. Go To Setup, Build, Customize, Cases, Fields.
  2. Scroll down to Case Custom Fields, and add a new field.
  3. The Data Type should be Text Area (Long). Click Next.
  4. The Field Name must be Zingtree_Transcript. Other parameters are your choice. See this example:


    Enter the other parameters, then click Next.

  5. Make the field read-only for all users, then click Next.
  6. Pick the Case Layouts where this information will be displayed, then click Save.

Troubleshooting

In case things aren’t working as you expect, here’s what to look out for:

  1. Changes to your case may not be reflected right away. Sometimes reloading the case (refreshing the page) will show the updates.
  2. If a Zingtree variable starting with sf_ has no field name counterpart in Salesforce, then the update will fail.
  3. You can check the Zingtree Event Log (Account, Event Log) to see all operations with Salesforce. This will show successes and failed updates, with error messages in case of failure.

5 Reasons Why Shoppers Might Hate Navigating Your Website

navigating website

Your customer-facing website is meant to be an environment that welcomes, informs, engages, supports, and converts. So why is it that most users only stay on the webpage they landed on for less than 59 seconds?

Everywhere you look online, you can find examples of websites and eCommerce stores that don’t necessarily meet today’s standards of customer ease-of-use. And, while a site visitor could have gotten their answer or information they were seeking within that single webpage in 59 seconds, it’s far more likely that something just isn’t working for your target audience. With eCommerce expected to hit $4.5 trillion in 2021 (Statista) and consumers’ risings expectations for flawless, seamless web experiences to browse and purchase your products or services, it’s more important than ever to pay attention to where your site may be lacking.

There could be any number or combination of reasons why customers might not enjoy navigating your website. We’re shedding some light on a few of the most common issues that eCommerce sites run into.

1. Your products and services are hard-to-find

Poorly-designed menus, hidden information, and clunky sub-categories are responsible for a huge amount of customer dread when it comes to navigating eCommerce sites. A whopping 41% of online shoppers cite this as being a reason for disliking a website; jumping through digital hoops to find what they’re looking for just doesn’t cut it.

Having a well-organized menu of web pages and easy-to-use product finders are a fantastic method for helping customers to help themselves and find just what they need. From selecting a pair of sunglasses to figuring out the best type of bike, Zingtree product finders are the easiest way to locate specifics among a robust product offering.

2. You have poor search functionality

Search is at the core of every eCommerce website’s ability to convert customers quickly and easily. Incredibly basic search functions that don’t even use filters to refine the results can be a frustrating experience. With a poor system fleshed out for searching products, support information, and other FAQs, customers will feel lost in your website and be much quicker to abandon ship.

The more complex your product or service offering, the more advanced your search functionality should be in order to keep up with customer needs. eCommerce search tools that are efficient and effective have shown to prolong a customer’s visit to your website and is far more likely to encourage a sale.

3. You haven’t optimized your site for mobile

It’s safe to say that mobile shoppers are now officially outnumbering desktop-only online shoppers. Mobile eCommerce sales account for 34.5% of total eCommerce sales in 2017, and that number is growing still. If your mobile eCommerce site leaves something to be desired, or if it’s completely non-functional, it’s time to make it a priority.

If a customer on a smartphone opens up your website to find and purchase a product, and that mobile site is difficult to navigate, loading slowly, or clearly not set up to support such dimensions, they will leave immediately and not come back. When making final purchases and using online bill pay, this becomes even more important to remain competitive.

Image via UserZoom

4. Your design leaves something to be desired

While we may teach not to judge a book by its cover, the look and feel of your eCommerce site means absolutely everything. In fact, many consumers won’t even make a purchase from a website they don’t feel has a trustworthy appearance. If your customers type in your URL and get launched into a UI from the early 2000’s, the urge to find somewhere more visually pleasing to do their shopping is inevitable.

Website design directly correlates with how customers determine whether they believe you to be a reliable, professional company. 95% of users indicated that a positive user experience is the most important factor when they visit a website (Econsultancy). In addition, Forrester has reported that your website’s conversion rate could increase by 200 to 400% with a well-designed interface.

5. You don’t have an FAQ

When any type of purchase is involved, customers will consistently have questions about shipping, returns, manufacturing, and other specific details of your business and its products. Having a Frequently Asked Questions (FAQ) section that’s easy to locate, scan through, and find what you need saves your customer valuable time and improves your eCommerce site’s conversion rates.

Interactive FAQs and customer support decision trees were designed with this in mind, offering a powerful platform for customizing and publishing an in-depth, yet concise knowledge base of information. With an interactive element that’s simple to search through and find just what’s needed, customers feel empowered to solve their own problems without getting in touch with your eCommerce business directly.

 

Ready to learn about how Zingtree’s powerful toolkit can help you create interactive FAQs and product finders that will keep customers happy, engaged, and converting? Get in touch, be sure to check out our example decision trees, and read up about our solutions for eCommerce and retail businesses. 

Zingtree Updates: September 2018 – Labor of Love

Just in time for Labor Day, here’s what’s been happening at the Zingtree labs this summer! With a new Task Manager, PDF capability for Document Nodes, renumber and merge trees, and some more notification options are the highlights, we’re really excited about the progress we’ve made over the last several weeks.

See all of our improvements since June 2018 below:

New Features

  • Task Manager tool: Business Process Management, using Zingtree decision trees.
  • Renumbering nodes: You can now renumber nodes using the new option in the Copy Tree tool.
  • Combine trees: Make two trees into one using the new Merge Trees tool.
  • PDF generation: Document Nodes can now create PDF files.
  • History and Breadcrumbs: Embedded trees now have URL switches for embed_history or embed_breadcrumbs (various).
  • Push Live update flag: For trees with Push Live, DEV trees with updates since last push live now show with a red icon in My Trees (thx Lasse).
  • Event Log: See failed emails, login attempts and more from Account > Event Log.
  • Simple SMS, email & Slack notifications: From new built-in Apps under Account > My Apps.
  • Multiple apps: You can now have several apps/webhooks on a single node.
  • Better receipts: Customer receipts now have a PDF download option.
  • Erase variables: There’s now a Zingtree Erase Variables stock webhook (for Pharoah).

Updates and Minor Improvements

  • Agent feedback comments on a LIVE tree now always go to DEV version of the tree (Ian M.).
  • Preview now includes a feedback button (customer request).
  • “Lookup credits” are now “Enhanced Usage” credits.
  • Now shows “please wait” when loading traffic map (button clicks) report.
  • Added “please wait” message to long tree loads.
  • CSS templates now display white text in HTML <btn> tags (used in adding buttons to node contents).
  • Preview tool shows back, restart button options.
  • Added hint for webhook calls in the node editor.
  • Uploads now go to uploads.zingtree.com instead of zingtree-uploads.s3.amazonaws.com.
  • Doesn’t show “back” or “restart” on the starting node (Various customers requested this).
  • Right-to-left (Hebrew) display for History bar looks better (for Tal).
  • New WordPress plug-in 5.0 supports history, breadcrumbs.
  • Reorganized My Apps page.
  • Node labels in button choices in content node editor now use node titles (if available).
  • Session Details report cleaned up.
  • “Unknown” result label changed to “In Progress.”
  • Drawing return-to links from tree nodes now supported in Designer.
  • Content Node editor loads faster (thx Oliver).
  • Multi-tree API calls sped up.
  • Link control in the editor and new link nodes now defaults to “new tab” (Jonathan B.).
  • Content editor no longer shows link option for Google, Facebook, Froala.
  • Content editor links now have a tooltip option.

Fixes

  • Linking from LIVE to DEV tree now shows proper tree ID of DEV tree in session data.
  • PNG export looks for invalid characters that can break it.
  • PNG export is better at framing the content of the tree in the PNG.
  • Copied trees now show current date and time for “last opened” – appears at top of the list in My Trees.
  • Adding new merge variables in a pause and resume scenario now works consistently (Lasse).
  • SSO author login errors no longer stay stuck unable to log in.
  • Empty checkbox score no longer crashes form field data update (Jay H.)
  • Double-quoted strings now work OK in Logic Node editor, Designer for Logic Nodes.
  • Single quotes no long make Zapier transfers fail (Alok).
  • Now says “new logic node” instead of “new scoring node” in an alert message when creating a new logic node.
  • Doc node Continuation buttons now use theme.
  • Searching linked trees used the wrong search when a fade transition was in effect.
  • MailChimp API calls changed to always use a secure connection – now works properly again (Jonathan T.).
  • Form field labels in the content editor no longer show HTML codes instead of single quotes (Kwame A.).
  • Document node continuation button editor now shows email nodes correctly.
  • Breadcrumbs and history restore to the same state when pause & resume is triggered after a ##treetag-any## or ##treetag-all## link is clicked (Tal).
  • Custom CSS generator now ensures variables have values – won’t show error messages.
  • Layout for Snapshots tool now better for action buttons on one line.
  • Now allows multiple simultaneous people to use Agent Portal or Task Manager demos.
  • Centering videos now works properly.
  • Task manager login page no longer redirects to agent login page if the session is no longer valid.
  • Session click history output when included in a node now also includes blank questions in the click path – substituting page titles instead (Tatiana).
  • User-only text now hidden in subtrees when in agent mode (Kelly S.).
  • Thumbnails overview now shows “auto-send” for auto-send email nodes.
  • Sending email when the main tree was pushed LIVE and subtree was DEV now works as expected (Rachel D.).
  • Fixed bug with Tree tag links not working after restart.
  • Tree-node node selector now shows updated labels.
  • Rendering engine faster for large trees with many variables (Lee S.).
  • Shows stock apps in Settings/Code selector.
  • Inviting authors always allows people to continue signup.
  • Auto-send from email nodes no longer logs click text from the previous click.
  • Email input form now displays wider on small devices (Christiaan).
  • Edit, Copy buttons for auto-email nodes in Thumbnails overview now works as expected (Ian M.).
  • Tree rendering now handles improper UTF-8 characters (Thai).
  • DEV trees no longer show in Agent Portal search results (Angie H.).
  • CSV import now handles UTF-8 characters properly (Emma V.).
  • API speed updates for find_agent_sessions, find_tree_sessions.
  • Editing code in pop-up Content Node editor now highlights properly (Matthieu).
  • Empty webhook return no longer causes JS error.
  • Tags now allow Hebrew characters (Tal).
  • Now replaces #session# in email node templates for auto-send (Lasse).
  • Phone number validation no longer fails if there’s a space inside the phone number.
  • Retina display of screenshots now works properly in Wizard, Designer tutorials.
  • New email form nodes now include session data.
  • Email form node shows default text if no continuation text specified (for Legacy forms).
  • Email form nodes properly show “please wait” when Send is clicked.

That’s it! Keep an eye on all of our product updates, and feel free to reach out with any questions, anytime. 

Service Issue – September 2-3, 2018

We experienced a temporary issue with saving data from approximately 12 PM PST September 2, to 12 PM PST September 3. This was caused by an update which passed our QA process, but nevertheless had issues.

The functionality of trees worked properly, but any data collection during that time may not have worked properly for some trees.

Going forward, we’ve updated our build process to ensure this particular issue does not resurface again. Our apologies if this affected your operation in any way.

Thanks for your patience, and continued support of Zingtree.

P.S. If you are using Agent Portal, we may be able to recover raw data from the outage period. Just ask us on chat.

Decision Trees for Business Processes – The Zingtree Task Manager Tool

Business Process Management with Zingtree

Overview

One of the more common, interesting uses for interactive decision trees is as an online task management tool for streamlining recurring business processes. These are standardized workflows that have a series of repeatable steps, which may need to involve handoffs to different people on a team or even in another department. For example, your company may have an approval process for:

  • making purchases
  • approving project budgets
  • hiring or firing employees
  • creating blog posts (like this one!)
  • and any other repetitive tasks or processes your business uses

The Zingtree Task Manager is a dashboard for guiding your coworkers through decision-tree-based processes created using the Zingtree tools.  This makes it easy for everyone to be held accountable, and to follow standard operating procedures.

Here’s a diagram of a simple purchasing process:

In this case, if the item is under $100, then the request is approved automatically. Otherwise, a manager needs to approve the order.

Set Up

Creating your first business process with interactive decision trees is not complicated. It involves these steps:

  1. Enter your “agents” – the people who act upon your processes – and assign them to groups.
  2. Create a decision tree, and assign each node (step of the process) to one of your Agent Groups.
  3. Assign your tree(s) to various Agent Groups. Only people in those groups will be allowed to start or kill a project.

This article has full details on how to set up your first business process.

The Task Manager

The Zingtree Task Manager was built with full-team functionality in mind. Anyone involved in a work process can use standardized decision tree workflows to navigate through the procedure. Certain steps can only be completed by specific people, and once you reach a step where it’s no longer your responsibility, that task is assigned to someone else.

This article has a video and full reference for the Zingtree Task Manager.

For example, in the procurement process diagrammed above, an employee creates the purchase request and a manager approves or declines it if over $100.

Here’s how the Task Manager could appear for an individual:

When someone Takes or Resumes a task, it looks like this:

Groups

Each person involved in a process (an “agent”) can belong to one or more groups. You can configure people and groups via Account > My Agents. So for example, a small team with two employees and one manager is set up like this:

Note that “Bill Zing” belongs to both the manager and employee groups.

When creating your process trees, you can tag each tree with the groups that are allowed to start the process.

Assigning Steps in the Process using Tags

Each node of your business process tree needs to include the Agent Group(s) allowed to act on that step of the process. You can see how our procurement process tree’s groups (outlined in red) are set up here:

 

The initial request step (node #1) is tagged with “employee”, so only people in the employee group can initiate a request. Node #6 – the Manager approval step – is tagged as “manager”, so only a manager can approve the purchase.

Assigning Agent Groups to a node is done using the Groups tab when editing a node. Here’s how node #1 is set up for an employee group:

 

Project Status: Success, Failure or In-Progress

At the end of a workflow, a project is either successful or a failure. When building your process tree, you can assign a result to each node in the node editor – like this:

Once a node is reached with a success or failure result, the process has ended.

Notifications

A notification can be sent when any node (process step) is reached so that the next person can be alerted and step in for their task. Notifications can be sent in a few different ways, including:

  • A text message
  • A simple email notification
  • A Slack notification
  • A customized email (using an email node)

Task Manager Operations

Your agents – people involved in your processes – can perform the following operations on each task:

  • Start: Begin a new task, and assign it a name.
  • Take: Take over the next step of a task. Only one person at a time can move a task to the next step.
  • Release: Release a task so another person can complete the step.
  • Resume: Continue with a task that you have previously taken.
  • Revisit: Go back to a previous step in the task you have permissions to act upon.
  • Reclaim: Take back a task from someone who has taken it.
  • Kill: End a task early, without following all the steps to completion.

Go here for a full reference on the Task Manager


Got questions about using Zingtree for streamlining your repetitive business processes? Reach out to our team!

Using Zingtree’s Task Manager for Your Business Processes

Business Process Management with Zingtree

Once you’ve been set up as an “agent”, you can log in and start using the Zingtree Task Manager. You can easily check for tasks that are awaiting your action, see other tasks of interest and revisit them.

Watch this video for a quick two-minute tour of Task Manager basics:

This video shows more advanced operations:

 

Task Manager Test Drive

Want to use Task Manager just like a real person?

Try a working version of the Task Manager here.

Operations Reference

Click on any operation below to learn how it works:

Opening the Task Manager

To start, open the task manager and log in from here.

The task manager appears like this:

Starting a New Project

  1. From Task Manager, click Start a New Project.

  2. Click the Start button next to a business process workflow. The Start New Project screen appears:

  3. Give the project a name, and click Start New Project.

You can now click through your task steps in the project.

Taking or Resuming a Task

The task manager shows you tasks which require your attention, under My Tasks Needing Action.

Click Take It to act upon the task. If you’ve already taken a task, you can click Resume to continue the task you’ve taken.

Releasing a Task

If you’ve previously taken a task, but now you want to let someone else in your group act upon it, you can Release it. In the above example, if you click Resume, your task screen will have the option to release the task via the orange Release Task button in the upper right:

Reclaiming a Task

If someone else has taken a task, and you want to act upon it and override them, you can use the Reclaim option. Here’s how to do it:

From Other Projects in Progress, click the info button to the right:

This opens the project info pop-over:

Click the Reclaim button to give yourself access to this task.

Killing a Project

Sometimes a task will get started, and it turned out to be a bad idea. Using the same process as above, you can click the red Kill button to kill a project.

Killed projects will appear under the Completed Projects tab in Task Manager.

Revisiting a Task

There may be times when you want to go back to a previous step in a project. For example, in the PC Purchase project, the manager may have declined a purchase and then changed her mind.

When a task is opened, the Task Progress accordion shows the steps taken previously. Click the brown Revisit button next to a step to go back to that part of the business process workflow.

Viewing the History of the Project

The Task Progress accordion also shows each step in the project, who acted upon it, and when (see above). You can get even more history by selecting Show Click Detail at the bottom of the Task progress area. This shows you EVERY operation on the project, not just the summary.

See more about our online task management tool for streamlining business processes

How to Setup Zingtree Decision Trees for Business Processes

Business Process Management with Zingtree

Getting your organization ready to use business process decision trees via the Zingtree Task Manager is relatively simple.

Here’s an overview of the process:

  1. Setup your organization to use the Task Manager.
  2. Create your “agents”, and assign them to one or more Agent Groups.
  3. Create your decision trees for the workflows your agents will follow.
  4. Assign decision trees to your Agent Groups.
  5. Assign the steps in your workflows to your Agent Groups.
  6. End the workflows with Success or Failure.

Setting Up Agents and Task Manager

To enable your organization top use Task Manager, start by going to Account > My Agents. Select Task Manager for agent logins, like this:

Next, you’ll need to add agent logins – one for each person who will be using the system. Click Add One New Agent, the enter the agent’s name, a login (usually their email), a password, and what groups they are assigned to, like this:

The groups will be used later to determine who is allowed to act on each step of the workflow. In the above example, Joe Smith is assigned to the employee group.

Assigning Decision Trees for Agent Groups

Each tree you create can be assigned to one or more groups. Any agent in the assigned group can start a new project using that tree as a business process workflow. This is done via the Settings tool.

For example, if we want Joe Smith to be able to run a procurement process decision tree, we would assign that tree to the employee group, as follows:

  1. Select the tree from My Trees.
  2. Open the Settings tool.
  3. Under the Groups tab, enter the group or groups to assign to this tree.

Here we entered the employee group:

Be sure to click Update All Settings when finished!

Assigning Nodes to Agent groups

Each step in the business process workflow corresponds to a node in your decision tree. And just like trees, you can assign nodes to agent groups. This has the effect that only agents in that group can act upon a specific node.

Here’s how to assign a group or groups to a node:

  1. Edit the node.
  2. Go to the Groups tab, and enter the group or groups that are allowed to act on this node.

It will look like this:

Click Save Changes when finished.

Now, repeat this for the other nodes in your tree.

Setting Endpoints

A project ends when you reach a node that has a “success” or “failure” result on it. You can set the result of the node as follows:

  1. Edit the node.
  2. Set the Result to Success or Failure, from here:

Handy Tips

Tip #1: The name of the current task can be used as a variable in your tree. Just enter #task_name# where you want the name of the task to appear.

Tip #2: You can see the results and the groups for every node in a tree from the Simple Overview tool. Here’s a procurement tree with the Results and Groups highlighted:

Tip #3: For all your trees, you can see the Agent Groups allowed to start a project via My Trees. Like this:

See more about our online task management tool for streamlining business processes

Decision Tree Updates: June 2018

Over the last six weeks, we’ve been focusing resources on improving tasks that have been the topics of our most frequent conversations with customers. In general, here’s what we’ve improved:

Here are the details of everything that’s changed:

Visual Designer

For more details on what’s new in Designer, see this post.

  • Update: Question and Answer nodes are now just “Content” nodes.
  • Fix: Designer no longer shows things like &apos; in labels.
  • Fix: Designer no longer hangs with “contains” operation in logic nodes.
  • Update: Designer shows better symbols in logic branches
  • Update: Can now move logic node branches in Designer
  • Update: Designer has no more “save” button. Changes are saved automatically.
  • New: Pop-up editor can now be used to edit button links or logic nodes. Changes appear instantly in the Designer view.
  • Fix: Adding nodes now makes them appear in the proper display order when viewing the tree in Simple Overview.
  • Update: Designer pop-ups can now change the root node.
  • Update: Removed Undo/Redo buttons.
  • Fix: Designer PNG export crops unneeded whitespace from the image file.
  • Update: Designer loads 2x faster!
  • Update: Unlinked buttons appear as red arrows and buttons.
  • Update: “unlinked” node position can be moved and saved.
  • Update: New node icons. These also appear in hi-res for Retina displays.
  • Fix: Button labels no longer occasionally return after being turned off.

Email Nodes

  • New Email Node option to automatically send email, and then continue to another node.
  • Creating email templates is much easier – no longer need to upload HTML files, or use a special link node.
  • You can customize the “Send Message” button for email forms.
  • After sending email, the next step can go to a new node instead of requiring a URL.

Document Nodes

  • New: Document node now has a button option which can continue the session at another node.
  • Update: Document node content selector now shows just content nodes with no to/from links.

Zendesk Agent Scripting App (Version 12)

  • Fix: Now properly sets or unsets checkbox custom fields (Tim J.)
  • Fix: New tickets now works properly in all cases (Linus P.)
  • New: Zendesk App Theme.
  • Version 12 now in Zendesk App Marketplace.

Other Updates

  • Update: Question and Answer nodes are now just “Content” nodes.
  • Update: New icons for all node types.
  • Fix: Editing nodes where there are a lot of variables in content editor list now loads faster (Oliver).
  • Fix: “return to Tree” tree node no longer adds unwanted variables to the list of options in Logic Nodes.
  • Fix: Wizard now properly sets display order for node reordering.
  • Fix: Simple Overview no longer shows nodes used in document nodes in the incoming link count.
  • Fix: Setting scoring value to ‘=0’ now resets the value to zero (Jay H.)
  • Fix: Persistent button link nodes from within a subtree now work properly (Lasse)
  • Fix: When editing a node, “Assign button click variable” no longer sometimes ticked when no variable is present.
  • Update: Added search to Gallery.
  • Fix: treetaglist macro no longer shows duplicate live and dev versions of matching trees. DEV master shows dev versions only when duplicates are detected, LIVE master shows live versions when duplicates are detected (Lasse)
  • New: Added Bootstrap Table styles in content editor (hover, border, striped, condensed) (Kim M, Rachel V, Justin B)
  • Fix: Entering values for scoring uses running total without requiring ‘+’ in front of number, as per documentation (Lisa F., Chad Y.)
  • Fix: Prevents variable names from starting with a digit (Gabriele P.)
  • Fix: Fade transition no longer shows last node when “back” is selected (John H, John K.)
  • Fix: Fade Transitions work properly with logic nodes (Werner G.)
  • Fix: Fade transitions and breadcrumbs now work properly (Ben M.)
  • Fix: Persistent nodes clicked from a subtree now hide last node properly with transition/fade effect.
  • New: GDPR page at zingtree.com/gdpr
  • New: Can now drag and drop document files into the content editor to upload them to our servers (PDF/DOC, etc.) (Lucas K.)
  • Fix: Kustomer integration now adds tags properly when jumping to the root node of a tree via a tree node (Katie)
  • Update: Periods now allowed in tags (Amanda D.)
  • Fix: No longer sending “score=” in Webhook calls for an empty score (John H.)
  • Fix: Adding, editing or removing collaborators from DEV version sets proper access to Live version (Lasse)
  • Update: Date picker now has expanded year ranges (Ronnie L.)
  • New: Can add extra emails for billing notifications (Tom M.)
  • Fix: Button click values like ‘123ABC’ now store as strings, not ints (was saved as 123) (Mark C.)
  • Fix: Default Theme updated so link colors are set properly.
  • Fix: Logic nodes drop-down selections now work when related trees have no variables.
  • Update: Link control in editor and new link nodes now defaults to new tab (Jonathan B.)
  • Update: Content editor no longer shows link options for Google, Facebook
  • Update: Content editor link manager now has a tooltip option.

As always, if you have any ideas to share with us on this or any other features, please let us know!