Configure multi-branch commission rules with priority
Establish a hierarchical commission structure that applies different rates based on partner performance, plan type, or time, ensuring correct payout logic.
How it works
The agent creates a new commission rule by selecting an appropriate template (e.g., 'Tiered by customers' or 'Monthly vs yearly'). It configures the General settings, including the rule name, scope (program, group, or partner), and priority. It then defines the Trigger (New payment or New signup) and Action (fallback rate and approval method). Finally, it adds Branches with specific conditions using customer, partner, or payment fields to set exception rates. The agent ensures the priority order is correct so that more specific rules are evaluated before general ones.
Prompt
Paste this into an agent that has the servers below connected. Adjust the names and dates to your own.
Create a new commission rule named 'Partner Tier Bonus'. Set the scope to 'One group' and priority to 50. The trigger is 'New payment'. Set the fallback rate to 10%. Add a branch for partners with '5 or more customers' to receive 20%. Add another branch for 'Monthly' billing type to receive 15%. Save the rule.MCP servers it needs
Source
The vendor page this playbook is drawn from, and the passage that supports it.
The rules are tried from the top of the list down. The first active rule that applies to the sale decides it. Inside that rule, the branches are checked in order.Commission rules | AffiliateRail docs