Monthly Archives: December 2017

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!

An Interactive Guide for How to Deal With Angry Customers

The hectic holiday season means a stressful time for customers, business, and support representatives at all levels. While we have our own great tips for how to improve the functionality and flow of support during the holiday season, we thought we’d round up some high-level communications to help navigate some of the trickier situations.

Before the thick of the holidays are upon us, take a quick interactive course on how to deal with some of the most common scenarios where a customer could become upset, angry, or frustrated. Good luck!

 



 

Want to see more amazing user-generated decision trees? Check out the Zingtree Gallery!

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.