Follow up while you teach, without texting at midnight

A lead asks about your intro offer while you are teaching. An automated reply helps. Another message after they have answered, or a text in the middle of the night, does not help in the same way.

The latest automation controls let you be more deliberate about when a conversation starts, when messages may send, and when a supported text sequence should stop.

Choose the hours your studio should communicate

Communication restrictions are configured per automation. When enabled, you can set a sending window for each weekday, with minute-level timing, and close days that should not send.

For an illustrative studio, weekdays might use a different window from Saturday, while Sunday is closed. The schedule uses your organization’s timezone rather than the timezone of the computer that built the workflow.

If a message becomes due outside an allowed window, it waits for an appropriate opening. You do not need to build a second overnight version of the same sequence.

A delay still means elapsed time

Sending hours do not turn all your delays into business-hour counters. A delay can finish overnight, with the communication then waiting for the next allowed window.

After that message actually completes, the next delay starts from that point. The sequence does not need to dump several overdue follow-ups on a client as soon as the studio opens.

That makes the relationship between timing and message spacing easier to understand. Build the sequence around the conversation you want a person to receive, then use communication hours as its sending boundary.

Stop when someone texts back

The supported Unenroll on reply setting lets a reply stop a text follow-up sequence. It helps prevent a lead from receiving the next scripted nudge after they have already started a real conversation with your team.

This setting is about the supported text-reply workflow, not a promise that every interaction on every social or email channel automatically stops every automation. Review the setting on the sequence you are configuring.

Use a tag as a clear starting signal

The Tag Added trigger gives your team another way to start a relevant workflow. A staff member can apply a meaningful tag during a real customer interaction, and the automation can respond to that event.

For example, your studio might use a tag to distinguish people who have asked about a particular program. That is a deliberate signal, unlike assuming everyone in a broad contact list has expressed the same interest.

Dynamic contact lists solve the separate job of keeping a reusable send audience current. Creating a list does not itself enroll everyone in an automation.

Review one sequence before copying the pattern

Choose a real follow-up your team uses. Check its trigger, allowed sending hours, delays, reply setting, and message wording together. Consent and channel eligibility still apply when the message is sent.

Good automation supports a conversation rather than continuing regardless of it. These controls give a small studio more ways to make that distinction practical.

Explore Zipper automations and the October 12-26 release notes.