I think several requests on the Ideas Board are symptoms of the same underlying issue: HighLevel currently treats multiple types of email as though they belong to the same sending architecture.

In practice, there are at least three distinct categories of email:

> Personal or one-to-one communication written and sent by a user.

> Transactional or system-generated messages triggered by workflows, notifications, receipts, reminders, etc.

> Marketing or bulk email sent to larger audiences through campaigns.

Each serves a different purpose and carries different deliverability considerations.

Personal email should support natural business communication, route replies back into Conversations, and allow users to work from within the CRM instead of managing separate systems.

Transactional email should prioritize reliability and consistency, and can often be separated onto a dedicated sending domain or subdomain.

Marketing email carries the greatest reputation risk and is typically best isolated from business-critical communications so bulk sending activity does not impact day-to-day correspondence.

I encourage the product team to think about this as an email classification and sending architecture problem rather than a simple sender-address feature request. Solving it at that level could address multiple deliverability and workflow requests across the platform at once.

Leads have complained that previous discussions were not included in replies to them. I agree with @silvia hua that this feature - which is default by all email platforms and applications - is needed.

API needs clear reply to thread option for any AI agents to make sense in Highlevel.

Yes. And show what address the email is going to (primary and Cc/Bcc):

Also need CC and BCC option at the same time

It seems very odd when you click Reply in the conversation view to an existing email to NOT have the original message included in the reply message, no other email client behaves like this.

make it optional