Category Archives: Product Updates

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 ' 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!

Visual Designer Update – What’s New With Our Decision Tree Maker

As a part of our continued efforts to make building decision trees easier and easier, we’ve updated the Zingtree Visual Designer tool to work better than ever.

Here’s what’s new:

  • Question Nodes and Answer Nodes are now a single type: Content Nodes. This makes it easier to add button options to any node with content in it.
  • The pop-up node editor can now edit button assignments, and these are immediately updated in the Designer view.
  • The “Save Layout” function is eliminated, as any changes to the tree are saved automatically.
  • Creating an image of the tree design via the PNG Export option now generates a full-size image, and eliminates unnecessary whitespace at the edges.
  • You can change the Root Node from within Designer (via the pop-up editor).
  • Designer loads 2x faster in most cases.
  • Unlinked buttons appear as red arrows, and the “UNLINKED” node can now be moved and repositioned.
  • Deleting buttons now updates the button order rank of the remaining buttons.
  • New, sharper hi-res icons.

Here’s an example of what you’ll see in the new Designer:

One other thing: We’ve eliminated the Undo and Redo buttons. Since changes to the tree save automatically, any previous versions can be retrieved using the Snapshots tool.

This update was a lot more work than it appears on the surface, as often we find that incremental improvements in the overall tree-building experience take a lot of time to build and test.

We hope you like the update! Please reach out with any questions, observations or suggestions.

 

How to Send Email from Decision Trees

send email from trees

One of the most frequent requests we get from customers is about sending email. We’ve spent a lot of time to make this process as simple as possible.

With Zingtree, you can use Email Nodes to send email in two ways:

  • Automatically, with no end-user interaction.
  • Showing a pre-defined form for the end-user to enter a message.

Emails can include everything you need:

  • The Session transcript.
  • Variables entered during the session.
  • Images and formatted text.
  • Attachments.

Sending  Emails Automatically

Emails can be sent automatically, with no end-user interaction. Start by creating an Email Node as follows:

  1. Click Tools, then Add Node.
  2. Select Email Node as the node type. The Send Method should be set to Send Automatically.
  3. The Email Node editor appears.

  4. Add a Page Title (mostly for your reference when using the Zingtree editing tools)
  5. In Send Email to, enter the delivery email address. You can enter multiple recipient email addresses separated by commas.
  6. Enter a subject and a message. The message can include images, formatted text, or placeholders for variables. For example, if you collect a variable called name, just add #name# into the email body for it to appear.
  7. Check Include Session Data in Email to include the Q&A transcript, and any data collected in the email. You can also check “Securely deliver session data via Link”, which will provide a link to the session information, instead of including it in the email body.
  8. In After Sending, choose a node to go to next. Or, choose Go to URL, and enter a URL to launch instead, like this:
  9. Click Save Changes when finished.

How to Create an Email Form Node

Your end-users can be presented with a stock email form, which looks like this:

You can make a node that displays this form by creating an Email Node as follows:

  1. Click Tools, then Add Node.
  2. Select Email Node as the node type. The Email Node editor appears.

  3. IMPORTANT: For the Send Method, select Show Form Before Sending.
  4. Add a Page Title (mostly for your reference when using the Zingtree editing tools)
  5. Add text for the Send Message button.
  6. In Send Email to, enter the delivery email address. You can enter multiple recipient email addresses separated by commas.
  7. You can enter a default subject or message. These are pre-filled in the email form.
  8. Check Include Session Data in Email to include the Q&A transcript, and any data collected in the email. You can also check “Securely deliver session data via Link”, which will provide a link to the session information, instead of including it in the email body.
  9. In After Sending, choose a node to go to next. Or, choose Go to URL, and enter a URL to launch instead, like this:

  10. Click Save Changes when finished.

Summary

These two methods are the recommended ways to send email, and should be used in place of any other methods.

As always, if you have any ideas to share with us on this or any other features, 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!

 

This article was originally published on January 16, 2018.

