Category Archives: Product Updates

February/March 2018 – Decision Tree Updates

We’re still getting a ton of great ideas from our customers, as well as the occasional “I can’t do this” message. The last couple month’s updates primarily focus on the little details that set Zingtree apart from any other solution, but there are a few new goodies as well.

Here’s what’s new:

  • Settings/Data has options to include these variables in the session: tree_id, tree_name, last_tree_id, last_tree_name (for Tal)
  • Agent Feedback option for sending agent feedback emails to a specific address, instead of all authors. (Tara)
  • Agent Alerts
  • New API call get_session_data_pure – removes “back” and “restart” clicks from session path.
  • ##library tag to load content from another node.
  • Agent Portal specific login page
  • Deleting agent feedback comments now has an option to send a message as well (Tara).
  • Kustomer integration now adds tags to nodes (Katie)
  • Added full-width textbox data entry field type (Lasse)


Some updates to existing features:

  • Reorganized Settings/Data tab area.
  • Logic Node editor now has tabs – just like content editor.
  • Added “Export to CSV” checkbox option in main reports tool page.
  • Session List report now shows lookup credits used (if any were used).
  • Session List report: If no sessions appear for DEV version, we now show a button for LIVE version reporting.
  • Session detail report now shows questions by default, not page titles.
  • Logic nodes now show variables from trees linking to and from the current tree, up to 8 levels.
  • No longer adds “score” as a score variable for Email, Link, Tree nodes
  • Tags now allow Unicode characters (Alfred G.)
  • Google sign-on now allowed for agent portal (Kwame)
  • Asks new users to confirm T&C and Privacy Policy (GDPR compliance)
  • Better color palette in node editor (Dean S.)
  • API JSON now returns in pretty-printed format for easier readability
  • Feedback comments now show in user’s timezone (Ian M.)
  • Patched security vulnerability in session tracking
  • Added session_notes to available Zapier data (Alok)
  • Hyphens now allowed in tags (Isaac W.)
  • Using Zingtree CDN for fonts (Roger A.)
  • Added tags as tag_ classes to node rendering (John H.)
  • Allows locale= parameter to be sent along in host.php to override browser’s default locale (Alok)
  • Now sends organization name into agent portal as a variable (for Ted B.)
  • Persistent buttons now spaced farther apart
  • Hosting lots of assets at assets.zingtree.com for faster browser load speed. (Roger A.)


And some fixes and performance enhancements:

  • Agent feedback messages no longer include slashes before apostrophes in the message text.
  • Organizations being paid for by another org now can enable the referral icon in Settings. (Alfred G.).
  • No longer does address verification lookups when loading tree with preloaded addresses (Jay H.).
  • Form data report now faster (Kyra).
  • Sessions List report now faster.
  • Should see fewer 504 or 524 errors on big reports since we increased the server time-out.
  • Extra spaces in list box data entry fields get removed properly (Nellie).
  • get_session_data API call would occasionally show wrong questions when a subtree was involved (Mark C.).
  • Webhooks mechanism disallows null values and arrays in return data (Daniel)
  • Centering or right aligning images in text editor now renders properly. (Chris)
  • Source list drop-down in Sessions List report no longer missing some agents (Chrissie)
  • Disabling Push Live still loaded Live tree in Agent Portal, messed up tag matching. (Alexandra R.)
  • Ill-formed taglist macros no longer cause deploying trees to hang. (Tara D.)
  • Button override colors work properly in all cases.
  • Button override class markers (like .btn.red ) no longer show in history display
  • Animated templates now wrap buttons properly in IE.
  • Importing CSV spreadsheets no longer allows variables with space characters in them (Daniel)
  • Single quotes in button click variable values now works properly (Isaac W.)
  • Dynamically generated list boxes from webhooks can now retain their previous selection after “back” is clicked (Raj P.)
  • ##treetaglist and ##taglist macros can now be properly combined in a page (Lasse)
  • get_session_data API calls now removes style prefix (i.e. .btn-red) from button text
  • JSON export no longer loses last character on occasion, output is more readable (Alfred G.)
  • Pressing BACK from root node no longer erases merge variables. (Jay H)
  • Copying trees now includes placeholders, hidden fields (Jay H.)
  • Edit node error message no longer goes to 404 page (BD)
  • Super-user with no trees now can see trees by other authors and assign themselves rights.
  • keep_vars_on_back=1 parameter no longer erases form data if a “back” was hit after first node (Jay H.)
  • Improved XSS detection so that formatted data isn’t changed (Michael B.)
  • Jumping to a tree node now keeps the form data stack properly in sync (Lazarus P.)
  • Can now update the Google Analytics account by erasing it (Josh)
  • Empty drop list data entry variables no longer throw an error.
  • Messages from overview.php now display properly.
  • Login forms ensure cookie is set and present.
  • Tree names with single quotes no longer cause browser error.
  • Clicking tree nodes in Zendesk app now updates Zendesk variables properly.
  • Patched author and agent logins to prevent CSRF attacks (logins into an unexpected account).
  • Going back over scoring nodes with a subtree jump now works properly. (Katie)
  • Now properly scrolls Thumbnails overview to last edited node.
  • Browser back button now works properly in Preview tool.
  • Alert messages with @ in them now show (introduced from security fix).
  • Agent Portal – Hides DEV version of a tree if a live version is present (Matthieu).
  • Security Fix: Prevented URLs that can change emails or passwords of logged-in users.
  • Security fix: Locked down alerts system to display validated Zingtree-generated messages only.
  • Confirmation emails now use https for verification links.
  • Wizard tutorial page now up-to-date.
  • Uses new LIVE version of Designer help (with embedded video)

