OpenText Decision Service - Loci Integration and Automation

Common Integration Use Cases Between OpenText Decision Service and Loci

OpenText Decision Service and Loci complement each other well in environments where content personalization must follow governed business rules. OpenText Decision Service provides consistent, auditable decision logic, while Loci delivers AI-driven content recommendations based on user behavior and content analysis. Together, they enable organizations to personalize content delivery without losing control over policy, compliance, or business priorities.

1. Rule-Governed Content Recommendation for Customer Portals

Use OpenText Decision Service to determine which recommendation rules apply to a user segment, then pass those rules to Loci to generate personalized content suggestions. For example, a financial services portal can use decision rules to restrict certain product content based on customer profile, region, or eligibility, while Loci recommends the most relevant approved articles, offers, or next-best actions.

• Data flow: OpenText Decision Service to Loci
• Business value: Improves personalization while enforcing eligibility and compliance rules
• Operational benefit: Marketing and compliance teams can update rules without changing application code

2. Personalized Content Prioritization Based on Business Policy

OpenText Decision Service can assign priority scores or decision outcomes that influence how Loci ranks recommended content. For instance, a healthcare provider may want educational content about preventive care to appear before promotional content for certain patient groups. The decision engine sets the priority logic, and Loci uses it to tailor the recommendation order.

• Data flow: OpenText Decision Service to Loci
• Business value: Aligns content recommendations with strategic business goals
• Operational benefit: Ensures recommendation logic reflects current policy and campaign priorities

3. Dynamic Content Eligibility Filtering Before Recommendation

Before Loci returns recommendations, OpenText Decision Service can evaluate whether a piece of content is eligible for a specific user based on consent status, geography, account type, or regulatory constraints. This is especially useful in industries such as banking, insurance, and public sector, where content visibility must be tightly controlled.

• Data flow: OpenText Decision Service to Loci
• Business value: Reduces risk of serving non-compliant or inappropriate content
• Operational benefit: Centralizes eligibility logic across channels and content types

4. Behavior-Triggered Decisioning for Next Best Content

Loci can detect user behavior patterns such as repeated searches, article views, or content abandonment and send those signals to OpenText Decision Service. The decision engine then determines the next best content action, such as recommending a tutorial, escalating to a support article, or suppressing repetitive content. This creates a more structured response to user intent.

• Data flow: Loci to OpenText Decision Service
• Business value: Improves engagement and conversion by responding to user intent with governed actions
• Operational benefit: Enables business teams to define decision thresholds for behavioral triggers

5. Campaign Rule Enforcement for Personalized Marketing Content

Marketing teams can use OpenText Decision Service to enforce campaign rules such as audience exclusions, frequency caps, or offer eligibility. Loci then uses those decisions to recommend only approved campaign content within CMS-driven experiences. This is useful for enterprise marketing teams managing multiple campaigns across regions or product lines.

• Data flow: Bi-directional
• Business value: Prevents conflicting or overexposed campaign content
• Operational benefit: Supports coordinated workflows between marketing, compliance, and digital teams

6. Content Recommendation Governance for Regulated Industries

In regulated environments, Loci can generate recommendations from content libraries, while OpenText Decision Service validates whether the content can be shown based on policy rules. For example, an insurance company can recommend claims guidance, policy updates, or educational content only if the content matches the customer?s policy type and jurisdiction.

• Data flow: Bi-directional
• Business value: Balances personalization with regulatory control
• Operational benefit: Provides a clear audit trail for recommendation decisions

7. Analytics-Driven Rule Refinement for Content Strategy

Loci analytics can identify which content recommendations perform best across segments, and those insights can be fed into OpenText Decision Service to refine decision rules. Business teams can then adjust rules to favor content types with higher engagement, better conversion, or lower bounce rates. This creates a continuous improvement loop between AI recommendations and governed decisioning.

• Data flow: Loci to OpenText Decision Service
• Business value: Improves content performance using real user engagement data
• Operational benefit: Enables faster rule updates based on measurable outcomes

8. Case or Workflow Content Assistance in Service Portals

In customer service or case management portals, OpenText Decision Service can determine the appropriate content category based on case type, customer tier, or issue severity. Loci then recommends the most relevant help articles, knowledge base entries, or guided next steps. This reduces agent workload and helps customers resolve issues faster.

• Data flow: OpenText Decision Service to Loci
• Business value: Improves self-service resolution and support efficiency
• Operational benefit: Helps service teams deliver consistent guidance across channels