Zendesk Agent Scripting App – Version 12

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.

Contents of this Article

Overview: Sidebar and Popover views
Pause and Resume
Benefits of the Zendesk Agent Scripting App
New Features in Version 12
Demo Video
Getting Started
Installing the Agent Scripting App into Zendesk
Configuring the App
Enabling Automatic Script Selection
How to Configure to Update Ticket Fields
Using Zingtree Data Entry Fields to Update Tickets
Using Zingtree’s Zendesk CSS Theme
Try It with Example Data

Version 12 gives you the option to show your script directly in the right-hand panel when viewing a ticket, like this:

 

Or you can use less sidebar space, and make it appear as a button in the right-hand panel:

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

 

Pause and Resume

This happens automatically: If another agent picks up a 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, the agent name, customer info, as well as Zendesk ticket tags and user tags, are transferred into your script so you can display 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 12

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

  • Option to choose between Sidebar and Popover views
  • New customer information data variables sent from Zendesk: requester_name and requester_email
  • New Zendesk Theme to match Zendesk fonts and styling. This gives you a little more real estate for your content, especially in side-panel mode.

If you’re upgrading from version 10, these features are also new:

  • Toggle to share Zendesk data with Zingtree: Some customers don’t want ticket data shared with Zingtree. There’s now an option to disable data sharing.
  • Removed “Flash”: Some customers experienced a “flash” when moving from ticket to ticket in pop-over mode. This is now fixed with this update.

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 12) 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 12 like so:

  1. Download the Agent Scripting app Version 12 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.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.)

Show Tree in Side Panel: Select this option if you want to display the entire tree in the right-hand sidebar when a ticket is open. Uncheck this to use pop-over mode instead.

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.

Display Half-Height: In Popover mode, the popup view will cover half the height of the screen. This has no effect when using Sidebar mode.

Don’t share Zendesk Custom Fields with Zingtree: By default, the app sends custom field data from each Zendesk ticket to Zingtree so you can do more powerful automatic branching via logic nodes, as well as echoing customer information (like their name, for example). If your organization has data privacy concerns, you can check this option to disable data sharing.

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 Resources, API.

Data Sent from Zendesk to Zingtree

Unless you select the Don’t share Zendesk Custom Fields with Zingtree configuration option, Zendesk will send the following variables to your Zingtree decision tree:

  • requester_name – The customer’s full name.
  • requester_email – The email of the customer.
  • zendesk_tags – Any tags in the ticket.
  • agent_tags – Any tags from the agent.
  • agent – The Agent’s full name.
  • agent_first_name – The Agent’s first name.
  • Any custom fields

To display one of these values, just surround the variable name with # characters. So to show the Agent’s first name in your script, enter #agent_first_name# in the content area of any node in your decision tree.

Tip: Add #ALL DATA# to the content area of any node in your own tree to see all the variables sent to your script.

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 on 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 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 Tags tab.
  4. Enter or select a tag from the Tree Tags field.

  5. Click Update All 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:

Using Zingtree’s Zendesk CSS Theme

For the best user experience, we recommend using the Zendesk Apps theme in your trees that display inside of Zendesk. This will give you more room for your content (since the fonts are smaller), and also match the look and feel of the rest of the Zendesk experience.

Here’s how the theme looks in the two style options:

Buttons style:


 

Panels style:


 

 

To include the Zendesk Agent Scripting App theme in your trees, do the following:

  1. In Zingtree, open the Settings tool for your tree.
  2. Click the Display tab.
  3. Choose either Buttons or Panels as the Default Display Style.
  4. Click Pick a Color Theme.
  5. Choose Zendesk Agent Scripting as the theme.
  6. Click Save Theme and Colors.
  7. Click Update Settings.

 

Try It with Example Data

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

This Zendesk Agent Scripting Demo shows how to implement some of the basic integration features. You can install it into your own Zendesk configuration by entering tree ID 350546744 in the App Configuration.

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

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

 