Got a suggestion for us? Just chat us up.

Agent Update Alerts for Call Scripting

Several contact center clients have asked for a way to display one-time notifications to agents when critical parts of an interactive decision tree have changed. This is easily accomplished using Zingtree’s Agent Update Alerts.

Overview

An agent alert appears like this:

Some key points about Agent Alerts:

  • The agent cannot continue to use the tree until they dismiss the alert.
  • Once the alert is shown to an agent, he/she will see it just once.
  • Alerts can appear on subtrees (trees launched via tree nodes), or the starting tree.
  • You can add and manage alerts from Account, My Agents, Agent Alerts.
  • Alerts are tied to specific trees. Currently, there are no universal alerts.
  • The Push Live mechanism has an easy way to optionally add an alert.
  • If you have multiple alerts set, they will be combined into a single alert message, rather than showing one-by-one.

Managing Agent Alerts

Alerts can be added, deleted or modified from a single place. Here’s how to manage them:

  1. Go to Account, My Agents.
  2. Click the red Agent Alerts button. The Alert Manager appears:

This page shows all active alerts for every tree in your organization. You can see alerts for specific trees by choosing the tree from the drop-down.

  • To add an alert, click the  Create New Alert button.
  • To delete an alert, click the delete icon next to an alert
  • To change the alert text, click the edit icon next to the alert.

Push Live Shortcut

If you’re using the Push Live tool, you can add an alert when you do a push.

Alerts created in this fashion can still be maintained using the Agent Alerts manager.


Alert us
if you find this feature useful, or have a suggestion to make it even better!

 

Decision Tree Improvements – January 2018 Updates

This past month’s updates include some new security and access restriction features, performance enhancements, interface improvements, and a variety of small bug fixes. Here are the details:

New Features

  • New Change Log report to show what authors have done. Also exportable to CSV.
  • New Hidden Field data entry type (for Ted B, Others)
  • New API calls for agent_add, agent_remove. (These are no-login agents.)
  • Google sign-in authentication for agents (for Benjamin)
  • Push Live tool
  • Server updates and extra capacity
  • Performance enhancements with smarter file caching. Added cache_tree URL parameter option.
  • Different Single Sign-on Identity Providers for authors and agents.
  • Internally logging security events (logins, failed logins, email sends, tree changes)
  • Single Sign-on logins for agent portal (Lynne H.)
  • ##include_url: ## template macro for loading data from 3rd party URLs
  • Agent Portal now has #agent_first_name# variable. (Craig S.)
  • Can now pass new merge variables into a pause-and-resume session (Geoff)

