An automation is a trigger plus one or more steps. The trigger is what starts it. The steps are what happens next: a wait, a condition, or an action like sending an email or moving the job's stage.
Make one: go to Tools, then Automations. Type a name in "New automation name" and click "Create automation", or pick one under "Start from a template". "View all" opens every template by category; click "Use this template" and it's built for you, emails and all. You land on the canvas: one line down the page, with round "+" buttons wherever you can add a step. Click any block, including the trigger card, to change it in the panel on the side.
Turn it on: click "Save", then set the canvas switch to "On". "Off" means "Nothing sends until you turn this on". The list shows On or Off. Templates, copies and automations from "Automate with AI" start Off so you can check them first.
Triggers: click the trigger card, then "Change". Pick one under "Starts when":
"Project enters a stage": the moment a job lands on the stage you pick.
"Client books a session": when a client books the session type you pick.
"Proposal went quiet": when a proposal has had no answer for the number of days you set. It uses your own word, like "Quote went quiet".
"Lead form submitted": "Any lead form", or the one you pick.
"Proposal sent": the moment you really share a proposal.
"Payment received": pick "Any payment", "First payment on the job", "Second payment on the job", "Final payment (the balance is paid off)", or "A payment whose label contains..." and type the words. Capital letters don't matter.
"Stage sits stale": when a job has sat in one stage for the number of days you set.
"Manual (run by hand)": never starts on its own. You start it with "Run an automation" on a job's page.
Stop when they answer: on the trigger card, under "Stop this automation when...", tick any of "They reply" (an email or text reply, including texting STOP), "They book a time", or "The job moves to another stage". For that last one, pick a stage under "Stops if moved out of", or leave "The stage it started in". It's checked before every wait ends and before every step runs, so a lead who already answered doesn't get another follow-up. The job's Automations card shows why it stopped, like "Stopped: they replied".
Steps: add one with any "+" button.
"Wait": a real pause before the next step, in minutes, hours or days.
"Condition": splits into Yes and No paths right away. It can check "Proposal responded", "Proposal not responded", "They replied", "They haven't replied", "They booked a time" or "They haven't booked" (proposal uses your own word).
"Action": "Send email", "Send text", "Move stage", or "Recommend a stage (creates a task, doesn't move it)".
Fields in emails and texts: under a text step's message box, click a field to add it, like the client's first name, project name, proposal link, invoice link, client portal link, or the session's date and time. The first name field is written as {{client.firstName|there}}, so someone with no first name on file gets "Hi there". If a message uses a link or session the job doesn't have yet, the automation holds it for your review instead of sending it blank.
Hold for review: every action step has "Hold for my review before sending". Turn it on and that step never goes out on its own. When a run reaches it, it waits on your dashboard's "Needs attention" card with the automation, what it's about to do, and the client and job. "Approve" sends it and the run keeps going. "Skip" skips that step and the run moves on.
My automation isn't running (check these in order):
- Is it On? The switch sits next to "Save" on the canvas and the list shows On or Off.
- Is the trigger set? If the trigger says "No trigger", or a stage, session type or lead form was never picked, nothing starts.
- Give it a little time. Waits and the "went quiet" and "sits stale" triggers are checked on a schedule, not the second they happen.
- Payment label: "A payment whose label contains..." looks for your words in the payment's name on the schedule. To tell a deposit from a production deposit, use "First payment on the job" or "Second payment on the job" instead.
- Already running: if a job already has an active or paused run of that automation, moving it back into the same stage won't start a second one.
- Stage triggers start only when a job enters the stage, not for jobs already sitting there. Use "Stage sits stale" for those.
- "New lead from email" starts when a new inquiry comes through shop email forwarding, once per person. Google Voice texts and voicemails have no email, so they do not join.
- "Manual (run by hand)" automations never start on their own. Use "Run an automation" on the job's page.
Editing a live automation: you can edit an automation while it has active runs in progress. Adding, removing, or reordering steps and saving doesn't wipe out what's already happened: every client mid-run keeps their history, and any run that's waiting or paused stays exactly where it was. One real caveat: if you delete the exact step a run is currently sitting on, that run loses its place. Everything else is untouched by later edits.
The switch next to "Save" on the canvas says "On" or "Off". Off means "Nothing sends until you turn this on". The automations list also shows On or Off. Automations made through "Automate with AI", a starter or a copy begin Off. If yours is not running, check that it is On.
Ask Shop Hand to build an automation and it points you to Automations, then "Automate with AI", with a description ready to paste.