Last updated: 2026-05-13
Freddy AI Agent Studio is a platform within Freshservice that lets you build, deploy, and manage AI agents that answer employee questions, create incidents, and take action to resolve service requests. Instead of one generic assistant, you can deploy a workforce of specialized agents for IT, HR, and other business functions. Agents understand requests in context, access the right data, and take action across workflows and systems.
The following video explains what the platform unlocks, how it works, and the key behaviors to watch out for so you can roll it out with confidence:
Build and deploy AI agents without code
What Freddy AI Agent Studio can be used for
You'll get the most value from this platform when you have a steady volume of repeatable employee conversations that today rely on human agents, forms, or one-size-fits-all chatbots. Common reasons to turn it on:
Plan availability
Freddy AI Agent Studio is rolling out for Growth and Pro plans as a promotional offer until September 30, 2026. For more information, see Freddy AI Agent Studio FAQ.
Key concepts to know before you start
A few terms appear throughout this article and the rest of the Freddy AI Agent Studio documentation. Knowing them upfront makes setup much easier.
| Term | What it means |
| Agent | An AI agent built in Freddy AI Agent Studio that answers employee questions, creates incidents, and takes action to resolve service requests on one or more channels. |
| Pre-built agents | A ready-made agent that ships with the platform. Two are available at launch: the IT Agent and the HR Agent, each with pre-built agentic workflows. |
| Agentic workflow | A defined sequence of steps that an agent runs to complete an action. For example, resetting a password, approving software access, or updating PTO. 20 pre-built workflows are included at launch. |
| Knowledge source | Content the agent uses to ground its responses: files, URLs, the knowledge base, the service catalog, and external connectors such as SharePoint, Google Drive, and Confluence. |
| Channel | Where the agent is deployed: the Support Portal (web widget), MS Teams, or Slack. |
| Session | Any 24-hour period of conversation between a unique user and the agent. A session covers all messages exchanged in that window. If a conversation continues beyond 24 hours, it counts as multiple sessions. |
How agents, knowledge, and workflows connect
Agents, knowledge sources, and workflows are linked through configuration. Two simple ideas govern the model. Once you know them, the rest of the behavior follows naturally.
Tips to get the most value
``` For answers to common questions about capabilities, pricing, availability, and deployment, see the Freddy AI Agent Studio FAQ. ```