Updates

  • Updated Zendesk Agent Scripting App. New agent_tags variable included in URL, no more flashing when going between tickets.
  • Session summary from Zendesk app now shows which agent did which click (Sonny R.)
  • Add Agent can now use a no-login option.
  • Max video upload size is now 150 MB (from 50 Mb) (Darryl )
  • Session Info cookie is now protected by https.
  • Agent portal node search now includes node tags (Jonathan B)

Interface Enhancements

  • Reordered Add Node selections based upon popularity.
  • Reordered node icons in Designer by popularity.
  • New Tutorials and Videos.
  • Easier-to-use Edit Content Node. Now uses tabs to surface advanced options.
  • Pop-up editors in Designer now use more screen space.
  • Easier-to-navigate Settings tool uses tabs.
  • Tools pages and drop-down tools menu reorganized.
  • Consistent tree info display across tools.
  • Formatting of default hosted link on Publishing Tools page – removed extra spaces at front.
  • No more weird message when viewing gallery trees in Designer.
  • Node editor – Data entry fields no longer appear by default in question nodes.
  • Node editor – switching between question and answer types now keeps tabs straight.
  • Node editor – Dragging to reorder buttons or data entry fields now positions items properly in range of editor.
  • Reordering nodes in Simple Overview now shows node being moved in proper position.
  • Simple Overview no longer shows empty “Variables: “
  • Session Details no longer unnecessarily shows tree name from starting tree in each step.
  • Node editor no longer flashes a bunch of blank buttons when first loading.

Fixes

  • Archiving Development version of a tree also archives the live version (Vlad).
  • No longer showing button class overrides (i.e. .btn-red) in front of History (Tal D.)
  • Designer no longer adds “score” variable to new nodes.
  • Zapier interface handles newlines in data entry variables properly (i.e. Session History variable) (Gabe L.)
  • Importing session_history variable into a pause and resume session no longer causes a JS error (John H.)
  • #agent# now gets used as a variable in Agent Portal (Ted B.)
  • Space character in agent login no longer makes agent portal tree viewing fail (Gordon S.)
  • Cleaned up tree search tool for Live vs. Development trees.
  • Nodes with tree search forms now locate live or development versions depending on live/dev status of the originating tree.
  • Tree search nodes no longer always return results where page title had “search” in it. Also didn’t properly look for page titles.
  • FAQ and end-user tree searches no longer return every node when searching keywords “title”, “span”, and other HTML elements.
  • Zapier authentication no longer ignores fields that were once empty (Josh D).
  • Zendesk Agent App: Newline in Zendesk custom field or merge variable value caused no session to be saved.
  • Session Matrix report uses faster queries, no longer displays button formatting overrides.
  • Responsive image selection now works properly for all image insert operations.
  • Compare Trees tool no longer shows “Return to previous tree” as an option.
  • Data Entry Fields: Required markers for placeholders now appear on the same line as input control for small display widths (Jay H.).
  • Data entry fields no longer have extra line space between them in small display widths (Jay H.).
  • Address auto-complete and validation no longer fails when a pre-existing address is in the form (Jay H.).
  • No longer tries to validate empty phone numbers (Jay H.).
  • “Add another” for repeating form entries is now working properly on all browsers.
  • Ill-formed include_url blocks no longer reload this tree, causing a propagation of buttons.
  • “Sorry, but you don’t belong to organization…” endless login loop message no longer when organization no longer accessible.
  • Clicking tree search results didn’t always change the page.
  • Clicking search results should now always change the page.
  • IPV6 addresses now work for getting location data (Raj).
  • Changing email address in login info now goes to proper logout page.
  • Copying or moving trees to new organizations also copies webhooks. (Raj)

Credits

Thanks to all of our customers who contacted us with great suggestions and astute observations.

If you have a suggestion for us or see something that you think could be done better – please let us know!

Push Live: A Simple Decision Tree Publishing and Approval Process

Some of our larger customers have asked for a simple process for managing changes to their decision trees. When there are multiple people involved in making edits, and the final versions need approval, the Zingtree Push Live tool makes this procedure a breeze.

