SMS automation not sending unless I've interacted with lead

Talon H. shared this question 15 days ago
In Progress

I have an SMS automation that uses a filter to text leads with high wind.

The issue is that this automation doesn't seem to be happening unless I'm interacting with the lead at some point during the filter's window. For example, if I have a lead booked a month ago that's coming up tomorrow (and matches the filter), the SMS won't be sent until I text the client, after which the automated text gets sent right after. It seems to also get triggered if I open a lead, or if a lead autosaves.

How can I make sure the SMS automation works even if I don't text the client, or don't open/save/view the lead?

Example lead: 64568093 (I can dig and find a dozen more examples, but this is the one I have handy)

64568093

64568093

64568093

Comments (3)

photo
1

Could you provide me with a few more lead examples so I can look deeper into the patterns on which this has been sending?

photo
1

61076381 - was this coincidence? I sent a text immediately prior to the alert going out, but now I see that messages for 61100025, 61349421, 62212375, etc. went out simultaneously with the other alerts. Did my message for 61076381 trigger all of them, or was it purely coincidental?

photo
1

I'm actually having trouble finding more historical examples, but I will add any more here that I catch happening in the moment.

photo
1

It looks like with the second lead it might have been coincidental but from what I see now it looks like this automation is sending properly on it's own.

photo
1

It is just a coincidence but it is set up properly and is working as intended. If you see this alert not go out when it should have please let us know.

photo
1

Just happened again to me: lead 63299439


I sent a message at 1:01, and the automatic message went out at 1:08 right after.

I had been looking back through older leads looking for messages sent closer together, but now I realize there's probably a 15-minute window.

photo
1

Do you have an example of when this didn't go out when it should have?

photo
1

Just happened to me again with lead 65889581. The message should have gone out earlier this week, like it did for lead 64090935 which was sent yesterday morning 16min after the automatic email sent the contract. The text for lead 65849805 went out on 5/31, even--I'm not sure why the one for ...935 didn't go out sooner too.

photo
1

If I find an example of when it should have gone out but didn't I'll add it, but I'm fairly confident that as soon as I open the lead to check the log, that will trigger it sending....

photo
1

Ask and ye shall receive: lead 63305825 should have gone out with those as well. It finally went out just now, right after I interacted with the lead.

photo
1

Please see attached what is your intention with this line in the filter? I think this might be what is throwing it off and it's just coincidental you are noticing it after an email goes out as the timing of the email falls in that window of it being sent.

photo
1

It's certainly not coincidence at this point--I can purposely trigger it happening like I did for 63305825.

The purpose of the "Lead event dates over 1 days in the future" is so that the automation doesn't happen less than 24 hours before the event. I had to add this in because the messages kept sending the morning of the event after I printed the contract. I didn't realize it at the time but I think the reason the messages were sending last minute was because I printed the contract...

photo
photo
1

Just happened again to me: lead 63299439


I sent a message at 1:01, and the automatic message went out at 1:08 right after.

I had been looking back through older leads looking for messages sent closer together, but now I realize there's probably a 15-minute window.

photo
1

We have our developers looking into this further and will advise when we have an update.

Thanks!

Leave a Comment
 
Attach a file