Automatic Daily Runs

What it does

Automatic Daily Runs does the whole find, check and tag routine for you on a schedule. Once a day, at the time you set, Blast Follow-Up finds the most recent blast in the sub-account, checks every recipient's reply history, and tags everyone who never answered with a dated tag like no-reply-oct-14.

Each sub-account has its own schedule. Every run is logged under Recent runs with what it did: which blast, how many were tagged, how many were left out because they replied.

Why it matters

The manual flow works well, but only when someone remembers to run it. Teams that blast daily or several times a week end up with gaps: Monday's blast got tagged, Wednesday's didn't, and nobody noticed until the resend list looked thin.

Native GoHighLevel automation can tag contacts when a message goes out, but a workflow can't easily wait, check every channel for a reply, and tag only the silent ones across a whole blast. The schedule handles that consistently, at a time that fits your sending rhythm. For context on why a reply check is better than a last-message filter, see finding contacts who never replied.

Picking the time is worth a moment's thought. If you blast in the morning, a late-afternoon run gives people most of the day to answer before they're tagged. If you blast late in the day, a run the next evening may fit better. Because each run handles only the newest blast, the schedule works best when it runs at least as often as you send.

How it works

1. Pick the sub-account and open Automatic.
2. Turn on automatic runs.
3. Set Run at (it starts at 6:00 PM) and the Timezone. Choose Every day or Weekdays only.
4. Choose Leave out: anyone who has ever replied, or only people who replied since the blast.
5. Under Blast detection, set:
   • Look back (days, default 7, up to 90)
   • Max gap between texts (minutes, default 10)
   • Smallest blast to count (contacts, default 20)
6. Press Save, then Run now to test.
7. Check Recent runs for each result. Use Remove to delete the schedule.

Good to know

• Latest blast only. Each run handles the newest blast in the lookback window. If you send two blasts between runs, the earlier one isn't tagged automatically; tag it by hand with the Resend Tagger.
• Tag dates follow your timezone. The tag uses the blast's date in the timezone you chose.
• Disconnected sub-accounts show an error in Recent runs instead of failing silently.
• Nothing is sent. Runs only add tags. Your resend still happens in GoHighLevel, when and how you decide.
• Settings match the manual tool, so you can tune detection in the Blast Finder first, then copy the numbers here.
• Weekdays only skips Saturday and Sunday runs, which suits teams that don't blast on weekends.