Skip to main content
Set up Fin for Zendesk tickets

How to configure and customize Fin to handle Zendesk tickets.

Beth-Ann Sher avatar
Written by Beth-Ann Sher
Updated over a week ago

Setup

Add knowledge

To set Fin up to handle Zendesk tickets, the first thing you need to do is import knowledge. Go to Channels > Zendesk tickets and select Add knowledge.

You can import knowledge by:

  • Syncing your existing Zendesk knowledge base.

  • Syncing any public URL such as your knowledge base or marketing site.

  • Uploading PDFs.

  • Writing or copy/pasting snippets of text directly into Intercom.

Configure answer and hand-off workflow

Next, customize how Fin responds to customers and hands off to your team when it’s unable to resolve a ticket by clicking on Answer and hand-off.

At the end of all paths (except for That helped ), Fin will unassign itself from the ticket and apply the “routed-to-the-team” tag.

You can tailor the experience further by:

  • Creating different branches based on your conditions.

  • Choosing when Fin answers.

  • Having Fin send a message.

  • Providing reply buttons.

  • Collecting data.

  • Collecting the customer reply.

  • Adding internal notes.

  • Adding an AI generated summary of the conversation.

  • Auto-classifying ticket attributes based on what the customer said.

Once you’ve finished tailoring the hand-off to your team, click Save.

Connect to Zendesk API

Next, connect to Zendesk by entering your:

  • Zendesk subdomain,

  • Zendesk email address for the person who's generating the API token, and

  • Your API token.

You can generate a new API token from your Zendesk Admin Center › Apps & Integrations › Zendesk API.

Then select Connect to the Zendesk API. This will only enable Fin for testing without affecting your live environment.

AI Agent identity

After connecting to the Zendesk API, select an identity for the AI agent on Zendesk. Fin will reply as this agent when a ticket is assigned to it in Zendesk. We suggest creating a new agent for it and making it explicit that it's an AI agent, rather than a human.

You can create a new agent from Zendesk Admin Center › People › Team members. You can use your own email address by appending “+fin” to the name (e.g. beth+fin@examply.io). You need to use a real email address because you'll need to verify the email address in Zendesk. Make sure to select “Agent” as the role since this account needs to be able to reply to tickets.

Once you've created a new agent account and verified it, you can select it under “AI Agent identity” in Channels > Zendesk tickets.

Auto assign tickets

By default when you set Fin live, this will create a new trigger in Zendesk that automatically assigns all new tickets to Fin AI Agent (which triggers Fin to reply).

If you want to have more control, you can disable or edit this trigger in the “Auto assign tickets” section. You can also create your own custom triggers in Zendesk that assign tickets to Fin on any condition you choose.

Test Fin

After adding knowledge, connecting to Zendesk, and selecting an identity for AI Agent, you’ll be able to test Fin.

Send an email to the given email address with the subject line “Fin test” to see how Fin responds and ensure hand-offs to your team are working as expected.

Turn Fin on

Now you’re ready to set Fin live for your customers. Go to Channels > Zendesk tickets and select Turn Fin on.


Customer experience

When a customer sends an email or submits a form, this creates a ticket in Zendesk. Using Zendesk Triggers, you have full control over which tickets are automatically assigned to Fin.

For any conversation that gets assigned to Fin, it'll apply the fin-involved tag.

If Fin has relevant knowledge available to answer, Fin will respond and cite the sources it used, mark the ticket as solved, and apply the following tags:

  • fin-resolved: Fin has resolved the ticket (for either a soft or hard resolution).

  • fin-soft-resolution: Fin has resolved the conversation, but the customer hasn't confirmed it.

If the question is ambiguous, Fin will ask clarifying questions and mark the ticket as pending. If the customer doesn't respond in 3 minutes, Fin will pass it to the team.

If Fin can’t find any relevant information in your knowledge to answer the question, it'll hand-off the ticket to the team by unassigning itself and marking the ticket as open.

