OpenText Decision Service - Zendesk Integration and Automation

Common Integration Use Cases Between OpenText Decision Service and Zendesk

1. Automated ticket prioritization and routing based on business rules

Data flow: Zendesk ? OpenText Decision Service ? Zendesk

When a new support ticket is created in Zendesk, key attributes such as customer tier, issue type, product line, region, SLA status, and sentiment can be sent to OpenText Decision Service for evaluation. The decision engine applies centralized rules to determine priority, assignment group, escalation path, and required response time. The result is written back to Zendesk to automatically route the ticket to the right queue or agent.

Business value: Improves first response times, reduces manual triage, and ensures high-value or high-risk cases are handled consistently.

2. SLA breach prevention and escalation management

Data flow: Zendesk ? OpenText Decision Service ? Zendesk

Zendesk ticket status, elapsed handling time, customer segment, and case severity can be evaluated by OpenText Decision Service against configurable SLA rules. If a ticket is approaching breach thresholds, the decision service can trigger escalation actions back in Zendesk such as reassigning the case, notifying a supervisor, or increasing priority. Different rules can be applied by product, geography, or contract type without changing Zendesk workflows.

Business value: Reduces SLA violations, supports contract compliance, and gives service teams a controlled escalation framework.

3. Eligibility-based approval for refunds, credits, and goodwill gestures

Data flow: Zendesk ? OpenText Decision Service ? Zendesk

Support agents often need approval before issuing refunds, service credits, or compensation. Zendesk can send case details such as order value, customer history, complaint category, and prior concessions to OpenText Decision Service. The rules engine determines whether the request is auto-approved, requires manager review, or must be denied based on policy thresholds. The decision is returned to Zendesk so the agent can proceed with the correct action.

Business value: Speeds up customer resolution, enforces financial controls, and reduces policy exceptions.

4. Customer entitlement validation for premium support handling

Data flow: Zendesk ? OpenText Decision Service ? Zendesk

Before a ticket is assigned to a premium support queue, Zendesk can pass customer account data, subscription level, warranty status, and contract terms to OpenText Decision Service. The service validates whether the customer is entitled to expedited handling, dedicated support, or out-of-scope assistance. The decision can then update the ticket with the correct service level, routing, or response template.

Business value: Ensures customers receive the support level they purchased and prevents misrouting of entitlement-sensitive cases.

5. Dynamic case handling for regulated or high-risk issues

Data flow: Zendesk ? OpenText Decision Service ? Zendesk

For complaints involving privacy, legal, safety, fraud, or regulated products, Zendesk can send case metadata and keywords to OpenText Decision Service. The rules engine can classify the case as sensitive, restrict visibility, require compliance review, or trigger a special handling workflow. The outcome is then reflected in Zendesk through tags, fields, assignment rules, or internal alerts.

Business value: Reduces compliance risk, improves governance, and ensures sensitive cases are handled by the right teams.

6. Automated next-best-action recommendations for agents

Data flow: Zendesk ? OpenText Decision Service ? Zendesk

Zendesk can send customer context such as issue history, product ownership, open orders, and prior resolutions to OpenText Decision Service. Based on business rules, the service can return recommended actions such as offer troubleshooting steps, initiate replacement, request documentation, or escalate to technical support. These recommendations can be displayed to agents inside Zendesk to guide consistent handling.

Business value: Improves agent productivity, shortens resolution time, and standardizes service quality across teams.

7. Closed-loop policy tuning using support outcomes

Data flow: Zendesk ? OpenText Decision Service and OpenText Decision Service ? Zendesk

Zendesk can provide outcome data such as resolution time, reopen rate, customer satisfaction, escalation frequency, and refund usage back to OpenText Decision Service. Business analysts can use this feedback to refine decision rules for routing, approvals, and escalations. Updated rules can then be pushed back into live decisioning without redeploying application code.

Business value: Enables continuous improvement of service policies, supports data-driven operations, and keeps decision logic aligned with changing business conditions.

8. Automated handling of repeat complaints and exception cases

Data flow: Zendesk ? OpenText Decision Service ? Zendesk

When Zendesk detects a repeat complaint from the same customer or related account, it can send the case history to OpenText Decision Service for rule evaluation. The service can determine whether the issue qualifies for special handling, a higher escalation path, or a predefined exception process. The decision can update the ticket with the appropriate workflow steps and internal notes.

Business value: Helps organizations manage recurring issues more effectively, reduces churn risk, and ensures exceptions are handled consistently.