Chat rule conditions for URL targeting only support "equals" and "contains" operators. For customers managing complex page structures without consistent URL patterns, this forces the creation of large numbers of individual rules that are difficult to maintain.

Adding regex as a matching operator would allow admins to define a single pattern that covers an entire class of URLs. For example, distinguishing paid landing pages from email or organic pages within the same URL path structure (/lp/) requires regex today but can only be approximated with a long list of "equals" or "contains" conditions.

Without regex support, customers managing multi-experience setups across large page inventories face significant admin overhead. A single well-written regex pattern can collapse dozens of rules into one.