Push Live lets you have two versions of a tree – a development version and a live version. Your team makes changes to the development version, and when these changes are ready to go live, an administrator approves these changes by invoking the Push Live tool to update the live version of the tree.

Using Push Live is optional, and can be implemented at any time.

Overview

Here’s how Push Live organizes the publishing process:

  1. An author or authors make changes to a tree.
  2. Once the new tree is approved for release, an adminmistrator invokes a Push Live so that the new tree is available to end-users and agents.
  3. All changes and push events are tracked through the Snapshots tool.

Setup

Here’s how to set up a tree for Push Live:

  1. Select your tree from My Trees.
  2. Go to the Settings tool, click the Push Live tab, and check Enable Push Live.

  3. Make sure to click Update All Settings next.

Managing Live and Development Versions

You can switch between the development and live version of your tree from the main Tree Tools screen. Go to My Trees, and select a tree, or use the All Tools option in the Tools drop-down on every page.

Select Development or Live from the Version selector:


IMPORTANT: Use Live Publishing Links

The live version of a tree has different links than the development version. Make sure you are using the Publishing Links code for the live version of your tree by switching to the live version before using the Publishing Links tool.

The tree ID for the live version of a tree is the same as the development version, except that it adds 000 to the end of the ID. For example: If your tree ID is 123456789, the ID of the live version is 123456789000. So you’ll need to use different publishing links when making the live version of your tree available to others.

Pushing Changes Live

In order to update the live tree, you need to have Administrator rights on that tree.

Once you’re ready to “go live”, invoke the Push Live tool from the main Tools page, or the Tools drop-down. You’ll be asked for update notes on this version, which makes it easy to track what changed.

You can see the history of changes (with the update notes) for each update of the live version using the Snapshots tool (under More Tools).

Using Tree Nodes with Live Versions

If you have several trees under the Push Live process, and you are using tree nodes to link them together, Zingtree will ensure the proper development or live version is linked. When editing in the development version, use tree nodes that reference the development versions for your other trees. When you push live, those tree nodes will go the live versions of the other trees if they exist.

Here are the rules:

  • Tree nodes in the development version go to development versions of other trees.
  • When you push live, tree nodes in the live version go to live versions of those trees.
  • If a live version of a tree node doesn’t yet exist, the development version is used instead.

Give Us Feedback!

Is this Push Live feature useful to you? Do you have any suggestions to make this process work even better for you? Let us know!

Fall/Winter 2017 Updates: New Improvements, Fixes, and More

Lots of small but helpful things have been added to Zingtree since our last updates post.

New Goodies

Everybody loves new features. Think of these items as an early holiday gift.

  • Option to enable Single Sign-on (SSO) for authors.
  • MailChimp App and integration.
  • Add, subtract, multiply and divide variables using a new Math webhook.
  • Added a Script Code option to Settings. Makes it easy to insert JavaScript code into your trees.
  • &keep_vars_on_back=1 parameter. (for Shawn, Raj)
  • New author timeout after inactivity option.
  • Admins can set strong password requirement for invitees.
  • Can upload and play videos via a private Zingtree server. (Customer requests for private videos.)
  • New setting for right-to-left languages for easier editing.
  • Logic/Document nodes now offer a “contains” string operation. (for Austin)
  • New Search and Replace tool. Makes it even easier to edit text in your trees.
  • &merge_vars_not_fixed parameter: Merge variables can now set data entry field defaults. (Pascal)
  • Settings / Themes picker now has an option to place question area on top or bottom.
  • Added Linked tree search to search through all trees and any linked trees via tree nodes. (Nick W.)
  • Added auth_token parameter for webhook authorization – returns X-Auth-Token in Header. (Vivek)
  • Temporary File Upload type – expires in 3 days. (Jim)

Updates to Existing Features

