Repeatable “30-Day Silence” Follow-Up Automation

Ask a question
1

Hi everyone,

Product background: We’re a therapy platform. I’m working on an automation that will send out a reminder to users when they haven’t booked a session with a therapist for one month or more. Relevant custom field is called Appointments as Client, which tallies the number of sessions a client has had. I also know when their last appointment at was booked, this field is just called Last Appointment At.

What I want is a perfectly repeatable “one-month silence” follow-up for every session ≥ 2, but I’m running into trigger limitations.

Current setup

  • We have Automation A that fires when our custom “Amount of sessions” field goes from Blank → 1, sending a welcome/reminder sequence for anyone who only ever books session #1.
    That sequence will keep reminding for up to a year if they never book session #2.

What I need now

A second automation (let’s call it Automation B) that, after session #2 (or 3, 4, etc.), waits 30 days, then sends a single “Hey, let us know if you’d like to book again” email, but only if they haven’t already booked another session in the meantime.

And then repeats that same pattern every time they hit a new session milestone.

Example flow:

  1. User books session #1 → Automation A runs.
  2. They book session #2 → Automation A stops for them.
  3. They wait 30 days with no new booking → Automation B sends a one-off reminder.
  4. They book session #3 → reset the 30-day timer.
  5. Wait 30 days → send one more reminder, etc.

Issues

  • The only “Field changes” trigger I see only lets me target a field changing to a specific value (e.g. “to 2” or “to 3”), which would force me to build and maintain a separate automation for every session number.
  • I don’t see a way to trigger based on “field increments by 1 (when value ≥ 2)” or “any time Amount of sessions > 1.”
  • I have a custom date field for their last session (like “Last Appointment At”) but I can only choose specific dates in my if/else blocks, not total time elapsed since that date
  • I’d prefer to avoid parallel automations or convoluted tag swaps just to cover session 2, 3, 4, etc.

My exact question pertains to the issues listed. Are these true limitations of ActiveCampaign? Perhaps I’m mistaken or missing something. TIA!

2

Hey there, we’ve actually just been playing around with a similar scenario, and based on our testing, the “Date based” trigger would work.

You would set it up like in this image: https://go.screenpal.com/watch/cT1DFNnXUdC

The nice thing about this trigger is that it will re-trigger whenever a contact matches the condition. So if your “Last Appointment At” date is updated, the trigger will start checking again.

1 Like
3

Giving this a try. Thanks!