"More than {x} (or no value)" condition in health profile

Comments

4 comments

  • Sean Maguire

    Agree this could be helpful. In case helps (and since it's not currently available), our workaround is to use 2 different health profiles to address these populations.

    (Using your example...) One health profile includes customers with "at least X" as part of the segment criteria. The second health profile includes "attribute does not exist" as part of the segment criteria.

    We can then use the same structure for Good/Average/Poor across both populations and even if customer criteria changes (for example, they have more than X ticket ratings) the health calculation approach remains consistent.

    0
    Comment actions Permalink
  • Thomas Favre-Bulle

    Hi Sean! Thanks, that's a pretty neat trick indeed. I guess that's what we'll have to do for now. Unfortunately that also means multiplying health profiles for every branching...

    0
    Comment actions Permalink
  • Sean Maguire

    Absolutely. It's a total brute force method that is a huge burden to administer (and feels slightly like taking a chainsaw to the patient instead of a scalpel or laser), but it gets the job done. Good luck!

    0
    Comment actions Permalink
  • Thomas Favre-Bulle

    Thanks!

    Since the reverse is implemented, I don't see an engineering reason why it would not be possible.

    And I fail to see a product justification for preventing it as well.

    0
    Comment actions Permalink

Please sign in to leave a comment.