Reply To Existing Email Thread Via Workflows
M
Matt Cavanaugh
For email conversations that are now on autopilot with AI it would be great to be able to respond in same thread via workflow.
One possible way this could be accomplished is by making a unique email thread ID that can be accessed via workflows.
For example, when putting a send email action in a workflow there could be an option to copy the unique email thread id.
when setting up a send email action there could be 2 options.
- Start new thread
- Reply to existing thread. - when replying to existing thread it could allow you to use the value in a custom field or value.
Log In
A
Alex Nedelea
It’s hard to believe this issue remains unresolved. It’s a significant problem. My clients frequently ask for a normal email, but they just receive empty ones. It’s quite concerning that this is still not fixed. What has happened to the email chain?
S
Sales & Marketing
Merged in a post:
Email Thread
A
Andrew LeBaron
I just want all the follow-up emails that I have in the workflow to be in one thread so the recipient can see the initial email.
D
Divyam Bhadoria
Merged in a post:
Automated Emails to continue in the same thread
J
Jason Soobramoney
Can we add a feature for automated follow up emails to start in a new thread, instead of new email threads each time
D
Divyam Bhadoria
Merged in a post:
Email Threads Within Automation
C
Caskey Ndaba
I want to send cold emails out but the emails don't automatically reply in the same thread when using automations.
So i want my automated follow ups to be in the same email thread however that's currently not possible.
D
Divyam Bhadoria
Merged in a post:
Ability to send automated emails as replies
L
Leander Howard II (leander@writesea.com)
I'd like the capability to send follow up emails in campaigns as replies instead of new emails. That way it looks less automated.
R
Randolph Taylor
I realized something that proves this feature is possible right now: The functionality to grab the email history already exists in HighLevel.
If you click "Forward Thread," the system successfully grabs the entire conversation history and pastes it into the body.
To the HighLevel Team: Please just apply that exact same "Forward Thread" logic to the "Reply" button! The code is clearly already there. The only reason our replies look "naked" and unprofessional is that the Reply button isn't triggering the same history-grab that Forwarding does.
To other users (The Workaround): If you absolutely need the email history to show up (so the client sees the context) but want to stay inside GHL, don't click Reply.
Click "Forward Thread" instead.
It will paste the full history into the body.
Manually paste the client's email address back into the "To" field.
Send.
It’s an extra step, but it forces the system to include the thread history until they fix the native Reply button.
R
Randolph Taylor
I realized something that proves this feature is possible right now: The functionality to grab the email history already exists in HighLevel.
If you click "Forward Thread," the system successfully grabs the entire conversation history and pastes it into the body.
To the HighLevel Team: Please just apply that exact same "Forward Thread" logic to the "Reply" button! The code is clearly already there. The only reason our replies look "naked" and unprofessional is that the Reply button isn't triggering the same history-grab that Forwarding does.
To other users (The Workaround): If you absolutely need the email history to show up (so the client sees the context) but want to stay inside GHL, don't click Reply.
Click "Forward Thread" instead.
It will paste the full history into the body.
Manually paste the client's email address back into the "To" field.
Send.
It’s an extra step, but it forces the system to include the thread history until they fix the native Reply button.
R
Randolph Taylor
This is critical. Currently, HighLevel acts more like an SMS blaster than an email client. When we reply from inside GHL, it sends a 'naked' message without the previous email history appended. This breaks the professional context for our clients and forces them to dig through their inbox to understand what we are replying to.
The Fix We Need:
Native Threading: Replies sent from GHL must automatically append the previous email body (quoted text) so the client sees the full conversation history, just like Outlook or Gmail.
Gmail Sidebar/Extension: If you can't fix the internal threading, please give us an official Chrome Extension that creates a GHL Sidebar inside Gmail. Let us view Contact Tags, Pipelines, and Notes directly in Gmail so we can reply there (where threading works) without losing CRM data.
Right now, I am forced to reply via Gmail to maintain professional threads, which defeats the purpose of an 'All-in-One' inbox. Please prioritize this
R
Randolph Taylor
This is critical. Currently, HighLevel acts more like an SMS blaster than an email client. When we reply from inside GHL, it sends a 'naked' message without the previous email history appended. This breaks the professional context for our clients and forces them to dig through their inbox to understand what we are replying to.
The Fix We Need:
Native Threading: Replies sent from GHL must automatically append the previous email body (quoted text) so the client sees the full conversation history, just like Outlook or Gmail.
Gmail Sidebar/Extension: If you can't fix the internal threading, please give us an official Chrome Extension that creates a GHL Sidebar inside Gmail. Let us view Contact Tags, Pipelines, and Notes directly in Gmail so we can reply there (where threading works) without losing CRM data.
Right now, I am forced to reply via Gmail to maintain professional threads, which defeats the purpose of an 'All-in-One' inbox. Please prioritize this
K
Keith Besherse
Core Platform Sales & Marketing https://ideas.gohighlevel.com/automations/p/custom-reply-to-email-address-option-within-automations-workflows
Load More
→