Agility - OpenText Decision Service Integration and Automation

Common Integration Use Cases Between Agility and OpenText Decision Service

1. Rule-Governed Content Personalization on Websites and Landing Pages

Data flow: OpenText Decision Service ? Agility

Use OpenText Decision Service to evaluate customer attributes, eligibility rules, and campaign criteria, then return the approved content variant or offer type to Agility for rendering on web pages and landing pages. This enables marketing teams to publish content once while ensuring the right message, promotion, or call to action is shown based on business rules such as region, customer segment, account status, or product ownership.

Business value: Improves conversion rates, reduces manual segmentation work, and keeps decision logic centralized so marketing and compliance teams can update rules without changing website code.

2. Compliance-Controlled Content Publishing Approval

Data flow: Agility ? OpenText Decision Service

When a marketer submits content for publication in Agility, OpenText Decision Service can evaluate whether the content is allowed to go live based on rules such as legal disclaimers present, regulated product category, geographic restrictions, or required approvals completed. If the content fails validation, Agility can block publishing and route the item back for correction.

Business value: Reduces compliance risk, enforces publishing standards consistently, and shortens review cycles by automating rule checks before content is released.

3. Dynamic Product Page Eligibility and Offer Logic

Data flow: OpenText Decision Service ? Agility

For content-rich product pages managed in Agility, OpenText Decision Service can determine which product messages, financing options, service bundles, or promotional banners should be displayed based on customer eligibility, inventory constraints, or business policies. Agility then assembles the page using the decision output.

Business value: Prevents customers from seeing offers they cannot use, supports more accurate merchandising, and helps sales and marketing teams maintain consistent offer rules across channels.

4. Guided Customer Journey Routing for Landing Pages

Data flow: OpenText Decision Service ? Agility

OpenText Decision Service can classify visitors or leads into journey paths such as new prospect, returning customer, high-value account, or service issue. Agility uses that decision to present the appropriate landing page content, form, or next-step call to action. For example, a returning customer may see a renewal page while a new prospect sees a lead capture page.

Business value: Increases lead quality and engagement by aligning page content with the visitor?s business context, while allowing journey rules to be updated independently of the CMS.

5. Case Intake and Content-Driven Self-Service Routing

Data flow: Agility ? OpenText Decision Service

Agility-hosted forms, help pages, or service portals can capture user-submitted information and send it to OpenText Decision Service to determine the correct case type, priority, or routing path. The decision engine can apply rules based on issue category, customer tier, product line, or SLA commitments, then return the routing outcome to the portal or downstream workflow system.

Business value: Speeds up service intake, reduces misrouted cases, and improves first-contact resolution by ensuring requests are classified consistently at the point of entry.

6. Region-Specific Content and Policy Enforcement

Data flow: OpenText Decision Service ? Agility

OpenText Decision Service can evaluate location, language, legal entity, and regulatory constraints to determine which content blocks, disclosures, or policy statements Agility should display. This is especially useful for multinational organizations that need different terms, privacy notices, or product descriptions by market.

Business value: Supports global content operations, reduces the risk of publishing incorrect regional content, and helps teams manage localization and regulatory variation through centralized rules.

7. Content Operations Exception Handling and Escalation

Data flow: Agility ? OpenText Decision Service

When content in Agility fails a business rule, such as missing required metadata, expired approval, or conflicting campaign dates, OpenText Decision Service can determine the exception path. It may route the item to a specific reviewer, trigger an escalation, or allow temporary publication with restrictions. Agility can then reflect the decision in the editorial workflow.

Business value: Reduces bottlenecks in content operations, standardizes exception handling, and gives business users clearer guidance on what to fix and who must approve it.

8. Personalized Content for Account-Based Marketing Programs

Data flow: OpenText Decision Service ? Agility

For account-based marketing campaigns, OpenText Decision Service can evaluate account status, industry, pipeline stage, or buying group rules and return the appropriate content theme, case study, or CTA. Agility then serves the matched content across campaign pages, microsites, and digital experiences.

Business value: Helps marketing teams deliver more relevant experiences to target accounts, improves campaign consistency, and keeps targeting logic centralized so it can be updated quickly as account strategies change.