Some of our existing features we have made even more useful with some tweaks.

  • New Text editor. Big Improvement for editing content.
  • Single Sign-on now enabled for viewing session details.
  • Reconfigured Single Sign-on setup interface.
  • Now includes time zone UTC offset in location info variables as zt_tz and zt_tz_encoded. (Raj)
  • Duplicate (Copy) Webhook option (Raj)
  • App manager (Webhooks) now has more details, shows usage and which trees use each app.
  • Uploaded images can now be viewed in the tree. (Karen D.)
  • Added session info button to History in agent view, Zendesk Agent Scripting App. (Katie)
  • Webhooks now get a variable node_id sent by default. (Raj)
  • Added Tree Title: Show option to Publishing Links, Hosted, Advanced Options.
  • Added disable_scroll option to embedded Advanced Options in Publishing Links tool.
  • Create Tree now lets authors choose the tree’s language.
  • Zendesk Agent scripting app now passing zendesk_tags as a variable.
  • Session History stock webhook can now return plaintext data instead of HTML formatted data. (Gabe)
  • Button click variables can now be assigned text.

And Bug Fixes:

Yes, sometimes even we make mistakes or discover edge cases nobody ever thought of! We do our best to fix these as quickly as possible.

  • Ensures pop-ups always appear on top. (DT)
  • API calls with a large amount of data no longer give an error 500. (Jay)
  • Phone number validation now returns invalid if any characters or unusual punctuation is found in the number. (Jay)
  • First button with zero value no longer resets the running total score to zero. (Steve H.)
  • Now properly tracks form data from “back” buttons over logic nodes. (Mari)
  • Going “back” properly refreshes nodes that contain form data variables.
  • Email nodes now stay inside of containing iFrame after a message is sent. (Pinkesh)
  • Going back over logic nodes keeps previous scores intact.
  • Moved resources to new CDN due to them being blocked in China.
  • Tab characters in data entry fields should no longer break webhook or Zapier calls. (Alok)
  • Back button no longer removes form data items from the session. (Raj, others)
  • Doesn’t use Chinese as default language if non-Chinese is used.
  • Instant Preview in Edit Node now shows custom button styles properly.
  • Mobile pop-overs now work properly.
  • Allows special characters in merge variables. (Miguel)
  • Missing scrollbar in Agent portal for IE 11 now shows. (Mark D.)
  • Server auto-scaling tweaks to alleviate morning traffic spike congestion.
  • Transfers account status to new organizations linked to original. (Arnel)
  • Link colors in answer nodes using Default, Classic theme templates now show properly.

Thanks!

A majority of these enhancements were initiated from customer requests.

Got any suggestions for the rest of 2017, or to start 2018? Please share!

Generating Custom Documents Using Document Nodes


We’ve had several requests to create a final, single page document based upon answers to decision tree questions. Zingtree’s Document Nodes makes this powerful document generation capability a reality.

With the help of Document Nodes, you can now complete tasks like:

  • Making custom sales brochures.
  • Building legal agreements.
  • Generating purchase orders.
  • Creating evaluations and assessments.

For a simple example, examine our What Computing Device Do I Need? decision tree from the Zingtree Gallery.

Document Nodes Overview

Document Nodes display the content from one or more answer nodes on a single page, based upon variables and values. Variables can be from one of these sources:

  • Data Entry field values.
  • Scoring variables from button clicks.
  • Scoring variables set from Data Entry field list boxes or radio buttons.
  • Variables introduced from calls to Webhooks.

Here’s how it looks in the Document Node editor:

Note that scoring variables are a running total.  So if you set variable v to 1 in one place, and to 2 in another, the value of v will be 1+2 = 3.

Building a Tree to Generate a Document

To build a decision tree that generates a document based on answers selected, we recommend these steps:

  1. Create your question nodes, and assign variables to your responses.
  2. Create answer nodes for all of the possible snippets of content you’ll want to show in the final document.
  3. Create a document node.

Set Up: How to Create a Document Node

Here’s how to create a fully-functional Document Node, step-by-step:

  1. From Overview, click Add Node.
  2. Select New Document Node.
  3. Add the pieces of content you want to serve to your end-users.

Each piece of content is set up like the image shown below. In this example, if the variable phone_calls equals “Yes”, we add the contents of node #6 to the final document.

Using the Document Node Editor

Drag this to reorder the content:

Click this to delete the content from the document node:

Pick a variable to test:

Pick an operation:

Pick a value to test against:

Edit the contents of the included node:

Show the contents of the included node:

