Multibrand works with the widget and Zendesk Chat. You can customize the Chat widget depending on the brand center it is embedded in, and manage all of the tickets within your primary instance of Zendesk Support. Having one Chat account embedded on multiple different sites for your agents to work out of can help increase efficiency and saves on administrative minutiae.
This article assumes you have Multibrand, Zendesk Chat, and have set up branded Help Centers. If not, I highly recommend you check out our Multibrand setup documentation to get started!
Configuring Zendesk Chat
A Suite or Chat account on at least Professional plan is needed to take advantage of unlimited triggers and departments. Here's a Zendesk Chat setup walkthrough! We are also going to take advantage of the Zendesk Support integration for Zendesk Chatto automatically create tickets when chats end and for offline messages. Configure the departments you would like available for each of your brands and allocate your agents accordingly.
Configure the triggers you'll be using for each brand -- you can key off the page or site URLs & names in your conditions . Would you like to know more ?
Configuring Zendesk Support
A widget with chat enabled for each brand should be created -- this is especially helpful if you'd like to shepherd your users to a Help Center search before leaving a message. It is possible to forego the use of the Zendesk Support widget and just embed the Zendesk Chat widget on your sites, but you will lose some really useful functionality (Help Center searches before chat/ticket submission, brand placement on ticket creation).
Triggers
While requests made via the Web Widget contact form will automatically create the ticket under the appropriate brand, chats do not currently recognize the brands they're installed on. So, we need to tell Zendesk Chat which brand each should be associated with! We do this by keying off the user agent string passed through in each ticket via internal comment.
Since all requests originating from that brand will have the subdomain as part of the URL, our trigger is light weight and automatically routes the chat request to the appropriate brand.
I won't go into the full details of modifying notifications as they differ depending on the needs of the company, but as it stands when tickets are created via chat they will fire off the "Notify Requester of Received Request" default trigger. That notification will appear as coming from the default brand support address. To prevent those notifications from sending out to chat-created tickets, you can add a condition to the "Notify Requester of Received Request" trigger where Channel is not chat . You would then be free to create new triggers where Channel is chat to send follow-up notifications.
Branding the widget
The Web Widget code is embedded in the <head> section of your Help Center (or external page). Any sort of modifications to the web widget itself can be done through the Embeddables API , but the primary modifications needed are through the Chat API .
Here's an example of the same Zendesk Chat instance with widgets branded for different purposes:
In these examples, I have filtered the departments available, changed the concierge avatar image/name, varied the prechat form greeting, and set a new title for the chat window.
You will need to add a code block to the JS tab of your Help Center under the line
$(document).ready(function() {
which initiates the Zendesk Chat APIs and performs your customization changes:
In text form:
zE(function() {
//Zopim API
$zopim( function() {
$zopim.livechat.departments.filter('Haven Hobbies Support', 'Haven Hobbies Sales');
$zopim.livechat.concierge.setTitle('Hierophant Hobbyist');
$zopim.livechat.concierge.setName('Helley Haven');
$zopim.livechat.concierge.setAvatar('Image URL');
$zopim.livechat.window.setTitle("Helley's Haven Hobbies");
$zopim.livechat.prechatForm.setGreetings("Need a new hobby? We've got your hobbies right here!");
$zopim.livechat.theme.reload();
//End Zopim API
});
});
Publish your changes, refresh your Help Center, and the new changes will take effect.
0 Comments
Article is closed for comments.