Any questions? We’re always here to help

Zapier Decision Tree Integrations with Zingtree

zingtree zapier integration

Our Zapier app makes it easy to send data collected during each Zingtree session to 1000+ applications supported by Zapier. In case you haven’t heard of it, Zapier is a tool that simplifies data exchange between various web applications. We’re big fans.

Here are some cool things you can do with Zingtree and Zapier:

  • Send data collected in a Zingtree session to Salesforce, Zoho, Highrise, or any other CRM.
  • Add an email address entered into a tree into Mailchimp.
  • Send yourself an email or SMS message when a customer reaches a critical node in a tree.
  • Save new customer information in a Google Sheets row.
  • Create Trello cards from trees, and include customer notes and session data.
  • And tons more!

When using Zapier, you create “Zaps.” A Zap has a “trigger,” which is the source of the data, and an “action,” which is where the data gets sent. Most of our customers want to send data from Zingtree to another app, so we’ll demonstrate how this is done here.

Before starting, you may want to examine a demo tree from our Gallery that gathers data and sends it to Zapier, or copy it to your account.

How to Set up Zapier for Zingtree

The Zingtree Zapier app is currently invite-only. But if you’re reading this article, you’re invited!

  1. Create a free Zapier account at Zapier.com.
  2. Go here to accept an invitation to use the Zingtree app. The invitation appears:

    Accept the invite.
  3. You’ll be prompted to make a new Zap:
    Click Make a new Zap.
  4. You’ll be asked to choose a Trigger App, which is the source of the data exchange.
    Search for Zingtree, and select Zingtree (Beta).
  5. You’ll be asked to choose a single trigger.
    Click Save + Continue.
  6. Next, you’ll need to connect your Zingtree account and a tree to Zapier.
    Click Connect a New Account.
  7. You’ll be asked for your Zingtree API Key, which you can find here. Also, enter the Tree ID that will be sending data to Zapier.
    Click Continue when finished.
  8. Change the name of the account, then click Test.

    You should see “success.” Click Save + Continue.
  9. Next, Zapier will attempt to retrieve any variables or sample data from your tree. If this is a new tree, you may want to run through it once and gather some data.
    Click Fetch & Continue.
  10. You’ll see some of the stock data that Zingtree always provides, as well as any custom data for your tree. Again, if you don’t see all the data you expect, do a test run through your tree, and enter some data at least once. This will make the rest of the process easier.
    Click Continue.

Set up the Action App – Email Example

So now you’re done with the Zingtree part. Congratulations! Next, you need to set up an Action App, which will receive data from Zingtree. Let’s set up email delivery as an action, as follows:

  1. Search for email, and choose Email by Zapier as an action app.
    Select Email by Zapier.
  2. This app has just one action.
    Click Save + Continue.
  3. Fill in details for the outbound email. You can insert fields from Zingtree in the body of the email as well.Click Continue when the email is set up correctly.
  4. You’ll see  a preview of what to expect.
    Click Create & Continue to save the action and send a test email.
  5. You should see another “success” screen.
    Click Finish when the email appears as you like.
  6. Name your Zap Zingtree to Email, and turn it on!

Your Zapier Zap is all set.

Making Zingtree Send Data

The final step is to tell Zingtree when to send all the data collected in a session to Zapier. This can be triggered from one or more nodes, when they are seen by the end-user of your tree.

  1. From Overview, Edit Node, edit the node that you want to trigger sending data to Zapier.
  2. Go to Send Message to, and pick Zapier: Zingtree to Email. This is the new Zap you created.
  3. Click Save.
  4. Now try a test from Zingtree. Using Preview or the Publish tool, navigate your tree, and when you reach the node that triggers the send, you should see something in your inbox. IMPORTANT: Make sure to use https in your published Zingtree URL when using Zapier.

Once you get your first Zap done, it becomes easy and addictive to hook Zingtree to the other applications that your business depends upon. So keep going!

Have any questions? Contact us anytime!

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!

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!