Try the Document Node editor with a demo page here.

Hint: Once the content from an answer node is inserted, it won’t be inserted again.

Debugging Tip

Use a node that shows your variables while you are testing. The What Computing Devices do I Need example tree uses Node #10 as an ending piece in the Document Node so you can see the value of all of your variables.

Live Example

The What Computing Devices do I Need tree demonstrates a simple tree with a Document Node at the end.  This tree helps an end-user decide whether they need a phone, tablet or desktop PC, based on the answers to some questions.

Have any questions, comments, or suggestions on this feature? Talk to us on live chat or by email!

This article was originally published on November 29, 2016. 

How to Use Process Flows to Build Mailchimp Lists

As end-users are using your Zingtree decision trees, you can add any information collected during the session into a MailChimp mailing list. Zingtree has a handy MailChimp App for just this purpose.

Here’s how to add data from Zingtree to a MailChimp list.

  1. In Zingtree, go to Account, My Apps, and click add Add MailChimp. The MailChimp configuration screen appears:

  2. Enter a name for this App. For example: “Add to Mailing List”.
  3. Enter the MailChimp API Key. To find your API Key, log into MailChimp, and select Account, Extra, API Keys. Generate an API key if you haven’t done so already.
  4. Enter your MailChimp List ID into the configuration. In MailChimp, click Lists, then select Settings from the drop-down next to your list. The List ID will be at the bottom of the page.
  5. Click Add MailChimp App when finished.
  6. Edit the node where you want to add to a MailChimp list. Look under Show Advanced Options, Send Message To App. Pick the name of the app you just created: “MailChimp: Add to Mailing List”.

  7. Important: The field names you are using in Zingtree must match the merge tag names in MailChimp. So if you have merge tags NAME and ADDRESS in MailChimp, you would use variables named NAME and ADDRESS in Zingtree. You can find the merge tags for each field in MailChimp from List, Settings under List fields and *|MERGE|* tags. They will appear like this:

  8. In Zingtree, the email address of the end user should be a variable named either EMAIL or email.

Once the end-user reaches the node you built in step 6, MailChimp will receive the information collected by Zingtree and add all matching fields to the list for email.

Do you have a cool application for this feature? Let us know on our Feedback page.

How to Do Math Operations in Decision Trees

If you’re using Data Entry Fields or Merge Variables to bring data into your decision tree session, you may want to perform basic math operations on these variables. Zingtree offers a stock webhook option that lets you assign a new variable to the results of an addition, subtraction, multiplication or division operation. Here’s how to set it up:

  1. Edit the node where you want the new variable (the result of the math operation) to be calculated.
  2. Click on Show Advanced Options.
  3. At Send message to app, choose Webhook: Zingtree Math.

  4. In the Message, you’ll need to provide the operation, the two variables or values to calculate, and a variable name for the result. In the example above, we’re assigning a variable named result to the sum of variables a and b. Variables must be enclosed in # characters.

Example Calculations

Here are some message examples:

&op=plus&a=5&b=3&result=c
Sets variable c to 5+3

&op=minus&a=#gross#&b=#expenses#&result=net
Sets variable net to the difference of variables gross and expenses.

&op=times&a=#weeks#&b=7&result=days
Sets variable days = weeks * 7.

&op=div&a=#days#&b=7&result=weeks
Sets variable weeks = days / 7.

 

Operations Reference

You can use the following in the op= parameter:

  • plus
  • minus
  • times
  • div

Demo

The Zingtree Demo gallery has an example. You can try it and examine it.

View Demo

Zendesk Agent Scripting App – Version 10.1

If you’re a Zendesk user in a Contact Center environment,  you’ll want to be using our Zendesk Agent Scripting app.  This makes it easy to guide, train and onboard agents and is a huge productivity booster for everyone.

The Agent Scripting app appears as a button in the right-hand panel:

Click Open Script, and you’ll see your decision tree in a pop-over like this:

If another agent picks up the ticket, they return to the last viewed node, and can see each step taken previously by opening the History:

 

