Your documentation states that you use the .NET regex engine, which allows (?i) for case insensitive data, and then (?-i) if you want to continue case sensitivity again. However, these are not accepted values in the web form. If I have (?i) in my regex, the web form states that it is not a valid regex. Allowing this in a regex would be awesome.
If we can't have this, it would be beneficial to be able to have multiple keyword filters in an automation rule. Right now there can only be 1 keyword condition in an automation rule, which is normally fine. But if I want to filter on say "Password reset" and cannot do it without case sensitivity (which would be ideal.) As it is right now, if someone sends in PASSWORD RESET it will be missed. I could possibly get around this by having keyword "password" and keyword "reset" (which actually may be better anyway, since it would catch something like "can you reset my password?") if I could have multiple keywords.
In any case, I'm trying to setup a case insensitive keyword condition with multiple words, and it is proving to be extremely difficult. The only way around it right now would be to do something like: [pP][aA][sS][sS][wW][oO][rR][dD] which is insane, especially with longer words or phrases.
