Using Web Widget (Classic) to embed customer service in your website – CX Experts

Note: This article applies to accounts using Web Widget (Classic). If you're using the messaging Web Widget, see Creating a messaging Web Widget.

In this article, we’ll introduce you to Web Widget (Classic), Zendesk’s legacy embeddable customer support interface. Web Widget (Classic) allows you to add features from other Zendesk products you're using – Guide, Support, Talk, and Chat – to your website or help center, so that your customers can get immediate help from a single interface, in whatever form they like best. including:

Search help center articles for immediate self-service.
Submit a support request using a contact form.
Request a callback, or view a phone number that they can call instead.
Start a live chat with an agent.

This article includes these sections:

About Web Widget (Classic)

Web Widget (Classic) is a separate web application that you embed in a web page that gives customers access your help center and the agents in your other Zendesk support channels (Support, Talk, and Chat). It can encourage customers to self-serve, whenever possible, by using help center articles. It can also make it easier to get help from an agent by reducing the number of steps required to access a contact form, request a call back, and start a chat.

All of these things can be done from a single interface. The customer doesn't need to go from your home page to your help center, open their email application, or search your website to find a email address to contact you.

You can add the Web Widget (Classic) to your website or help center. It appears in the bottom corner by default.

You must be an administrator to set up and manage the Web Widget (Classic).

The first thing you need to do is configure the components you want in the widget (see Configuring the Components in your Web Widget (Classic)), and then you can add the widget code your website or help center (see Adding Web Widget (Classic) to your website or help center).

For a complete list of documentation about the Web Widget (Classic), see Web Widget (Classic) resources.

Browser requirements for Web Widget (Classic)

Web Widget (Classic) is supported on the following browsers.

Device type	Browsers
Desktop computers	Google Chrome: Latest two versions Microsoft Edge Mozilla Firefox: Latest two versions Apple Safari: Latest version
Mobile devices	iOS Safari: Latest two versions Android browser: Latest version Chrome Mobile for Android and iOS: Latest version

Understanding the end user experience

In Web Widget (Classic), you can enable components to combine knowledge base search, live chat, phone calls, and contact forms. The end user experience depends on what options are enabled and whether agents are online.

When multiple components are enabled in the Web Widget (Classic), components are presented to end users in a specific sequence, at different times, rather than all at once.

Components are presented in this order:

For more information about how visitors can use these components, keep reading.

Self service

If the help center is enabled in the Web Widget (Classic), customers are presented with help center search first. When the Web Widget (Classic) opens, it includes both self-service and the contact button.

When you search, up to nine results appear, if matches are found. The customer can click an article in the list and it opens in Web Widget (Classic).

If Contextual Help is enabled in Web Widget (Classic), up to three suggested articles appear below the search box. The suggested articles are determined by the page URL from which the customer accessed the Web Widget (Classic), or it is chosen by the administrator using advanced customizations (see About Contextual Help for the Web Widget (Classic)).

Live chat

This is an overview about how live chat works in Web Widget (Classic) from a visitor’s perspective. It’s meant to give administrators and agents a general idea about how it works, but it doesn’t cover all scenarios—the exact appearance and behavior of live chat in Web Widget (Classic) depends on how it was configured by the administrator.

Visitors to your website can use live chat functions in Web Widget (Classic) from a desktop or mobile browser (see Customizing the Chat widget for mobile devices).

Your visitors can perform these chat-related activities from the Web Widget (Classic):

For more information, see Setting up Zendesk Chat in Web Widget (Classic).

Starting chats from Web Widget (Classic) launcher

When live chat is enabled in Web Widget (Classic), the appearance of the launcher to end users depends on which other contact options are enabled.

Launcher appearance	Contact options and agent availability
	If live chat is the only contact option enabled in Web Widget (Classic) and a Chat agent is online, the launcher includes the Chat icon and says Chat.
	If live chat and the help center are enabled, when a chat agent is online, the launcher includes the Chat icon and says Help.
	The chat badge is a special launcher that allows a customer to get support from a chat agent immediately. If the chat badge is enabled, chat is the only contact option enabled in the Web Widget (Classic), and a Chat agent is online, the chat badge appears on the page instead of the regular Web Widget (Classic) launcher.
	If Chat is the only contact option enabled and no agents are online, the launcher does not display.

Once the customer opens Web Widget (Classic), they see this:

When the customer clicks Live chat, what they see next depends on whether the pre-chat form is enabled.

If the pre-chat form is enabled, the customer fills in the form, then clicks Start Chat

If the pre-chat form is not enabled, the customer can start the chat right away.

