# Zendesk Channel Integration

## The Zendesk channel integration in Ebbot <a href="#introduction" id="introduction"></a>

Ebbot offers a seamless integration with Zendesk, allowing businesses to enhance their customer support capabilities. Through this integration, AI agents in Ebbot handle initial customer inquiries, gather essential details such as name or email, and automatically escalate chats to human agents in Zendesk when required.&#x20;

Note: the channel integrations are only available in the Chat platform.

### Sunshine API / channel <a href="#sunshine-api-channel" id="sunshine-api-channel"></a>

This integration leverages Zendesk’s Sunshine Conversations platform, enabling real‐time messaging through Ebbot’s web widget. Sunshine differs from legacy Chat/Tickets in that it provides a more flexible conversation model, integrates multiple channels seamlessly, and stores richer context about the conversation.

### Requirements and setup <a href="#requirements-and-setup" id="requirements-and-setup"></a>

• **Zendesk subscription:** Ensure you either have access to Zendesk Suite Professional (or higher) with Sunshine Conversations enabled, or any Zendesk Suite with the Sunshine Conversations API add-on.

• **API credentials:** You will need a Zendesk subdomain, API key, and app credentials (App ID, Key ID, Secret) to connect Ebbot to Zendesk.

• **Ebbot configuration:** The integration can be found in the side panel of the Ebbot platform, navigate to **Settings** → **Channels** → **Agent** → **Zendesk** to set it up.

#### Setting customer information (email, phone) <a href="#setting-customer-information-email-phone" id="setting-customer-information-email-phone"></a>

During the chat agent conversation, the Ebbot chat agent can prompt users for information such as email addresses or phone numbers. This data can be passed along with the conversation to Zendesk, allowing your human agents to see key customer details in the ticket. Make sure you configure these fields in Ebbot so they sync correctly with Zendesk’s requester details.

#### Statuses and custom statuses <a href="#statuses-and-custom-statuses" id="statuses-and-custom-statuses"></a>

Zendesk provides default statuses (e.g., “New,” “Open,” “Pending,” “On-hold,” “Solved”) and may also allow custom statuses based on your configuration. These options appear in Ebbot’s “On chat close” dropdown. Selecting a status here means:

• If a chat ends in Ebbot, Zendesk is automatically updated with the chosen status.

• If an agent marks a ticket with the chosen status in Zendesk (for instance, “Solved”), Ebbot also closes the chat for the user.

• If “Send message” is selected (the default), Ebbot does not change the Zendesk ticket status when the user ends the chat; instead, it sends a customizable closing message to inform the user the chat has ended.

#### Group ID <a href="#group-id" id="group-id"></a>

If your Zendesk setup uses multiple groups, you can specify a Group ID for incoming chats. This ensures that tickets generated from Ebbot go directly to the appropriate support team or department. Define the correct Group ID in the Ebbot integration settings based on your Zendesk environment.

#### Handover and Chat history <a href="#handover-and-chat-history" id="handover-and-chat-history"></a>

Once a user requests to speak to a human agent (or the chatbot determines an agent is needed), Ebbot escalates the conversation to Zendesk. Agents will see the chat history directly in Zendesk’s Agent Workspace, maintaining full context for a seamless handover. Any messages sent by the user or chatbot before escalation remain visible in the conversation transcript.

#### Requesters in Zendesk: merge, create, and anonymous users <a href="#requesters-in-zendesk-merge-create-and-anonymous-users" id="requesters-in-zendesk-merge-create-and-anonymous-users"></a>

• **Merge with existing users:** If the chatbot collects an email address matching an existing Zendesk user, Ebbot merges the chat with that user’s profile, ensuring a consistent support history.

• **Create new users:** If the email is not found in Zendesk, a new user record (requester) is created automatically.

• **Anonymous users:** Should the conversation lack an email or identifiable data, Zendesk may show the requester as an anonymous user. Agents can then prompt for identification or merge the requester manually if needed.

## Known limitations <a href="#known-limitations" id="known-limitations"></a>

Here are the known limitations for the Zendesk channel integration in Ebbot chat platform.&#x20;

• **“action\_leave\_queue”-status:** If you have this custom status in Ebbot, it will not function as intended in Zendesk (i.e., the user cannot be immediately removed from the queue).

• **No status applied:** If “Send message” is chosen and the user closes the chat, Zendesk’s ticket status remains unchanged. The agent must manually solve or update the ticket.

• **Lack of contact data:** Without a valid email or phone, merging conversations with existing user records is not possible—Zendesk treats them as separate or anonymous requesters.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.ebbot.ai/ebbot-docs/integrations/chat-integrations/channel-integrations/zendesk-channel-integration.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.