Connecting Freshdesk
If your team already uses Freshdesk, you can connect it to your messenger. Teammates can then turn a chat into a Freshdesk ticket in one click, the AI agent can create one at the end of a procedure after the customer confirms, and the inbox lists every Freshdesk ticket made from your conversations, with its status kept up to date.
Freshdesk is separate from Docent's own tickets. If you want to keep tickets in Docent instead, see Setting Up Ticketing.
Connecting your helpdesk
- In Freshdesk, click your profile picture, then Profile settings, and copy Your API key. Tickets are created with that agent's key, so use an agent who can create tickets, such as an admin or a dedicated integration agent.
- In Docent, open your messenger and click Integrations in its sidebar (owners and admins), then the Freshdesk card.
- Enter your helpdesk address (for example
yourcompany.freshdesk.com) and the API key, and click Connect.
Docent checks the key with Freshdesk before saving it. The key is kept encrypted, is never shown again (only its last four characters), and is only ever sent to your Freshdesk address. To use a new key, connect again. Disconnect deletes the key and switches off the actions it added.
Connecting adds a freshdesk_create_ticket action to your messenger's actions. It creates an open ticket tagged docent-chat (priority low unless you set one), and Freshdesk emails the customer as usual. Because it changes something, it only runs from a procedure's Do step after the customer says yes to a Confirm step, never on the AI's own initiative. The Report an issue procedure template is a good place to use it.
Creating a ticket from the inbox
- In a conversation, open the ⋯ menu and choose Create Freshdesk ticket….
- Check the subject and description the AI wrote from the conversation, and edit them if you like. Tick Add the full transcript to append it.
- Check the customer's email (required) and name, the priority, the type and group, and any fields your helpdesk requires agents to fill in.
- Click Create ticket. Tick Close this conversation… first to close the chat at the same time.
Nothing is sent in the chat; Freshdesk emails the customer. A note in the conversation links to the ticket, the details panel shows In Freshdesk #4821, and the menu item becomes View ticket #4821. A conversation can have one Freshdesk ticket. Anyone who works the inbox can create one.
The Freshdesk view
Once Freshdesk is connected, Tickets → Freshdesk appears in the inbox's sidebar. It lists every Freshdesk ticket made from your conversations, whether a teammate or a procedure created it, with:
- the ticket number, subject and customer;
- its status, group and agent, as named in your Freshdesk account;
- when it last changed.
Tabs narrow it to Active (not resolved or closed), each of the Freshdesk statuses in use, or All. Search matches the subject, the customer or the ticket number. Click a row to open its conversation, and use ‹ › to step through the page; click the number to open the ticket in Freshdesk. On a phone, the tickets show as cards.
Keeping statuses up to date
Docent reads ticket statuses from Freshdesk every five minutes, and Refresh in the Freshdesk view reads the tickets on screen straight away. To update them the moment a ticket changes, add an automation rule in Freshdesk that calls Docent:
- In Docent, open Integrations → Freshdesk. Under Ticket status in the inbox, copy the Address and the Body.
- In Freshdesk, open Admin → Workflows → Automations → Ticket updates and click New rule.
- Set it to run when an action is performed by Agent or Requester or System, and the events include Status is changed. Add Group is updated and Agent is updated too, if you like.
- Under actions, choose Trigger webhook: request type POST, the address you copied, encoding JSON, content Advanced, and paste the body.
- Save the rule, then change a ticket's status to check it works.
The Integrations page then says when Freshdesk last called. If it says Freshdesk hasn't called yet, check the rule's conditions and the address.
Keep the address privateAnyone with the webhook address can ask Docent to re-read a ticket, and nothing else. Docent only ever reads tickets made from your own conversations, and reads them from Freshdesk itself, so the address can't be used to change anything.
Checking a ticket's status
- Your team: type
/ticket_statusin the reply box to see this customer's Freshdesk tickets, or/ticket_status 4821to check any ticket by number. The result is a card only your team sees, with Insert in reply to give the customer the status in their words. See Using the Chat Inbox. - Customers: when a customer asks the AI agent about a ticket made from one of their own conversations, it looks up the status and tells them: the status as your helpdesk shows it to customers, the group, and when it was opened and last updated. It never shares the description or notes, and it won't look up a ticket number someone simply types into the chat.