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.
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.
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.
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:
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.
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:
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.
/ticket_status in the reply box to see this customer's Freshdesk tickets, or /ticket_status 4821 to 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.