Zendesk announced Employee Service AI Agents and Advanced Action Flows on October 19 to automate internal company requests, from application access to equipment management. The two components are offered through the company’s open early access program. Zendesk places general availability in the coming weeks, as a subsequent stage after the current program.

The agents interpret an employee’s request, while workflows coordinate the necessary operations in the organization’s systems. The capabilities target IT, human resources and workplace teams. Announced examples include access approvals, laptop replacements, employment verification letters and badge access, as well as the processes involved when someone joins or leaves a company.

Three colleagues reviewing laptops and work documents in an office
Mikhail Nilov

The request continues across company systems

The product combines a conversational interface with administrator-built workflows. An employee can make a request in Slack or Microsoft Teams, and an agent connected to Advanced Action Flows initiates the steps in the underlying applications. In this architecture, the conversational response is linked to process execution, including the rules and approvals established by the organization.

Zendesk describes onboarding as a process involving several teams: preparing equipment, enabling access and completing the necessary paperwork require coordination. The proposed automation follows that sequence of operations across systems. The company therefore presents an individual request as an entire workflow that can include both information to consult and actions that need to be carried out.

When building an automation, an administrator describes the intended outcome in natural language. According to Zendesk, Advanced Action Flows helps identify and configure the required integrations and generates the business logic connecting them. Administrators can create, test and refine workflows rather than configuring every operation exclusively through a visual editor with elements dragged into place.

Fixed rules and different paths within one workflow

The capabilities had already been described in a Zendesk presentation updated on October 4. The October 19 announcement adds early access usage figures and specifies the current distribution stage. This timeline separates the present announcement from the earlier existence of documentation and participants who could use the workflows before the broader general availability stage.

In a laptop replacement example, a workflow can check available equipment, employee eligibility and the necessary approval before arranging delivery. Zendesk explains that routine steps can follow predefined rules, while elements that depend on context can take different paths. The configuration follows the company’s actual process, including the exceptions associated with it.

If information is missing, the workflow can ask a follow-up question. When equipment is unavailable, the request can be routed to procurement or sent for human review. These are examples the company has published of branching processes. Approvals and safeguards remain part of the workflow’s organization, including when AI helps determine which path should come next.

The connection with applications with AI integration lies in coordinating conversation, internal data and permitted operations within company systems. In the solution Zendesk describes, the agent connects to workflows that perform those operations. Tool connections, process logic and approvals are separate components of the same automation, managed within the organization.

Information access follows existing permissions

Employee Service AI Agents can consult knowledge sources such as Google Drive, SharePoint and Confluence, according to the product presentation. Zendesk says that information can be connected without moving or duplicating files. Search and answers use the company’s internal sources, with access tied to the rights of the person seeking help within the integrated configuration.

The company names identity providers such as Okta and Active Directory, alongside support for file-level permissions. These capabilities concern the information an employee is authorized to see. In a process involving several departments, access to documents and steps requiring approval are therefore described separately from the simple act of asking a question in a conversation.

In addition to Slack and Teams, agents can be accessed through an organization’s internal Help Center. Zendesk states that history and context carry across supported channels. The stated objective is to let a request continue within the tools an employee already uses, while actions are coordinated through connected systems operating behind the conversation.

The early access figures are company estimates

Zendesk reports that 300 customers completed six million workflow executions with Advanced Action Flows during the first five weeks of early access. The company associates that volume with an estimated saving of 500,000 hours of manual work. The reported metric measures workflow executions rather than equating them with the same number of employees or unique requests.

The published calculation uses an assumed saving of five minutes for each execution. Applied to six million executions, this produces 30 million minutes, or 500,000 hours. The figure represents Zendesk’s estimate using that benchmark, rather than a total obtained by individually timing each operation across the 300 organizations participating in the early access program.

The product page presents AI agents in Employee Service Suite Growth plans and above, with pricing based on automated resolutions. The terms separately describe resolutions powered by external knowledge sources and those based on content within Zendesk Help Center. This commercial information about the agents does not change the early access status specified for the package announced on October 19.

At the current stage, the announcement connects three components: building automations through natural-language descriptions, coordinating operations across systems and accepting requests within employees’ existing work tools. General availability remains the next stage stated by Zendesk. Current participation takes place through the early access program, ahead of that wider expansion of availability.