Cross-sell recommendation task from complementary product match

Outcome. An account owner gets a specific, named cross-sell recommendation the moment an account's product mix matches a known complementary pairing, instead of a generic "consider upsell" nudge with no product attached.

Workflow map Enrollment, branches and actions at a glance renewal-expansion-029

flowchart TD
    A[Active Products known, no cross-sell task yet] --> B{Has A, not B?}
    B -->|Yes| C[Recommend Product B, create task]
    A --> D{Has C, not D?}
    D -->|Yes| E[Recommend Product D, create task]
    B -->|No| F{Any match found?}
    D -->|No| F
    F -->|No| G[Set recommendation = None]

When to use it, when not to

• UseUse it when the product catalog has known, fixed pairings (owning Product A makes Product B a natural next purchase, for example) and those pairings are stable enough to encode as a small set of branches.
• UseUse it as a more specific companion to renewal-expansion-010, which only detects single-product accounts in general; this fiche matches an actual product combination to a specific recommended add-on.
• SkipDo not use it for a large or frequently changing product catalog. A catalog with many products and shifting pairing logic needs a lookup table outside standard workflow branching, which is a custom object or custom code concern at a higher tier.
• SkipDo not use it on accounts that already own the complementary product; the branches below check for that explicitly.