One trigger can hold more than one step. A "Deal moved into a stage" automation can send an email, then a text three days later, then file a task a week after that - all from the same card, all counted from the same moment.
Watch Mandric walk you through this topic
8:43Add a Second Step Behind the First
Open a trigger and use Add Step at the bottom of the Steps column, or the small plus between two existing steps to insert one between them. Each step is its own card: pick what it does (email, text, task, notification, tag, or a call list round), then set its timing. Dragging a template onto a trigger from the template library works the same way - it lands as a new step at the end, written as a draft so you can look it over before it sends.
How a Step's Timing Is Counted
Every step's day count is measured from the moment the trigger fires, not from the step before it. A step reading "3 days after the trigger" fires three days after the deal moved into the stage, whatever the step ahead of it is doing. Two steps can share the same number and fire the same day. This matters when you reorder steps: moving a card up or down changes which message sends first, but not the number sitting in its own timing field - check each one after a reorder.
The blue clock chip on each card, and on the Review tab, says when that step goes, such as "Sends immediately" or "Sends in 3 days". Hover it for the full sentence, such as "Sends at 9:15 AM in the client's timezone." The PDF export lists the same timing in its When column.
Send at a Set Time of Day
To land a message at a friendly hour, open the step, expand Advanced, and set Time of day (for example 9:15 AM). Once the step's wait is over, it holds for the next 9:15 AM on your client's clock, worked out from the address on their profile, the home address on their application, or the property on their deal. A client none of those place goes by your own timezone. Clear the field to send the moment the wait ends. The card's chip then reads "9:15 AM client's time". You can also ask your assistant to set it, for example "send the check-in at 9:15 AM".
The Renewal Countdown as a Worked Example
Renewal auto outreach is the clearest case, because it starts pre-built. A fresh renewal trigger opens with seven steps already timed at 12, 9, 6, 4, 3, 2 and 1 months before the mortgage's maturity date - you only need to pick or write the copy for each one. The field on a renewal step reads "days before renewal" instead of "days after the trigger," because the trigger itself anchors 360 days out and counts down; enter how close to renewal you want a step to land and it works out the rest. Add an eighth step and it starts at the same spacing as the one before it, ready to retime.
Waits and Repeats on the Canvas
The flat card above covers a straight sequence. Turn on Advanced and a canvas can also hold a wait block, which pushes every step after it back by a fixed number of days, and a repeat block, which sends the same step again every few days for a set number of times - a reminder that goes out weekly for up to a year rather than once. A wait's Counts From choice runs it Since the Previous Step or Since the Trigger Fired, which holds it to that day of the automation.
Stopping the Chase Once They Answer
A repeat on the canvas can also stop itself. Set it to chase until the client replies, finishes a task, submits a portal request, or uploads a document, and the moment that happens the remaining reminders in the loop are cancelled - only the last scheduled copy acts as a real deadline, so an early reply is never beaten by a reminder that was already queued. Point a separate step at what happens once they do answer, and the sequence branches into a real "thanks, here's what's next" instead of trailing off.
What to Do Next
- Write an Automation Template to give each new step its own copy instead of reusing one message everywhere.
- Branch on What the Client Does to send a different step depending on how they respond.
- Build Your First Automation if you are starting from a trigger with no steps yet.