If an agent is available when the customer clicks the launcher, but the then agent signs off before the chat begin, the customer sees a message indicating that the Chat agent is not available.

Receiving proactive chats

Agents can see who is the currently on your site and decide whether to proactively contact a visitor before they request a chat. For example, you might want to reach out to visitors who have items their shopping cart, but are taking too long to complete their purchases. For more information, see Browsing your site's visitors, Using Zendesk Chat, and Targeting key visitors with proactive chat.

Viewing conversation history

If visitor authentication is enabled in the Web Widget (Classic), authenticated visitors can see their past chats. For more information about visitor authentication, see Enabling authenticated visitors in the Web Widget (Classic) and Conversation history in Web Widget (Classic) for authenticated visitors.

Customize the avatar, name, and byline of the chat Concierge section

Before visitors connect with a support agent, they see the avatar, name, and byline of the chat Concierge. For more information, see Customizing the Chat widget concierge.

Sending and receiving attachments with chats

Visitors can send and receive attachments. Clicking the attachments icon () opens a standard file selection dialog box, but you can also drag and drop files into the Web Widget too. For more information about attachments, see Managing file sending options.

Adjusting sound, requesting transcripts, editing contact details, and ending chats

Visitors can use the expandable menu at the bottom () to turn sounds on and off, request a transcript of the chat, edit their contact details, or end the chat. For more information about transcripts, see Automatically send chat transcripts with email piping. For more information about editing contact details, see Editing Visitor Profile settings.

Translating chats

If Chat detects that the agent and visitor are using different languages, the Show translated link appears in the conversation. Visitors can click this link to translate the agent’s replies into their language. The translation is performed by Google Translate.

Ending and rating chats

When the visitor is ready, they can end the chat by clicking the end chat () icon. They can also end the chat from the expandable menu ().

Visitors can rate a chat as good or bad using the thumbs up () and thumbs down () icons at any time during the chat. After they rate the chat, the Leave a comment button appears, so they can add a comment, if desired.

If the visitor doesn’t rate the chat after a little while, the agent can prompt the visitor to rate the chat by making the Rate this chat button appear.

For more information about chat ratings, see Measuring visitor satisfaction with chat rating.

Popping out Web Widget (Classic) during chats

WhenChat is enabled in the Web Widget (Classic), visitors can click the pop-out icon () to pop-out the Web Widget (Classic) to it's own browser window.

The Web Widget (Classic) becomes separate from the website and receives a unique URL. It can be moved around and is no longer anchored to the website.

You can share the URL to the Web Widget (Classic) popout in a range of marketing communications, inviting the user to engage directly with you without having to be on your website.

Phone calls

When Talk is enabled in Web Widget (Classic), the appearance of the launcher to end users depends on which other contact options are enabled.

Launcher appearance	Contact options and agent availability
	If Talk is the only contact option enabled in Web Widget (Classic) and an agent is online, the launcher includes the Talk icon and says either Request a callback or Call us, depending on your configuration.
	If Talk and the help center are enabled in Web Widget (Classic), and an agent is online, the button says Help.
	If Talk, the help center, and Chat, or contact forms are enabled in Web Widget (Classic), and agents are online, the launcher includes a question icon and says Help.

When Web Widget (Classic) opens, the exact appearance of Talk in Web Widget (Classic) depends on the how it's configured by the administrator and the status of agents (see Configuring Zendesk Talk settings for Web Widget (Classic)). Depending on your configuration, customers can:

View a phone number that they can call
Request a callback
View the average wait time for a callback

The following examples show how Talk in Web Widget (Classic) might appear, depending on your configuration.


If Talk is the only option enabled in Web Widget (Classic) and it is configured to allow callback requests, and then you click the launcher, the callback form displays.	If Talk is the only contact option enabled and Talk is configured for Call Us only, your phone number displays.
If Talk and the help center are enabled, and other contact options are enabled (for example, Chat or contact form), after a help center search the customer can access Talk from the Contact us button.	If Talk and the help center are enabled, and Chat and contact form are disabled, after a help center search the Contact us button says Request a callback (or Call us) instead.

Contact forms

Your customers can submit a ticket from Web Widget (Classic) to receive an email reply to their inquiry. The contact form is enabled in Web Widget (Classic) by default.

By default, the contact form includes fields for the customer's name, email address, and a description of the problem. If the administrator enabled multiple ticket forms in Web Widget (Classic) (see Configuring the components in your Web Widget (Classic)), then the customer can choose from multiple ticket forms. If not, then only the default contact form appears.

Tickets submitted through Web Widget (Classic) contain the tag web_widget.