Skip to content

Support

AI agents that use Freshdesk

UtilitySpaces gives an AI agent scoped access to Freshdesk through its own encrypted connection, not your password. The agent can call 5 named Freshdesk tools, and the 2 that write wait for a person's approval unless an admin has set the connection to run without asking. Every call is written to a hash-chained audit log with its arguments and its result.

What an agent can do in Freshdesk

Read and create support tickets and reply to customers in a Freshdesk helpdesk. An agent calls these by name, and matching is exact.

Every tool a Freshdesk connection exposes, and whether it writes, which waits for approval by default
ToolWhat it doesWaits for approval by default
List ticketsList helpdesk tickets.No — read only
Get ticketGet a single ticket by id.No — read only
List contactsList helpdesk contacts.No — read only
Create ticketOpen a new ticket on behalf of a requester email.Yes — it writes
Reply to ticketSend a reply to the ticket's requester.Yes — it writes

3 read tools, 2 write tools. Generated from the connector catalogue the product runs on, so it cannot list a tool that does not exist.

What teams hand an agent in Freshdesk

Helpdesk teams hand an agent the reading and drafting around tickets: pulling a ticket with Get ticket, matching the requester against List contacts, and writing the first version of an answer. Create ticket and Reply to ticket are the writes, and both stop for approval unless an admin has let this connection run writes without asking.

  • Summarise the open ticket list each morning by listing tickets and grouping them by priority and how long they have waited.
  • Open a ticket on behalf of a requester when a problem is reported in chat rather than by email (after a person approves it)
  • Reply to a ticket with a drafted answer when the fix is documented and the ticket matches it (after a person approves it)
Before you let it write, or keep out: Reply to ticket sends straight to the requester, not to the team: think before letting it run without asking, and have the agent quote the exact ticket id it is answering, so a reply never lands on the wrong thread.

What waits for a person

Reads run on their own. These do not — each one waits in Approvals for an owner or admin unless an admin has set this connection to run writes without asking, and every call toFreshdesk, approved, rejected or unattended, is logged.

  • Create ticket POST
  • Reply to ticket POST

What connecting Freshdesk takes

Freshdesk uses an API key you create in Freshdesk and paste in once. A workspace admin sets the connection up; the fields are:

  • Freshdesk URL
  • API Key

Credentials are encrypted and bound to your workspace, never read back, and every outbound call passes one guarded fetch — the connector security posture sets out exactly how, and the security page covers the platform around it.

Where Freshdesk fits

Give an agent Freshdesk work by writing a message in the inbox, or put its tools in a scheduled flow. What the run cost is on the cost breakdown.

Other support integrations: Intercom, Zendesk. Or see every application agents can connect to.

See it doing your actual work

Open a demo workspace, connect one app, and give an agent a real job. No card, no sales call.

We reply to every message within one business day.

Try the demo