4 Reasons Why Marketing & Sales Need to Adopt Decision Trees

You’ll often hear us talk about how decision trees can save contact centers and support managers valuable time and expended energy, but did you know that this interactive toolkit can also benefit those in the marketing and sales world? With a simple question-and-answer flow, it becomes much easier for marketers and sales staff to boost their own productivity and efficiency, collect business-driving information and much more.

Here are just a few of the ways that building decision trees can boost your game.

1. Streamline Lead Qualification

Every B2B marketer and sales staff is well-versed in the importance of lead generation and qualification for the continued health of a business – without new interest being cultivated, a company simply cannot grow.

Placing these leads into a robust decision tree based on key classifiers for your ideal customer ensures that the most qualified leads are quickly delivered to the right person, for faster and more accurate follow-up. Including the types of content, communications and promotions to best serve to these potential new consumers, along with the correct flow of distribution for proper sales resources, is a great way to enhance the lead qualification process overall.

2. Build & Optimize Sales Funnels

It’s incredibly important, in any business or industry vertical, to focus on the customer’s complete path to purchase; the sales funnel is, in essence, a decision tree looked at in a slightly altered way. By designing your initial sales funnel (or any other process) in Zingtree prior to consumer use, you’ll quickly be able to spot and measure any inconsistencies or trouble areas through simple user testing. If your business or organization is struggling with their current sales funnel flow, creating and testing decision trees can vastly excel the improvement process.

3. Improve Procedural Standards

Following and improving corporate procedures, including procurement processes (acquiring or purchasing products/services from an external source), are another factor that should not be overlooked. By using decision trees to build internal codifying systems, getting employees to follow corporate procedures, and continually optimizing these processes, any company can effectively boost these procedural standards.

4. Narrow Down Designs

Marketers are always serious when design is involved; after all, how something looks is directly related to how a consumer perceives a product or service offering! Companies that use decision trees as part of a decision-making process can easily generate a Zingtree based on potential design (or copy) options to gather direct feedback on team preferences. Rather than communicating in longer form, a decision tree is ideal for collecting quantitative data to drive faster decisions.


 

Ready to get started? Sign up for a free trial or contact us to see how Zingtree can help improve your sales and marketing efforts.

This article was originally published on May 11, 2016, and has been updated for relevancy.

5 Reasons Why Shoppers Might Hate Navigating Your Website

navigating website

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

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

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

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

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

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

2. You have poor search functionality

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

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

3. You haven’t optimized your site for mobile

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

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

Image via UserZoom

4. Your design leaves something to be desired

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

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

5. You don’t have an FAQ

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

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

 

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

Create Freshdesk Tickets from Zingtree Decision Trees

Does your company use Freshdesk to manage technical support?

If so, you can use Zingtree decision trees to reduce your technical support team’s workload. Customers can either self-solve their issue, or you can get a new ticket in your Freshdesk that includes all the information from their decision tree session. By effortlessly gathering background information from the customer via the decision tree, you save a lot of time by reducing back-and-forth messages.

Here’s how a ticket generated by Zingtree appears in Freshdesk:

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

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

Setup Overview

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

  1. Add a new Application to Zingtree for creating Freshdesk Tickets.
  2. Create a “Ticket Submitted” node.
  3. Create a “New Ticket” node to obtain the customer’s name, email, a ticket subject, a description, and optional custom fields.

Add a new Application to Zingtree for creating Freshdesk Tickets.

A Zingtree application can be called from any node. You’ll need to add the Freshdesk App first as follows:

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

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

Create a “Ticket Submitted” Node

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

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

  7. Click Save Changes to save this node.

Now we’re ready to link a ticket entry page to this “Ticket Submitted” node.

Create a “New Ticket” node

After your customer goes through the troubleshooting session, if they haven’t been able to resolve the issue, you can direct them to a node which collects the following info:

  • Name
  • Email
  • Subject for the Ticket
  • Description of the problem.

You use Zingtree’s Data Entry Fields to get this info. The field variables need to be named as follows:

