What We Fixed
- Lead Flow and Automation conditions on number custom fields (currency,
formatted, and percentage formats) now compare numerically. Previously a
condition like “price is greater than 1,200,000” could evaluate incorrectly
because a stored value like1,475,000.00was compared as text rather than
as a number — a rule that should have matched (or shouldn’t have) could
silently do the opposite. - Date custom field conditions now compare by actual date/time rather than as
text. - Multi-select custom field conditions (“equals”, “contains any”, “contains
all”, and “is one of”) now correctly check the selected options, instead of
comparing the whole stored list as one string. - Thresholds typed with separators or symbols —
1,200,000,$400,000,
95%— are now read as numbers on any numeric condition, including built-in
ones such as talk time, texts sent, calls made, and property price.
Previously1,200,000was read as1, so nearly every record cleared the
threshold. - Plain-format number fields (which intentionally preserve leading zeros, like
MLS IDs) are unaffected and continue to compare as text.
This fixes leads being silently misrouted by Lead Flow rules and Automation
conditions that reference number, date, or multi-select custom fields.