@CodyGray That pattern looks like it's already caught by Potentially bad keyword in body and Potentially bad keyword in answer Append -force to the command word(s) if you really want to add the pattern you provided.
Yes, I know the circumstances that led up to me taking that action, but I have no idea what I was thinking or why I was thinking that it would be useful.
@SmokeDetector tpu- I had originally marked this one as FP because it could be an innocent question, but I'm changing that in light of the user's history (multiple deleted questions spamming books on Amazon).
[ SmokeDetector | MS ] Bad keyword in answer, bad keyword with email in answer, pattern-matching email in answer, potentially bad keyword in answer, blacklisted user (343): ATM skimming and cloning by willie mcghee on security.SE
@CodyGray A normalized version, {{'19282727056'}}, of that pattern is already on the number watchlist and the pattern you provided is not an exact match to an existing entry on the number watchlist. You can use !!/bisect-number +1 (928) 2727056 to determine which entries on the number lists match that pattern, which would tell you: Matched by +1 (928) 2727056 on line 2982 of watched_numbers.txt: +1 (928) 2727056 found verbatim; 9282727056 found normalized
