We operate a multi-entity FinTech setup in Help Desk, where agents support clients across multiple regulated entities.
When a ticket originates from email, HubSpot usually uses the inbox the customer emailed as the default From address. However, if a client emails the wrong inbox, or the ticket originates from Live Chat, Forms, or a manually created conversation, HubSpot defaults to the primary connected inbox instead.
We need HubSpot to automatically select the correct From address based on a Contact, Company, or Ticket property (e.g. Entity).
Currently, agents must manually change the From address before sending. In a regulated environment, this creates a significant compliance risk, as communications can be sent from the wrong legal entity.
The risk is compounded by the fact that the email editor is collapsed by default, hiding the From address and Subject fields unless the user expands it. These are arguably the most important fields to verify before sending, so it would be beneficial to have an option to keep the editor expanded by default.
As a workaround, we’ve built monitoring workflows that identify emails sent from the wrong entity, flag the ticket, and create follow-up tasks. However, this is reactive rather than preventative.
It would be valuable if HubSpot could:
- Automatically select the correct From address based on a property value (e.g. Entity).
- Allow admins to configure routing rules for outbound email addresses.
- Optionally prevent emails from being sent when the selected From address does not match the ticket’s entity.
- Allow admins to keep the email editor expanded by default.
For organisations operating multiple brands or regulated entities, these enhancements would significantly reduce compliance risk and improve agent efficiency.