OpenText Decision Service - Marq Integration and Automation

Common Integration Use Cases Between OpenText Decision Service and Marq

OpenText Decision Service is well suited for centralized, rule-driven decision automation, while Marq is typically used to create and manage branded content, templates, and personalized documents at scale. Together, they can support workflows where business rules determine what content should be generated, approved, or delivered, and Marq produces the final customer-facing asset.

• Policy-based document generation for customer communications
  OpenText Decision Service evaluates customer attributes, eligibility, and business rules to determine which communication template should be used, what content blocks should be included, and whether approval is required. Marq then generates the branded document or PDF, such as a welcome packet, policy notice, or account summary. Data flow: OpenText Decision Service - Marq.
• Automated sales proposal assembly
  When a sales opportunity reaches a certain stage, OpenText Decision Service determines the correct proposal structure based on deal size, region, product mix, discount thresholds, and legal constraints. Marq uses those decision outputs to populate the right proposal template with approved messaging, pricing sections, and branding. This reduces manual proposal creation and improves consistency across sales teams. Data flow: OpenText Decision Service - Marq.
• Eligibility-driven onboarding kits
  For new customer, member, or employee onboarding, OpenText Decision Service checks eligibility rules, geography, product selection, and compliance requirements to decide which onboarding materials are needed. Marq assembles the appropriate welcome kit, checklist, forms, and instructions into a personalized package. This helps operations teams deliver the right materials without manual review. Data flow: OpenText Decision Service - Marq.
• Compliance-controlled approval workflows for regulated content
  OpenText Decision Service can determine when a document must be routed for legal, compliance, or finance approval based on content type, jurisdiction, or risk score. Once approved, Marq produces the final version using the approved template and content rules. This is useful for regulated industries such as insurance, financial services, and healthcare. Data flow: OpenText Decision Service - Marq.
• Dynamic customer retention offers
  OpenText Decision Service evaluates churn risk, contract status, customer value, and retention policy to decide which offer or message is appropriate. Marq then generates the personalized retention letter, email attachment, or offer sheet with the correct branding and terms. This supports customer success and retention teams with faster, more targeted outreach. Data flow: OpenText Decision Service - Marq.
• Channel-specific marketing asset selection
  Marketing operations can use OpenText Decision Service to determine which version of an asset should be used based on audience segment, campaign rules, region, or channel restrictions. Marq receives the decision output and renders the correct version of the flyer, brochure, or campaign document. This reduces versioning errors and ensures brand and compliance alignment. Data flow: OpenText Decision Service - Marq.
• Exception handling for document exceptions
  If Marq detects missing fields, unsupported content combinations, or template exceptions during document creation, it can send the issue details back to OpenText Decision Service. The decision engine can then route the case for manual review, trigger an alternate template, or apply fallback rules. This creates a controlled exception process and reduces failed document generation. Data flow: Marq - OpenText Decision Service.
• Bi-directional workflow for personalized case correspondence
  In case management scenarios, OpenText Decision Service determines the next best action, correspondence type, and required disclosures based on case status and policy rules. Marq generates the correspondence, and delivery or completion status can be returned to OpenText Decision Service to update the case record and trigger the next step. This supports end-to-end operational workflows with clear auditability. Data flow: Bi-directional.