name = fd_name
email = fd_email
subject = fd_subject
description = fd_description

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

  4. You can also optionally add Custom Fields into the ticket. In the above example, we have a custom field named product in our Freshdesk installation. So the Zingtree equivalent is fd_cf_product.
  5. If you want to set the status and priority, you can also get variables named fd_status and fd_priority. This is optional.
  6. Click the Action Buttons tab, and add a “Submit” button to go to your submit ticket page.
  7. Save the changes to this node.

Summary

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

That’s how easy it is to create Freshdesk Tickets from Zingtree. Any questions, comments or suggestions for improvement? Talk to us!

How Connected Are Customer Satisfaction and FCR?

customer satisfaction and FCR

Did you know that, for every 1% improvement in first call resolution rate, contact centers will see a 1% improvement in customer satisfaction rates and a 1-5% improvement in employee satisfaction?

The opinion that your customers hold of your company, its employees, and its goods and services, has a direct and profound impact on the long-term health of your business. Simply put, if your customers aren’t happy, you need to make some drastic changes before it digs your company into a hole you can’t get back out of.

Customer Satisfaction also plays a huge role in how many other customer service metrics are measured; this includes First Contact Resolution (FCR), the percentage of reported issues or support tickets that are resolved on the very first interaction with the customer. However, it’s important to have an understanding of the connection between the two metrics in order to effectively track and improve over time.

In a recent article from ICMI, the author discusses how FCR is measured, why it’s so critical, and how customer satisfaction is a key driver in promoting a better FCR. With this information under your belt and the right tools to help you tackle it all, you can more actively take the steps you need to start tracking and improving these important metrics. Here’s just a segment of the article:

For a contact center, FCR is the percentage of contacts that are resolved on the first interaction with the customer. For live calls or web chats, this means that the customer’s issue is resolved before they hang up the phone or end the chat session. Calls or chats that require a customer callback or are escalated to another source of support do not qualify for first contact resolution. For emails and web submitted tickets, which now account for a significant percentage of all customer contacts, the de facto standard emerging in the industry is that resolution within one business hour of receiving a customer email or web ticket counts as FCR.

FCR is typically measured in one of two ways:

1. The agent checks a box on the trouble ticket at the conclusion of the call or chat session to indicate if the interaction was successfully concluded on the initial contact.

2. Customers are asked in follow-up customer satisfaction surveys whether their call or chat was resolved and concluded on the initial contact with the service desk.

The first method requires periodic audits to ensure that agents are accurately reporting FCR on the tickets they handle. This is done by reviewing a representative sample of tickets each month to determine if the tickets designated FCR by an agent are, in fact, being resolved on the first contact with the customer. Neither method of measuring FCR is perfect, but it is one of the most important KPIs to track and trend.

Why It’s Important

A high FCR is almost always associated with high levels of customer satisfaction. FCR is a measure of how effectively your contact center conducts its business and is a function of many factors, including the complexity and types of transactions handled, the experience of your agents, the quality of agent training, and tools such as knowledge management and remote control. The metric is most often measured monthly because a monthly timeframe is long enough to provide statistical significance. But it can also be measured annually, weekly, daily, or even hourly.

The figure below shows the relationship between FCR and customer satisfaction for a representative cross-section of service desks worldwide. This strong cause-and-effect relationship should come as no surprise. As stated above, we all want closure on the first contact with our service providers!

customer satisfaction and FCR

Key Drivers of FCR

As shown above, FCR is a key driver—in fact, the most important driver—of customer satisfaction. But what drives FCR?  If a contact center wants to improve FCR, how would they go about doing it?  If we go back to our cause-and-effect diagram for service desk KPIs, we can see that agent training hours are the biggest driver of FCR.

customer satisfaction and FCR

 

Read more about the link between customer satisfaction and first contact resolution on the ICMI blog here >> 

Here at Zingtree, one of our primary areas of focus is to provide a platform where customers can help themselves with self-service support, helping to improve first contact resolution and, ultimately, customer satisfaction. Additionally, with standardized and perfected agent scripts in place, agents and representatives can quickly match customers to the right solution through an interactive guide, making it much more simple to improve these key metrics over time.

For more on using decision trees to improve call centers:

How to Reduce Agent Turnover in Call Centers

Is Your Customer Service Working? How to Audit & Improve Your Strategy

These 5 Simple Call Script Techniques Can Easily Win New Customers

