If necessary, it is possible to use one tree for both end-user support and internal agent usage. Rather than maintaining two separate trees, being able to have one source of content and show (or hide) parts between agents and end-users can be extremely helpful. 

Creating Agent-Only or End-User Only Buttons

You can have a button only appear to Agents and not for end-users.  Here’s how this magic is done:

• If you prefix the button label with AGENT_ , only agents will see that button.
• Prefix a button with USER_ to show it to just end-users.
  
  

Creating Nodes with Dual Content

In the content area for any node, you can insert special tags that make the text visible to just agents, or just end-users.

To show content for agents only:

Surround the content with [[AGENT-ONLY]] and [[/AGENT-ONLY]].

To show content for end-users only:

Surround the content with [[USER-ONLY]] and [[/USER-ONLY]].

You can access these template tags from the content editor in any node:

If your node content area looks like this…

This is the content for a node.

[[AGENT-ONLY]]Agent stuff shows here[[/AGENT-ONLY]]

[[USER-ONLY]]User content shows here[[/USER-ONLY]]

An end user will see this…

This is the content for a node.

User content shows here

And your agents will see this…

This is the content for a node.

Agent stuff shows here

Implementation

Your agent-only content will appear in trees accessed via the Zingtree Agent Portal. You can also make this content appear by adding the following parameters to the URL for Zingtree hosted or embedded trees:

&agent_mode=1&apikey=YOUR_API_KEY

Substitute your API key for YOUR_API_KEY in the URL. You can find the API Key from the API page, or if you have multiple organizations go to My Account, Organizations and Billing, and click the API section.