Customers can ask follow-up questions and Fin will follow the same process.

If the customer says that it helped, the “fin-soft-resolution” tag will be removed and “fin-hard-resolution” applied.

If the customer asks to talk to the team, Fin will unassign itself from the ticket, remove the “fin-resolved” and “fin-soft/hard-resolution” tags and apply the “fin-routed-to-team” tag. Using this tag you can create additional Zendesk Triggers to route the ticket further.


How it works

The integration works by synchronizing Zendesk tickets to Intercom conversations. A ticket gets synced when it's assigned to a specified agent in Zendesk (e.g. Fin AI Agent). You can use Zendesk triggers to automatically assign tickets to Fin based on certain conditions.

By default the only user data attributes that get synced are name and email, but you can enable more attributes to be synced and further personalize the customer experience.

When a ticket is synced to Intercom, a customizable workflow will be triggered which lets Fin respond. Fin's response will get synced back to Zendesk.

Note:

Zendesk API usage

The Zendesk API key provided to Intercom is stored as an encrypted record inside Intercom. This explains how the API token will used when integrating Fin with Zendesk.

During configuration, you must choose an admin or agent for Fin to reply as. This will use the Users API to list Agents and Admins from your Zendesk workspace for you to choose from.

Five new Zendesk Triggers are created using the Zendesk Triggers API:

  1. A “Fin Test” trigger which looks for incoming tickets with “Fin Test” in the subject and triggers Fin to run without you having to activate Fin for all your customers.

  2. An optional “Fin” trigger which assigns incoming Tickets to Fin. This is deactivated on creation, and can be optionally enabled when activating Fin. Alternatively, you can assign tickets to Fin through your existing assignment trigger setup.

  3. A “Conversation updated” trigger – for tickets assigned to Fin, Intercom is notified that a new update has occurred.

  4. A “Resolution” trigger which allows Fin to mark a Ticket as “solved” when it answers the question. Note: This trigger skips filling in any required fields you may have on tickets.

  5. A “failsafe” trigger – in the rare occurrence that Intercom is down, and tickets are not being processed by Fin, this trigger will unassign tickets from Fin after a period of time to allow your support team to handle them.

When running the integration, Intercom uses the API token for the following:

  • When a ticket is assigned to Fin, Intercom is notified of an update to the ticket via a webhook. This uses the Tickets API to synchronize the Zendesk Ticket data into an Intercom Conversation object that Fin can operate on.

    • For new conversations, the end user’s name and the user’s email is synchronized into a User object in Intercom. You can also optionally synchronize specific User Fields to Intercom by choosing these fields in the Fin setup flow.

    • The Ticket’s comments are synchronized into equivalent Conversation Part objects in Intercom. You can also optionally synchronize specific Ticket Fields to Intercom.

  • When new comments or answers are added to the Intercom Conversation by Fin, the Tickets API is used to update the Ticket in Zendesk with Fin’s replies.

  • If an agent replies to a conversation while Fin is active, their comments to the customer are synchronized to the Intercom conversation. The agent name and avatar is also synchronized to Intercom in order to show a correct representation of the conversation within the Intercom workspace.

A request is made to the Zendesk Tickets API for every new update to a Ticket assigned to Fin in Zendesk. This allows the ticket to be mirrored correctly in an Intercom conversation.

Fin will try to update the ticket in Zendesk with a conditional update. This means if another automation in your system (e.g. another Zendesk Trigger) has updated the ticket concurrently, Fin will respect the changes that were made and try to apply it’s own updates after a short delay.

Intercom usage of the API is limited to 50 requests per minute. This represents 50% of Zendesk’s minimum API usage allowance. This limit will soon be configurable by you. Requests over this limit are retried after a delay.


💡Tip

Need more help? Get support from our Community Forum
Find answers and get help from Intercom Support and Community Experts


Did this answer your question?