Is your feature request related to a problem? Please describe.
Many organizations use multiple customer-facing email addresses that route into a shared helpdesk, such as:
support@company.com
billing@company.com
provisioning@company.com
sales@company.com
Currently, when agents reply to tickets, the outgoing email is typically sent from the primary mailbox associated with the helpdesk rather than the alias through which the customer originally contacted the organization.
This creates several challenges:
Customers receive replies from a different address than the one they contacted.
Departments appear inconsistent to customers.
Organizations may need to create and manage multiple separate mailboxes instead of using aliases.
It becomes difficult to maintain departmental branding and communication continuity.
Describe the solution you'd like
Add support for sending outbound emails from configured aliases.
Proposed functionality:
Allow aliases to be configured against an Email Account.
When a ticket is created from an incoming email, store the recipient address used by the customer.
When an agent replies, automatically select that alias as the sender address.
Allow agents to override the sender address if they have sufficient permissions.
Display the selected "From" address within the reply composer.
Support common scenarios such as:
Example:
Customer emails:
Ticket is created.
Agent replies.
Customer receives the response from:
instead of:
Describe the alternatives you've considered
Current workarounds include:
Creating separate Email Accounts for each department.
Creating separate Helpdesk Teams and mailboxes.
Using complex routing and assignment rules.
Managing multiple Microsoft 365 or Google Workspace mailboxes.
These approaches increase administrative overhead and licensing costs when aliases would be sufficient.
Additional context
This is a common requirement for MSPs, IT service providers, telecommunications providers, and organizations that operate multiple departments through a single helpdesk platform.
Many email platforms (Microsoft 365 and Google Workspace) support sending from aliases, and Helpdesk could leverage this capability to provide a more seamless customer experience while reducing mailbox sprawl and operational complexity.
Business Impact:
Better customer experience.
Consistent departmental identity.
Reduced mailbox licensing requirements.
Simpler helpdesk administration.
Easier migration from other service desk platforms that support alias-based sending.
Related Ticket ID: 68856
Is your feature request related to a problem? Please describe.
Many organizations use multiple customer-facing email addresses that route into a shared helpdesk, such as:
support@company.com
billing@company.com
provisioning@company.com
sales@company.com
Currently, when agents reply to tickets, the outgoing email is typically sent from the primary mailbox associated with the helpdesk rather than the alias through which the customer originally contacted the organization.
This creates several challenges:
Customers receive replies from a different address than the one they contacted.
Departments appear inconsistent to customers.
Organizations may need to create and manage multiple separate mailboxes instead of using aliases.
It becomes difficult to maintain departmental branding and communication continuity.
Describe the solution you'd like
Add support for sending outbound emails from configured aliases.
Proposed functionality:
Allow aliases to be configured against an Email Account.
When a ticket is created from an incoming email, store the recipient address used by the customer.
When an agent replies, automatically select that alias as the sender address.
Allow agents to override the sender address if they have sufficient permissions.
Display the selected "From" address within the reply composer.
Support common scenarios such as:
Example:
Customer emails:
Ticket is created.
Agent replies.
Customer receives the response from:
instead of:
Describe the alternatives you've considered
Current workarounds include:
Creating separate Email Accounts for each department.
Creating separate Helpdesk Teams and mailboxes.
Using complex routing and assignment rules.
Managing multiple Microsoft 365 or Google Workspace mailboxes.
These approaches increase administrative overhead and licensing costs when aliases would be sufficient.
Additional context
This is a common requirement for MSPs, IT service providers, telecommunications providers, and organizations that operate multiple departments through a single helpdesk platform.
Many email platforms (Microsoft 365 and Google Workspace) support sending from aliases, and Helpdesk could leverage this capability to provide a more seamless customer experience while reducing mailbox sprawl and operational complexity.
Business Impact:
Better customer experience.
Consistent departmental identity.
Reduced mailbox licensing requirements.
Simpler helpdesk administration.
Easier migration from other service desk platforms that support alias-based sending.
Related Ticket ID: 68856