# Freshdesk

> Connect Freshdesk for the workspace, and each person connects their own key, so each call can update the caller's ticket under their name.

Source: https://app.activelens.ai/help/freshdesk

An admin connects Freshdesk once for the whole workspace, from
**Connected apps → Freshdesk**. After that, each call can update the caller's
ticket — or open a new one — with a summary of the call and the ticket fields
it talked about. Each person then connects their own Freshdesk key, so what
their calls write shows under their name.

## Connect Freshdesk

The connection needs two things from Freshdesk. Sign in to Freshdesk as an
admin, then:

1. **Your domain.** It's the first part of your Freshdesk address: in
   yourcompany.freshdesk.com, it's _yourcompany_. Type it into **Freshdesk
   domain**. If your help desk has its own web address, still use the one
   that ends in .freshdesk.com.
2. **Your API key.** Click your profile picture at the top right and choose
   **Profile settings**. Click **View API key**, complete the quick check,
   then copy the key and paste it into **API key**.

The key works with the access of the person it belongs to: ActiveLens can see
and change only what they can. Use an admin's key here: it reads the account's
fields and tickets for everyone.

Then press **Connect**. ActiveLens checks the key with Freshdesk before
saving it, and **Test** on the same page checks it again at any time. The
**How to connect** button on the page shows these steps with pictures.

## Connect your own key

Freshdesk shows a change under the person whose key made it, in the ticket's
**Activities** too. So each person connects their own key, once. The admin's
connection doesn't do this for them.

You can do it in either of two places:

- **In your side menu:** open **Connected apps → Freshdesk**. If you aren't an
  admin, the page shows only your own connection, none of the workspace's
  settings. An admin finds the same thing under **People's connections**,
  further down the page, with who else has connected.
- **On a call:** the call's Freshdesk ticket action offers **Connect my
  Freshdesk** when it's your call and you haven't connected yet.

Then:

1. Sign in to Freshdesk as yourself. Changes show under whoever the key belongs
   to, so use your own.
2. Click your profile picture, choose **Profile settings**, then **View API
   key**.
3. Copy the key, paste it in, and press **Connect**.

From then on, the notes, replies and field changes from your calls show under
your name. Until you connect, they show under the account the admin connected.
That also happens when your key doesn't have access to a ticket: the action
says so when it does.

## After a call

By default, every phone call of 30 seconds or more gets a **Freshdesk
ticket** action. It works in three steps:

1. **Find the ticket** — the caller's open ticket, found by their phone
   number first, then by numbers said on the call, their name or business,
   and finally the call's topic. When none fits, a new ticket is drafted.
2. **The fields** — values for the ticket fields you chose, such as its type,
   priority or status, from what was said.
3. **Summary note** — a summary of the call, added to the ticket as a private
   note, as a reply the caller receives, or both, each with its own text.

What happens next depends on the **Mode** on the Freshdesk page:

- **Review first** (the default) — the action waits among the call's
  actions. Someone checks it, changes anything that needs it, and presses
  **Do It Now**. Nothing reaches Freshdesk before that.
- **Automatic** — the ticket is written right after the call. It waits for
  review instead when something is uncertain: when it isn't clear which
  ticket the call is about, or when the ticket was found only by the caller's
  name or the call's topic. You can also hold new tickets, and tickets with
  an empty required field.

Field changes can be undone from the action for 10 minutes after they are
written; a new ticket can't be undone. Sample calls, private calls and calls
in Trash are never written automatically. You can also add **Freshdesk
ticket** yourself from **+** on any call.

**CC** on the Freshdesk page lets the AI CC people on a ticket. Freshdesk
takes CCs only when a ticket is opened, so an update to an existing ticket
adds none.

## Freshdesk settings

The rest of the Freshdesk page sets what the action does: which calls get one
(**When it runs**), how the ticket is found, what a new ticket looks like,
which fields are filled and how, and the summary note. **People's connections**
shows who has connected their own key. Each section shows a live preview of a
sample call, and one **Save** applies them all. These settings are the
workspace's: they're the same for everyone.

## Caller lookup

After a call, ActiveLens looks the caller up in Freshdesk by their number, or by
a meeting attendee's email. What it finds shows on the left of the call page, with
a link to open it, and it looks again each time that panel opens, so you see the
record as it is now. The desktop app shows the same thing during a call.
Nothing is written to Freshdesk.

It is on by default. To stop it, turn off **Caller lookup** on
**Integrations → Freshdesk**.

## Disconnect Freshdesk

**Disconnect** on the Freshdesk page removes the key, these settings and
everyone's own connection. Tickets already written stay as they are in Freshdesk. The key itself keeps
working until you reset it in Freshdesk, on the same **Profile settings**
page — any other tool that uses it then needs the new key.

## Related

- [Zendesk](/help/zendesk)
- [Connect an integration](/help/connecting-an-integration)
- [Actions on a call](/help/action-items)
