Sales CRM
Build matching conditions for scores and territories
Use All or Any conditions, typed comparisons and missing-value rules consistently.
Where to start
Sales → Sales CRM setup → Configure rule or Configure territory → Matching conditions
Fields and options
- Access needed
- Administrator
- Permission and scope
- Administrator
Before you begin
Open the correct company workspace and confirm Administrator. Review the original record before following these steps. Open the relevant entry under the native Sales menu; the workspace tabs use shorter labels such as Deals, Reports, Relationships and Sales setup.
Follow these steps
- Choose a deal field. Currency, pipeline, stage, owner and choice fields offer readable selections; numeric and date fields use typed input controls.
- Choose Equals or Does not equal for an exact comparison. Text comparisons ignore letter case; Contains checks a text fragment.
- For numbers or dates, choose At least / on or after or At most / on or before for an inclusive boundary.
- Choose Has a value or Has no value to test whether information is present. These conditions do not need a match value.
- Add further conditions and select All or Any. Use All when combining a deal-value threshold with a specific currency.
- Save and inspect a deal that should match and one that should not.
Check the result
Test both sides of a numeric boundary and confirm an exact threshold matches an inclusive comparison. Test an empty field separately from a field containing a different value.
If something does not look right
If a field selector shows Unavailable field, choose a supported active public field and save the repaired rule. For linked customer or lead references, the numeric value is the existing CRM record ID; use Has a value when you only need to check that a link exists. When a selected value does not appear, refresh the page to load current pipelines, stages, currencies and staff.
Fields, rules and limits
- Each rule supports one to ten conditions. Empty rule sets cannot be saved. Conditions are simple comparisons, not executable expressions.
- A missing field does not match Equals, Does not equal, Contains or a range comparison. Use Has no value explicitly.
- Numeric comparisons support four decimal places; exponent notation and thousands separators are not accepted.
- A checkbox value of No is still a stored value. Match No explicitly rather than using Has no value.
- Only active, public custom fields are available. If any referenced field later becomes private or retired, the whole rule is unavailable.
- Parent territories do not contribute conditions to their children. Configure every territory’s matching logic explicitly.
Related technical reference: Britixo's detailed product guide (opens in a new tab). The screens available to you depend on your configured modules, company and permissions.
Useful next steps
Contact the Proplix team if you need help with your setup. Include the page or record reference and a description of the issue; leave passwords and private access tokens out of the message.