Benefits of the Zendesk Agent Scripting App

  • Standardization: Show a guided path for each ticket, so that Agents follow the proper operating policies or troubleshooting procedures.
  • Pause and Resume: If a ticket is transferred, the supervisor or new agent is taken to the last place in the script, and can see the history of the previous steps taken.
  • Automatic Script Selection: The Agent Scripting App can choose a script based on the Zendesk brand, Zendesk ticket tags, or the value of a custom field.
  • Agent Feedback: Agents can send feedback directly to the authors of the decision trees with a single button click. Feedback is delivered to each author’s email, and includes the tree ID and node number where the feedback was sent from.
  • Zendesk Ticket Data in your Scripts: Values in any custom field, as well as Zendesk ticket tags and user tags, are transferred into your script so you can echo them, or use these variables to branch via Logic Nodes.
  • Automatic Ticket Updating: Tags and custom fields in the ticket can be updated from actions in the script – either via buttons clicked in the script, or from data entry collected.

New Features in Version 10

If  you’re using a previous version of the Zendesk Agent Scripting app, you may want to upgrade to take advantages of these new benefits:

  • Pop-overs: Scripts now appear as pop-overs, rather than being constrained to the right-hand panel.
  • Ticket Updating: Your tickets can automatically update by navigating the script, or by entering data into Zingtree Data Entry Fields. For example, the start of your script could offer the agent a choice of a product, and the “product” field in your ticket will be automatically selected when the agent makes a choice.

Note: Don’t remove the current version of Agent Scripting until you are ready to make the switch. Versions 9 and earlier may not be updated going forward.

Demo Video

This two minute video shows you how Agents interact with the Agent Scripting App:

 

Getting Started

Here are the basic steps to get up and running:

  1. Build an interactive decision tree script with Zingtree (or use one of our demos to start).
  2. Install the Agent Scripting App (version 10) into Zendesk.
  3. Configure the Agent Scripting app within Zendesk.
  4. If you want to have your decision tree scripts update your  Zendesk tickets, you’ll need to add variables and/or tags to your Zingtree tree to match your Zendesk setup.
  5. If you want to enable automatic script selection, you’ll need to add tags to your trees in Zingtree and configure the Zendesk Agent Scripting app properly.

Installing the Agent Scripting App into Zendesk

Download and configure the Zendesk Agent Scripting App version 10 like so:

  1. Download the Agent Scripting app here.
  2. In Zendesk, click the Admin icon and go to Apps > Manage.

  3. Click Upload Private App.

  4. The Upload App page appears.

  5. Enter “Zingtree Agent Scripting” for the App Name.
  6. For App File, locate the file zingtree-agent-scripting-v10.zip you downloaded in step 1.
  7. Click Upload, then confirm if necessary.

Configuring the App

Once you’ve uploaded the app, click App Configuration to see the configuration screen:

Here’s what each item does:

Tree ID: This is the default tree that appears when agents click “Open Script”.  (You should always have a default tree.)

Hide Integration Setup Info: When you are setting up Agent Scripting for the first time, you may need some information about your Zendesk setup to take advantage of automatically updating ticket fields. An “Integration Setup Info” link appears by default when you first install the app, and ticking this option hides it.

Match Tree Tags to Zendesk Brand: If this option is checked, the subdomain of the selected brand will be matched to a Zingtree tree tag.  Any matching tree or trees will appear.  For example, if the brand subdomain is xyz.zendesk.com, any trees tagged as xyz (using the Zingtree Settings tool) will appear.

Match Tree Tags to Zendesk Ticket Tags: If checked, the values in the Zendesk ticket tags will be matched with your Zingtree tree tags (set via the Zingtree Settings tool) to show one or more matching scripts.

Match Tree Tags to values in a Custom field: If you want to use a custom field value to show matching scripts, enter the Zendesk custom field identifier here. The field name can be found using the Integration Setup Info link that first appears in the sidebar when you install the app.

Zingtree API key: Each organization in Zingtree has an API key, which is used to match scripts. If you’re using one of the tag matching options, this is required. Your API key can be found at zingtree.com under Help, API.

Enabling Automatic Script Selection

