Change to standard delimiter on Alert Emails

[jptechnical]

Is your feature request related to a problem? Please describe.

Parsing the email alerts is possible, but difficult if you have a customer with a comma in the name. Also, there isn't any consistency between the delimited sets of information, it starts as commas and then changes to hyphens. This makes it hard to parse the email with a PSA or other tool for creating tickets.

Describe the solution you'd like

Alert email subjects have a standardized and predictable delimiter to ease in parsing. For instance, the first 3 sets of data are obscured in the sample below.

Bob & Associates, Inc., Main, LeoVSer5Pro - LeoVSer5Pro - LeoVSer5Pro - Disk Space Check: Drive 😄 -  Warning Threshold: 95% Error Threshold: 85% Failed - Free: 87%,  Warning Threshold: 95% Error Threshold: 85%

Instead, if the delimiter were, say a pipe, then the Customer | Site | Agent | could easily be regex'd. I don't know what below is actually different elements, so I only piped the first 3 elements.

Bob & Associates, Inc. | Main | LeoVSer5Pro | LeoVSer5Pro - LeoVSer5Pro - Disk Space Check: Drive 😄 -  Warning Threshold: 95% Error Threshold: 85% Failed - Free: 87%,  Warning Threshold: 95% Error Threshold: 85%

Describe alternatives you've considered

1. Custom alert body templates... but this seems kind of heavy handed for what is already a perfectly usable alert notification.
2. Using n8n/zapier to parse them (I will work on this in the interim), but that's kind of heavy when most PSAs already have the ability to parse.
3. Spending the next day fighting with ChatGPT with the one regex to rule them all, only to have it fail in production.

Additional context Add any other context or screenshots about the feature request here.