Details about this thread
  • State Not Answered
  • Replies 6 replies
  • Subscribers 294 subscribers
  • Views 1048 views
  • Users 0 members are here
Related content from around SugarClub

Process automation - outreach status

Ada Napierala

Hello, 

I wanted to introduce an automation for some fields in Leads. We have an Outreach Status field (required, in process, engaged) and I was hoping to get it to change based on the following requirements: 

1. To move from required to in process when an Email has been synced to that lead and the email is sent by lead owner

2. to move from in process to engaged when a prospect replies. 

AND 

1. To move from required to in process when a new Note / Tasks is added as "LinkedIn Outreach"

Are any of these possible to build in Process Definition? I think that the second one is doable, I am more concerned about the Emails. 

Parents
  • 0

    Hi ,

    Your intuitions are correct. For the second use case, you would create two process definitions: one each for the Tasks module and the Notes modules. When the record is created in either module with the appropriate criteria, then the related lead is update. The definition would look like the following:

    I put a gateway before the action to update the related field on the lead record to ensure it only updates leads where the outreach status is 'Required'.

    With regards to your first use case, I'm not aware of any way this can be achieved in SugarBPM currently. Evaluating email senders and recipients dynamically to handle business logic is something we have always handled via logic hooks for our clients. You may also want to account for automatic replies (e.g. out of office, mailbox full, etc.) to avoid leads advancing through your business logic unexpectedly.

    Chris

    Co-Founder | SugarCRM's 2024 Global Outfitters Partner of the Year

Reply
  • 0

    Hi ,

    Your intuitions are correct. For the second use case, you would create two process definitions: one each for the Tasks module and the Notes modules. When the record is created in either module with the appropriate criteria, then the related lead is update. The definition would look like the following:

    I put a gateway before the action to update the related field on the lead record to ensure it only updates leads where the outreach status is 'Required'.

    With regards to your first use case, I'm not aware of any way this can be achieved in SugarBPM currently. Evaluating email senders and recipients dynamically to handle business logic is something we have always handled via logic hooks for our clients. You may also want to account for automatic replies (e.g. out of office, mailbox full, etc.) to avoid leads advancing through your business logic unexpectedly.

    Chris

    Co-Founder | SugarCRM's 2024 Global Outfitters Partner of the Year

Children
  • 0 in reply to Chris Raffle

    Hi Chris, 

    Thanks for that. I created something like this: 

    Basically, for new and existing records I want a task to be created and fields to be updated. The only condition that I am missing (between Change fields and Action #1 is a condition that If Field changed from A to B (manually updated by user), then Action 1 - change other fields. 

    Do you know how to add this if condition when somebody is changing a field from A to B?



    For Emails - logic hoops are a bigger thing, I thought to explore the "receive the message" on BPM, but I am not sure if this would work. 

    Ada