'Contact Replied' Trigger does not fire on cold inbound emails
J
John Flaniken
The contact replied trigger states that it fires when a message is received from a contact. It doesn't fire when receiving a cold inbound email. Perhaps this is because they client isn't technically 'replying' to an email we sent them. Nonetheless, seems like a simple fix
Log In
K
Keith Besherse
K
Keith Besherse
Prasoon Dadhich Puru Bansal Sales & Marketing Core Platform
I had a discussion with Super User Lou about the limitations of the Customer Replied workflow trigger and If/else action with regard to the header information of an email.
P
Prasoon Dadhich
Keith Besherse Will take a look here
K
Keith Besherse
Prasoon Dadhich thank you very much
K
Keith Besherse
At this time the Customer replied workflow trigger can filter on reply channel = email and message body Contains phrase. But not header contains specific email address.
And If/else branch conditions can check for Contact Details; Email. But not Email for the Location/Account.
A filter for the workflow trigger or a condition check in the If/Else for Header Contains would be very helpful.
K
Keith Besherse
K
Keith Besherse
What I am about to tell you is not a procedure approved by HighLevel. There are a couple significant risks. However, it seems to be working for me.
First: HL is not an email service provider (ESP) so deliverability and reception are not guaranteed. That is why they recommend integration with an ESP, preferably from either Google Workspace or Microsoft Outlook.
Second: I am not convinced the Customer Replied trigger with Channel is Email works consistently on inbound cold email.
Third: If your root domain is the Default Dedicated Domain (DDD) any Dedicated Sending Domain (DSD) will only receive emails which are a direct reply. No cold inbound. No new email drafted from scratch.
Fourth: If your agency has the same root domain as your SaaS your clients will not receive emails without their own DSD.
Fifth: There is no email addressed to filter for the Customer Replied trigger when Channel is Email. Thus you cannot trigger a different workflow for email addressed to sales vs email addressed to support...
With those caveats...
You can have your agency root domain (supersaasagency<dot>com) set as the DDD in the account for your agency. With a different domain (supersaasagency<dot>io) set as the agency domain for system messages. Then you can have subdomains for clients who don't give you a subdomain on their own DNS (client1<dot>supersaasagency<dot>io, client2<dot>supersaasagency<dot>io, client3<dot>supersaasagency<dot>io, ...).
There is no SMTP for emails addressed to your root domain. The address in front of the @ does not matter. All inbound email with your agency root domain should arrive in the Conversations tab.
If you want to test it you can send an email to: ideasboardtest@thebaldguymarketing.com.
K
Keith Besherse
Prasoon Dadhich, you might want to also merge in: https://ideas.gohighlevel.com/automations/p/incoming-email-trigger
Srikanth Chellaboina
K
Keith Besherse
Susmitha Damarla, thank you and Arjun Khurana for talking with me about these concerns. I think you are going in a very good direction!
The ability to use any of the headers set in the Dedicated Domain settings would be fabulous.
P
Prasoon Dadhich
Merged in a post:
Email To - Trigger Automation
J
Joel Buhr
If a TO email is sent to for example bob@em.domain.com or mike@em.domain.com we need the ability to assign that record to bob or mike based on the To value of the inbound email.
P
Prasoon Dadhich
Merged in a post:
Trigger For Cold Inbound Emails
M
Mario Perez
While cold inbound email is possible with lead connector, there isn’t a trigger that works with it. We need a trigger that can be used to tag a cold inbound email contact or add them to a campaign.
More specifically, a way to determine, if the email gets sent to AexampleA@dedicateddomiain.com then one specific action happens, and if it gets sent to BexampleB@dedicateddomiain.com then another specific action happens, like “assign to user”.
K
Keith Besherse
K
Keith Besherse
Maybe we don't even need a new trigger. Just a new filter.
Prasoon Dadhich, Shivam HighLevel, Core Platform, Sales & Marketing
P
Prasoon Dadhich
Keith Besherse Will take a look here and see what can be done
K
Keith Besherse
Prasoon Dadhich, thank you very much!
P
Prasoon Dadhich
Merged in a post:
Email Trigger based on the To Address
R
Raghid (Ray) Nami
It would be great to have a trigger in the automations section that allows us to identify the email address that is receiving the email (In the "To:" field) in order to customize the automations based on the address receiving the email.
Load More
→