OpenText Directory Services - Zendesk Integration and Automation

Common Integration Use Cases Between OpenText Directory Services and Zendesk

1. Automated agent and support user provisioning

Data flow: OpenText Directory Services ? Zendesk

Synchronize employee identities, support agents, and group memberships from OpenText Directory Services into Zendesk to automatically create and update user accounts, assign roles, and manage team access. This reduces manual onboarding effort for support operations and ensures that only active employees can access Zendesk.

• New support agents are provisioned with the correct Zendesk role on hire date
• Role changes in the directory are reflected in Zendesk without manual intervention
• Departing employees are disabled in Zendesk to reduce security risk

2. Group based ticket routing and queue assignment

Data flow: OpenText Directory Services ? Zendesk

Use directory groups to drive Zendesk routing rules so tickets are automatically assigned to the right support team based on organizational structure, region, or function. This helps large enterprises align ticket handling with internal ownership models.

• Regional support groups map to Zendesk queues for faster local handling
• Specialist teams such as billing or technical support receive tickets based on directory group membership
• Changes in team structure are reflected centrally through directory updates

3. Single source of truth for employee identity and access control

Data flow: Bi directional, with OpenText Directory Services as the master identity source

Keep Zendesk aligned with the enterprise directory so support staff access is governed by authoritative identity data. This supports consistent access control, reduces duplicate accounts, and simplifies audits.

• Directory attributes determine Zendesk access level and permissions
• Inactive or terminated users are automatically removed from Zendesk access
• Audit teams can verify that Zendesk permissions match corporate identity records

4. Internal support portal access for employees

Data flow: OpenText Directory Services ? Zendesk

Enable employees to authenticate into Zendesk using their existing enterprise credentials managed in OpenText Directory Services. This improves user experience for internal service desks and reduces password reset requests.

• Employees use one set of credentials for support portal access
• Authenticated users can submit and track internal service requests
• Support teams can identify requesters by department or location from directory attributes

5. Context aware support based on organizational attributes

Data flow: OpenText Directory Services ? Zendesk

Pass directory attributes such as department, location, manager, or job role into Zendesk to give agents better context when handling tickets. This improves resolution speed and reduces back and forth with requesters.

• Agents see the requester?s department and office location in the ticket profile
• Tickets can be prioritized differently for executives or critical business units
• Support workflows can vary by role, such as finance, HR, or IT

6. Automated offboarding and access revocation for support tools

Data flow: OpenText Directory Services ? Zendesk

When an employee is terminated or transferred, directory updates can trigger Zendesk account deactivation and reassignment of open tickets. This prevents orphaned access and ensures continuity of service.

• Former agents lose access immediately when their directory status changes
• Open tickets are reassigned to active team members
• Compliance teams gain stronger control over access lifecycle management

7. Support team structure synchronization for operational reporting

Data flow: OpenText Directory Services ? Zendesk

Mirror organizational hierarchy from OpenText Directory Services into Zendesk groups and teams to improve reporting on workload, response times, and service performance by department or business unit.

• Ticket volumes can be analyzed by support team aligned to directory structure
• Managers can review performance for their assigned teams
• Reorganizations are reflected in reporting without manual rework