Can Agent Scripting Improve Your Call Center KPIs?

 

Want to hear more about how interactive decision trees and call scripts help improve FCR and customer satisfaction every day? Get in touch with our team, and check out our example decision trees for call centers and support teams

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

This article was originally published on June 15, 2018, and has been updated for accuracy. 

Sending and Receiving Data from Decision Trees with Webhooks

Our larger corporate clients have asked us for a way to be able to exchange Zingtree data with other applications. Some customers want to send data from a Zingtree session to another application or include data from another application in Zingtree.

Zingtree’s data exchange feature makes use of Webhooks with JSON formatted data. In fact, a lot of the tools we utilize work the same way.

Here’s an Example

To demonstrate how to send and receive data from your decision trees, we will walk through how to build a simple tree that asks for a USA zip code, and then shows the city and state for that zip code inside the tree.

Try this demo tree in the Zingtree Gallery here.

We will send data to a custom webhook we built, which takes a parameter of a zip code. It returns a JSON structure with the city and state info.  Here’s an example of the webhook in use:

http://zingtree.com/apps/webhook/filters/zippopotamus.php?zip=94960

If you click the link above, you’ll see these results:

{"zip":"94960","state":"California","state_abbreviation":"CA","city":"San Anselmo"}

The PHP source code for the webhook URL is here.

The variables #city#, #state# and #state_abbreviation# will now be usable by Zingtree. So to show the city, just enter #city# into the content area of any node.

Webhooks Process

Here’s a summary of how this works:

  1. Add the webhook to your organization’s apps.
  2. Include a call to the webhook in a node. When the node is visited, the call is executed.
  3. Any JSON variables returned by the call become Zingtree variables.

Adding the Webhook:

  1. Go to Account > My Apps.
  2. Click the Webhook button under My Apps.
  3. Enter a name for the webhook, and the URL as shown:The URL is:
     http://zingtree.com/apps/webhook/filters/zippopotamus.php?zip=#zip#

    #zip# will receive the zip code variable entered by the end-user.

  4. Click Add Webhook. This makes the hook available to your trees.

Calling the Webhook when a node is visited:

  1. Go to Overview, and edit the node you want to trigger the webhook call.
  2. Under Send Message To, select Webhook: Zip Lookup.

Universal Parameters

Every call to the webhook URL you provide always includes the following parameters:

  • node_id
  • session_id

Adding Security/Authorization

You can add an extra layer of security to your webhooks by passing an authorization token into the URL that launches your tree. The token is passed back to the webhook URL in the HTTP header.

To send the authorization token MYTOKEN, add this to the URL that launches the tree:

&auth_token=MYTOKEN

To check the token in your webhook, look at the X-Auth-Token value in the HTTP header.

Please note: The auth_token remains the same for the entire tree session.

Credits

The demo uses the free zippopotam.us postal code lookup service.


Any questions? We’re here to help – please reach out at any time via the feedback page or the orange chat window at the bottom right of our homepage.

This article was originally published on April 28, 2016, and has been updated for accuracy. 

8 Stats That Prove You Need A Knowledge Management System

Knowledge Management System

A knowledge base – also called a knowledge management system (KMS) – is the repository of information that customers and/or staff need to use your product or service, from basics to getting the most out of your product. The content comes from the subject matter experts (usually the creators and top support staff), and is expanded and improved over time.

Employees, especially new employees, will use the KMS to familiarize themselves with the product, and customers will often use the knowledge base themselves rather than call in for support. It takes an investment of time and money to create a proper knowledge base, but you will absolutely get more out of it than you put in, especially if it is interactive. Here’s why:

1) 40% of Customer Interactions Are Now Only On the Web

Customers today are calling customer service on the phone less and less than they used to. A recent survey of CRM managers and professionals by DestinationCRM found that 40% of customer interactions were over the internet, including mobile web and apps. Of those companies, 45% reported “measurable reductions” in phone inquiries. That means less time that employers have to pay support staff to answer the phone, and more of the time they do spend is on more advanced programs; this also leads to less employee burnout.

2) Solve Customer Issues For Just $0.25