Automatic Script Selection works by matching tree tags you set in Zingtree to values in the Brand, Tags, or a custom field in a Zendesk ticket. For example, if a tree is tagged with “astrology”, and the ticket tags include “astrology”, then that tree appears. If several trees match, then they will all appear, and the agent can choose one.

To open a script based upon Brand:

  • Add tags to your trees for each brand you want to match. So if one of your brands is xyz.zendesk.com, use xyz as a tree tag in Zingtree for all the trees you want to show.
  • Make sure Match Tree Tags to Zendesk Brand is checked in the App Configuration.

To open a script based upon Zendesk ticket tags:

  • Add tags to your trees for each tag you want to match. So if one of your ticket tag possibilities is “billing”, use billing as a tree tag in Zingtree for all the trees you want to show.
  • Make sure Match Tree Tags to Zendesk Ticket Tags is checked in the App Configuration.

To open a script based upon a custom field:

  • Add tags to your trees for each possible custom field value you want to match. So if one of your custom field values is “billing”, use billing as a tree tag in Zingtree for all the trees you want to show.
  • Make sure the proper Zendesk field variable name is entered for  Match Tree Tags to values in a Custom Field is checked in the App Configuration.


Adding tags to a tree in Zingtree is done like this:

  1. Select a tree from My Trees.
  2. Go to the Settings tool.
  3. Click the Organize tab.
  4. Enter or select a tag from the Tree Tags field.

     

  5. Click Update Settings.

How to Configure to Update Ticket Fields

As agents navigate through your trees, their use of the decision tree scripts you create can automatically update any custom fields in that ticket. This can be done in two ways:

  • By clicking a button in a script
  • By entering data into Zingtree data entry fields.

The key is to use variable names in your Zingtree that match the ones used in Zendesk.

First of all, determine the names of the variables in Zendesk by clicking the Integration Setup Info link in the Agent Scripting app. You’ll see something like this:

You’ll see the label for the field as it appears in Zendesk’s ticket form, and the Zendesk variable next to it. In the above example, the Product custom field variable is custom_field_22899289. This is a drop-down selector, and the Zendesk values for the field options are astrology and insurance.

For the rest of this example, we’ll use custom_field_22899289 as the custom field variable.

To make a button selection update a custom field, you’ll set it up in your Zingtree as follows:

  1. Go to the Overview tool, and edit the node whose button selections will update the ticket.
  2. Click Edit Buttons (or Add Buttons if you don’t have any buttons defined). The button editor appears:

  3. Make sure Assign Button Click Variable is checked. This makes the other options appear.
  4. For the Button Click Variable, enter your custom field variable from Zendesk (custom_field_22899289 in the example).
  5. For each button option, enter the value of the variable under Score/Value. If this is a drop-down list in your Zendesk ticket, you’ll need to make sure the Score/Value entered matches one of the drop-down option values as shown in the Integration Setup Info.
  6. Click Save Changes when you’re done configuring buttons.

Bonus: Adding Tags via button clicks:

Button clicks can also add tags to a ticket. In the above example, clicking Something Else adds the tag other_tag to the ticket. Just include the tag name with two colons after the button text. So entering a button like Something Else::other_tag will add the tag other_tag to the ticket if this is clicked, but agents will only see Something Else as an option.

Using Zingtree Data Entry Fields to Update Tickets

Just like the above example, you can also use Zingtree for data entry, and have that data automatically transferred to your ticket. The key is to use the same variable name in Zingtree as you used in Zendesk. The Integration Setup Info link in the sidebar will give you those Zendesk variable names.

Example: If you have a text entry field in Zingtree you want to update into the Zendesk field custom_field_1234, you would set up the variable name as follows:

 

Try It with Example Data

You can use trees from the Zingtree Gallery to see how the Agent Scripting app works.

For a single tree, enter ’14’ as the Tree ID. This will show an Astrology website troubleshooter example.

For multiple trees, see how a tree can be selected by tag by doing the following:

  1. Enter 6a103737e44e4aa6e1e4b6b0bcb46f83 as the API key.
  2. Make sure Match Tree Tags to Zendesk Ticket Tags is checked.
  3. Try entering one or more of these tags into a ticket: “zingtree”, “astrology”, “pet_rock”.

Any questions? We’re always here to help