GitHub Project Repository: customer-action-prioritization

Business Context

Customer operations have limited human capacity. Differentiating treatment without a clear behavioral reason increases risk and wastes time. This project checks for stable, actionable differences in customer data to see if varying levels of attention are actually justified.

The Decision

The goal is to determine if customer behavior warrants specialized handling under current resource constraints.

Decision Mandate

Intervention requires strong proof. Preventing wasted effort is more important than chasing speculative gains through differentiation.

• Sending resources to the wrong customer is a material loss.
• Sticking to a standardized approach is the correct choice when evidence is weak.

Decision gates and enforcement rules apply before any optimization begins.

Evaluation Criteria

Specialized handling is only permitted if the data meets these standards:

• Natural Separation: Groups must exist on their own, not just because an algorithm forced them.
• Stability: Signals have to stay consistent during daily operations.
• Direct Action: Behavioral differences must map to specific workflows.
• Low Risk: The cost of an error has to be lower than the cost of the default approach.

Any data structure failing these tests is ignored.