Freshservice Freddy AI in 2026

The Freddy AI Agent session cap of 1,200 sessions per user per year is frequently misunderstood. A "session" is any Freddy AI Agent interaction within a 24-hour window. If a user contacts Freddy three times in one day, that counts as one session, not three. At 260 working days per year, 1,200 sessions allows approximately 4.6 sessions per working day per user.

For internal IT service desk use cases (the primary audience for this reference), 1,200 sessions is typically adequate. A 1,000-seat organisation with 50,000 annual tickets and 40% deflection would generate 20,000 Freddy AI sessions, averaging 20 sessions per user per year against the 1,200 cap. The cap is not a binding constraint for internal IT.

The cap becomes relevant for CX-heavy environments (external customer support with high per-user interaction frequency) or internal environments with unusually high ticket rates per employee. If your organisation runs more than 50 tickets per employee per year, model the session arithmetic before committing to Enterprise.

Freddy AI Copilot (agent-facing, Pro+ or $29 add-on): suggested ticket responses, article recommendations, ticket summarisation, conversation sentiment analysis, and resolution note drafting. Copilot does not autonomously act; it assists the human agent.

Freddy AI Agent (end-user-facing, Enterprise-only): conversational self-service via Slack, Teams, portal, and mobile. Handles password reset, access requests, software installation requests, status queries, and KB article surfacing. Action execution (actually resetting a password, provisioning access) requires Freshservice Workflow Automator configuration with your identity provider, adding implementation complexity.

Freddy AI Insights (Enterprise-only): analytics on deflection rate, ticket trend detection, agent-performance analysis, and knowledge-gap identification. Useful for reporting to stakeholders but not load-bearing for the AI capability itself.

Freshservice Freddy AI deploys in 2-8 weeks on an existing Freshservice instance. This is the fastest deployment timeline in the enterprise AI ITSM category by a significant margin. The baseline setup (enabling Copilot for agents and the AI Agent virtual endpoint for users) takes days, not weeks. Configuration of knowledge base connectors, intent scope, and channel activation (Slack/Teams) typically adds 1-3 weeks. Workflow Automator integration for action execution (the part that moves Freddy from answering to doing) adds 2-4 additional weeks.

Freshservice's fast deployment is possible because the platform tightly integrates the AI layer with the core ITSM ticketing system. There is no complex middleware to configure. The constraint is KB readiness: if your Freshservice knowledge base is sparse or out of date, Freddy will hallucinate answers or escalate everything. KB readiness is the implementation task that determines whether a 2-week or 8-week timeline applies.