2 Replies Latest reply on Jan 2, 2018 1:54 PM by Sanford Whiteman

    How to hack the 'send alert' feature

    Chelsie Cauthon

      I was wondering if anyone knew of a way to maximize the 'send alert' feature when several alerts should be going to the same person.

       

      For example: When an existing contact in our database visits our booth at an event, we send alerts to our sales reps to notify them that their contact stopped by. Sometimes we get several contacts assigned to one sales rep that visit our booth, resulting in several emails to this rep 'alerting' them.

       

      Does anyone have a work around for this to prevent the sales rep from getting spammed by our Marketo automation? I would love for the reps to still receive the notifications, but was hoping for a bulk option in sending if we have several notifications going to the same rep.

       

      Thoughts?

        • Re: How to hack the 'send alert' feature
          Josh Hill

          No, someone asked this the other day. Send Alert is based on Lead, not Owner.

           

          If you have the same alert, you can do Run Once a Day to reduce some of the Alerts. The best thing is to adjust your process.

          • Re: How to hack the 'send alert' feature
            Sanford Whiteman

            Chelsie, not just one but 2 recent threads on essentially the same topic:

             

                 Send one alert - Marketo & Salesforce

                 Manage alerts using smart/trigger campaigns

             

            As Josh notes and as you can see in those threads, throttling alerts is only possible if you use a webhook to maintain a counter (i.e. to only send to each sales rep 3x per hour, or 3x per day per Company, etc.). This works by simply ignoring any alerts that come in after the quota is exceeded.

             

            But even this kind of throttling, which is relatively easy to implement, can't accomplish the concept of an "alert digest" -- that is, one email that rolls up all the updates in a given time period. The reason it can't do this is pretty logical: if everything is triggered, then when the day's first alert  comes through, the system would have no way of knowing there will be a second alert. It has to send the first alert as it comes in.

             

            You can use custom development to generate alert digests, but only if it's worth the expense.