- Load data into MDA
- Map Account Id to MDA
- Write Contact to Account
- Map Contact ID to MDA
- Send emails via Copilot
Is there a way to schedule a copilot email to run at the end of a rule chain?
We are sending emails from Copilot that first require a few rules to run. The Copilot email pulls from one of our MDA tables. Before the email can be sent, we:
Is there a way to schedule a copilot email to run at the end of a rule chain?
Is there a way to schedule a copilot email to run at the end of a rule chain?
Page 1 / 1
Unfortunately not at this time. You'll have to rely on aligning the schedule. I'm assuming this is the workaround for the operational email limit. It is something we are monitoring and hoping to increase soon.
We have been struggling with the same issue. It would be great if rule chains could include Outreaches mixed in (we have dependent rules that then run after Outreaches). Currently we leave a 1 hour window before and after our Outreaches and cross our fingers. When our Rules and Outreaches run over each other we have to manually recover by running everything in the correct order.
If you have problems with rules running into Outreaches you could evaluate having the last rule in your rule chain insert a piece of data that is checked by the Powerlist. That way you prevent emails from being sent if that last rule hasn't finished. You could then evaluate scheduling an internal Outreach at the exact same time to notify you if partial data is in MDA and customer Outreach couldn't be sent.
If you have problems with rules running into Outreaches you could evaluate having the last rule in your rule chain insert a piece of data that is checked by the Powerlist. That way you prevent emails from being sent if that last rule hasn't finished. You could then evaluate scheduling an internal Outreach at the exact same time to notify you if partial data is in MDA and customer Outreach couldn't be sent.
This actually isn't the work around for the operational email limit. Since a lot of our data does not natively live in SFDC or on Customer Info but instead in MDA, any time we want to send an email with specific keys they typically are in MDA. To avoid having to write several new fields into SFDC of Customer Info, we load an MDA table and pull from there. Because of this, we have to write account ID and contact ID to the MDA table. Some of the tables we upload to daily. Therefore we have to run the rules to connect the Account ID and Contact ID.
Since we can't trigger a copilot email based off another activity but instead only at a specific time, we must either build in a time buffer in the Copilot schedule or trigger them manually to ensure everything has been mapped first.
Since we can't trigger a copilot email based off another activity but instead only at a specific time, we must either build in a time buffer in the Copilot schedule or trigger them manually to ensure everything has been mapped first.
Good work around, Jeffrey. Still, we totally acknowledge that making sure Outreaches happen after certain data processing finishes is a legit issue. Don't have a perfect answer at this time.
Reply
Sign up
If you ever had a profile with us, there's no need to create another one.
Don't worry if your email address has since changed, or you can't remember your login, just let us know at community@gainsight.com and we'll help you get started from where you left.
Else, please continue with the registration below.
Welcome to the Gainsight Community
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.