Action rules determine which actions PipeAI recommends after a record is graded. If your rules have gaps, conflicts, or overlaps, you might not get the best recommendations. Here’s how to quickly identify and fix common issues.
When no rule applies to certain records, they won’t receive a recommended action, leading to missed follow-ups.
→ Fix: Make sure every relevant grade and field value is covered by at least one rule.
→ Example: No rule exists for records graded between C+ and D.
Conflicting rules reference conditions that can never be true at the same time, blocking the correct action from being used.
→ Fix: Adjust rule conditions so they don’t contradict each other.
→ Example: Two rules specify different actions for grade A, but only one can be applied.
A record meets multiple rule conditions, leading to only the higher-priority action being recommended. Too much overlap can make it hard to understand why an action was selected.
→ Fix: Refine rule conditions to reduce unnecessary overlap.
→ Example: Rules for levels 3 and 4 overlap, making it unclear why one action was selected over another.
Rules that don’t fully define when an action should be applied can result in unexpected or incorrect recommendations.
→ Fix: Ensure rules include all necessary conditions, such as specific field values, flags, or grades.
→ Example: An action rule triggers for "high-priority" records but doesn’t specify what defines high priority (e.g., grade, flag, or custom field).
If multiple rules apply to nearly identical conditions, they create confusion without improving recommendations.
→ Fix: Combine similar rules into one where possible.
→ Example: Two separate rules apply the same action to records with a B+ or B grade when a single rule could cover both.
Fixing these issues keeps your action rules clear and effective, ensuring PipeAI always recommends the best next steps.