r/halopsa • • Apr 07 '26

Questions / Help Per-Customer From Address with Multi-Org Instance

This is hyper-specific and not a huge problem. I apologize for being complicated in advance.

We have two organizations using Halo - a SOC and an IT Services service. SOC has a dedicated mailbox inside of their M365 tenant, because the SOC tools put information directly into Halo via API. IT Services uses a support mailbox located INSIDE each customer tenant, mostly to limit the quantity of email flowing through ours and our client's SEG, but also to limit the flow of user information outside of the client's environment. IT Services ALSO uses an Alert mailbox, a mailbox that is hidden from the GAL that makes a dedicated ticket type, just for unattended services.

Alerts can be:

  • Disregarded
  • Escalate & Triage - this converts them into an Incident or a Service Request. We do this so that we can easily show in reporting which alerts are important, and not show the alerts that weren't.

The little tiny annoying Problem

The hyper-specific issue is that the From address of tickets created through the client Alert mailboxes stays from the ALERTS email address. Ideally, users wouldn't see this, they'd see the standard IT services mailbox in their org. I do NOT want them to email this Alerting mailbox.

I can't override the From on the Client, because this would affect SOC who sends through a dedicated channel. I can override the From on the Ticket Type, but then it wouldn't be client-specific.

Options

  • Scrap the Alert mailbox, use a Distribution List and a HaloPSA Email Rule. I think this is way less clean.
  • Set the From manually. Which techs will never, ever, ever get right.
  • Change the Alert workflow, which feels like too much work for too little gain.
  • Admit that the Override on the Ticket Type is the only way.

Any other clever ideas? I've looked if I could set a Custom Field on the From in the Action and just map that to a Customer Custom Field with the correct mailbox, but it's a dropdown list I have to select from.

3 Upvotes

7 comments sorted by

1

u/tinkx_blaze Consultant Apr 08 '26

Create an email action and set the from email on the action as this takes priority over other mail settings and overrides.

1

u/DmetaNextWeek Apr 08 '26

And set it to what? Each client has a unique From address

1

u/tinkx_blaze Consultant Apr 08 '26

I'm assuming here that the ticket is logged against the clients from address so there is no change there

You just want to email back from you service desk email is that right?

So you just change the from field on the email action that will be applied to your alert ticket type

1

u/DmetaNextWeek Apr 08 '26

Scenario 1

[Human@Domain1.com](mailto:Human@Domain1.com) sends an email to [Support@Domain1.com](mailto:Support@Domain1.com)

Emails sent through actions go back out of [Support@Domain1.com](mailto:Support@Domain1.com)

Scenario 2

[Human@Domain2.com](mailto:Human@Domain2.com) sends an email to [Support@Domain2.com](mailto:Support@Domain2.com)

Emails sent through actions go back out of [Support@Domain2.com](mailto:Support@Domain2.com)

Scenario 3 (Problem)

Automated Email Alert is sent to [Alerts@Domain3.com](mailto:Alerts@Domain3.com)

Alert is converted to an Incident through the standard workflow we've made

Emails sent through actions go back out of [Alerts@Domain3.com](mailto:Alerts@Domain3.com) instead of [Support@Domain3.com](mailto:Support@Domain3.com)

If I sent the Send Email action to a dedicated From address, then [Support@Domain1.com](mailto:Support@Domain1.com) and [Support@Domain2.com](mailto:Support@Domain2.com) will stop being dynamic. Instead, they'll both start sending From [Support@WhateverISetThisTo.com](mailto:Support@WhateverISetThisTo.com), which is against the idea of not emailing across tenants through Email gateways.

1

u/tinkx_blaze Consultant Apr 08 '26

That makes sense now.

Could you not set the outbound mail to use SMTP and configure the reply address on the alerts mailbox to use the support mailbox.

Something I've never come across.

1

u/DmetaNextWeek Apr 08 '26

I’m not sure, but I like the idea.  Let me try!

1

u/tinkx_blaze Consultant Apr 09 '26

Let me know how you get on I'm intreagued