OpenText Webroot Unity - Zendesk Integration and Automation

Common Integration Use Cases Between OpenText Webroot Unity and Zendesk

1. Automatic Security Incident Ticket Creation from Endpoint Threats

Data flow: OpenText Webroot Unity ? Zendesk

When OpenText Webroot Unity detects malware, ransomware, phishing, or suspicious endpoint behavior, it can automatically create a Zendesk ticket with the affected device, user, threat type, severity, and remediation status. This gives the service desk immediate visibility into security events that may require user communication, device isolation, or escalation to IT security.

Business value: Faster incident response, reduced manual logging, and better coordination between security and support teams.

2. Security Status Visibility for Support Agents

Data flow: OpenText Webroot Unity ? Zendesk

Endpoint protection status, recent detections, and remediation outcomes can be surfaced inside Zendesk ticket views or user profiles. Support agents can quickly see whether a customer issue may be related to a blocked threat, quarantined file, or compromised device before troubleshooting begins.

Business value: Shorter resolution times, fewer unnecessary escalations, and more accurate first-contact support.

3. Escalation of Repeated Security-Related Support Requests

Data flow: Zendesk ? OpenText Webroot Unity

When Zendesk identifies repeated tickets from the same user or device involving suspicious pop-ups, login issues, or performance degradation, it can trigger a security review in OpenText Webroot Unity. This helps security teams investigate whether the pattern indicates an endpoint compromise or active threat.

Business value: Earlier threat detection, improved cross-team triage, and reduced risk of unresolved security incidents.

4. Automated Customer Communication During Security Events

Data flow: Bi-directional

OpenText Webroot Unity can send threat event details to Zendesk, while Zendesk can manage customer-facing updates, status notifications, and resolution messages. For example, if a managed device is isolated due to ransomware risk, Zendesk can keep the end user informed about next steps and expected recovery timing.

Business value: Better customer experience during incidents, fewer inbound status inquiries, and more consistent communication.

5. Device and User Context for Security-Driven Support Cases

Data flow: Zendesk ? OpenText Webroot Unity and OpenText Webroot Unity ? Zendesk

Zendesk can pass customer, account, or device identifiers to OpenText Webroot Unity so security teams can quickly locate the affected endpoint and review its protection history. In return, Webroot can provide the latest threat and remediation data back to the ticket for support agents and managers.

Business value: Better case context, less time spent searching across systems, and improved collaboration between service desk and security operations.

6. SLA Prioritization for High-Risk Security Tickets

Data flow: OpenText Webroot Unity ? Zendesk

Security events from OpenText Webroot Unity can be used to automatically assign priority, category, and escalation rules in Zendesk. For example, a ransomware detection can create a high-priority incident ticket with immediate routing to the security response queue, while lower-risk detections can follow standard workflows.

Business value: Stronger incident governance, faster handling of critical threats, and more consistent SLA enforcement.

7. Post-Incident Reporting and Trend Analysis

Data flow: Bi-directional

Zendesk ticket outcomes and resolution notes can be combined with OpenText Webroot Unity threat data to analyze recurring endpoint issues, common attack vectors, and support workload tied to security incidents. This supports reporting for IT leadership, security operations, and service management teams.

Business value: Better visibility into operational risk, improved root-cause analysis, and data-driven security and support planning.