I just mentioned that fewer customers will call in and require a live agent. Here is a more clear breakdown of those costs. A 2010 study by Forrester research on the benefits of click-to-call and click-to-chat showed that chats can cost a company up to $5 per customer interaction, and phone calls can cost as much as twice that. Automation brings that down even further, because rather than paying for staff to help, once the base is up and running, you’re essentially paying for the cost of running the server. One KMS provider, Hubspot, estimates that cost is a meager 25 cents per interaction.

3) 47% of Companies That Have a KMS Report Increased Sales

According to the same DestinationCRM survey, 47% of those surveyed reported an increase in sales through self-service and 54% reported an increase in web traffic, compared to before deploying a knowledge base. This is in part because a knowledge base answers many technical support questions before the buyer even makes a purchase. Your customer is more informed and more confident, which brings down purchasing resistance. In other words, once you set it up, the KMS is working for you!

4) Save $1,000 by Keeping Employees Happy

Onboarding a new employee is expensive. In order to train the new employee, existing staff have to take time from their tasks and spend it with the newbie, so youre paying twice over. According to a 2014 study by Training Mag, the training expenditure per learner for a small or midsize business was in the range of $819-$1,238; lets round that to $1,000. Thats $1,000 per employee, and if theres a high rate of churn, its money down the drain. By having a knowledge base, it empowers the new employee to learn at his or her own rate without having to interrupt the trainer for every small question, and can even brush up at home.

5) Every 1% Improvement in FCR Means 1% Higher Customer Satisfaction

The best way to reduce the cost of a new employee is to keep the ones you already have happy. According to 3CLogic, for every 1% improvement in first call resolution rate, contact centers will see a 1% improvement in customer satisfaction rates and a 1-5% improvement in employee satisfaction. Repetition is also a reason for burnout, and with a proper KMS, they will see lower zero level solution calls in the first place. The KMS also is an opportunity for collaboration between team members that can foster connections within a company.  

6) Your Existing Customers Will Help You For Zero Dollars

A knowledge base is written by your team members, but as customers ask questions, and, if you let them, answer them, it becomes a become a curated but crowd-sourced source of information. Its possible that customers will even figure out solutions that you havent, and you can add those great ideas to your own training. In addition, your customers are your real-time bug detectors and product developers. They may find a mistake or oversight that you didnt, and your KMS is the first place theyll look to figure out the problem. Similarly, if theyre looking for how to do something your product or service doesnt do, thats an instant suggestion box.  

7) 78% of Millennial Customers May Not Give You A “Second” Chance

Here is some bad news: According to a Salesforce study, although 89% of millennials use a search engine to find customer service, 78% of millennial customers have moved their business somewhere else after one single poor customer service experience. The importance of first-call resolution is higher than ever. Your best bet for keeping younger customers is to let them help themselves with a knowledge management system. It isnt just millennials, 40% of customers, according to Forbes, would rather skip human contact altogether in favor of self-service.

8) 5% Growth in Retention Can Increase Profits by 95%

According to a study by Bain and Company, having only a 5% growth in retention can increase profits by 25-95%. This is because compared to the cost and effort required to get a customers first purchase, many companies dont even break on that first one. It often can take several purchases for the retailer to be ahead. In their example, a customer who purchased from an online apparel retailer once was likely to refer three friends, but a customer who made seven purchases was likely to recommend the store to ten friends. In other words, customer loyalty is tough to earn, but if you are able to satisfy the customers, you will see significant growth over time.

The Final Word

Building a proper knowledge base requires time and effort. It will be continually updated with new information as your customers use your product and you, in turn, improve it. Thats why its called an investment. We at GetVoIP are always in favor of spending the necessary capital expenditure for long-term lower operational spending. A knowledge base will save your employees time and help retain customers, which in turn will both keep and put more money in your pocket. That is the very definition of a worthy investment.


About the Author:

Reuben Yonatan is the CEO @ GetVoIP, a leading VoIP systems comparison guide that connects shoppers with relevant providers.

 

Zingtree Updates: September 2018 – Labor of Love

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

See all of our improvements since June 2018 below:

New Features

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

Updates and Minor Improvements

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

Fixes

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

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

Service Issue – September 2-3, 2018

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

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

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

Thanks for your patience, and continued support of Zingtree.

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