Best approach for sending reminders

[JohnnySnow]

Hi Team,

We have a requirement to send reminder notifications to the end user (1st reminder 20 business days, 40 business days & then 3rd reminder 42nd business days) where the state has been in pending.(please note this is a custom app table)

I'm confused as to which approach is better (or if there are other ways to achieve this please do let me know).

1st approach:

Create SLA definition for with condition of state=pending for mentioned business days. This is easier to implement, the only thing that concerns me is the amount of time (in this case 20,40,42 business days)  the SLA flow will wait and the amount of memory consumption can cause issues (correct me if wrong).

2nd approach:

Check the reminder dates in flow designer(like a scheduled job) which would run daily to check if the record has been in pending state and accordingly send notifications. I don't see an issue with this approach.

Need some expert opinion on this.

[AshishKM]

Hi @JohnnySnow , 

Yes, i m also with 2nd approach. We dont need to create SLA for state = pending notifications.

What is expectation from end user, when state = pending, pending with whom, and how this state will change to other state if end-user is responding ( assuming pending the caller/requester ).  

Need to track all three notification flag for record, and when every day job runs it will check all 3 flag for pending records. This flag will help to restrict duplicate notification on same record.

-Thanks,

AshishKM