Best practices, tips & tricks
Written By Timothy Murenzi
Name automations like sentences. "Reminder — nudge client 3 days after estimate viewed" beats "Automation 4." The name and the one-line summary on each card make the list easy to scan.
Test on yourself first. Use A specific email… with your own address, fire a test with ▶, and read the email as your client would.
Add a short delay so you don't feel robotic. An email that lands the same second something happens can feel automated. "Wait 1 hour" or "wait 1 day" reads as more human.
Use "Wait for another event" for anything you chase by hand. Signatures, approvals and payments are exactly what reminder loops are for.
Scope with conditions. If you only care about large invoices, add an amount condition so the automation doesn't fire for every one.
Add a human check where it matters. A Check (approval) step pauses until someone approves — useful before emailing a client about money or delays.
One job per automation. Three small, clear automations are easier to read and edit than one giant one.
Duplicate to make variations. Same flow, different recipient or project type? Use the copy icon and tweak.
Write in your studio's voice. Templates and Walter give you structure; personalise every message in the email editor.
Pause instead of deleting while experimenting. Paused automations are free and reversible.
Review run history monthly. A quick look shows what's firing, what isn't, and what's being skipped.
Switch automations on before you need them. They don't apply to things that already happened — turn them on before a busy season or project launch.
Check Needs review regularly. When procurement slips, Workroom pre-drafts the client email and follow-ups for you there.
Mind the reply-to. Branded emails come from your studio and use its reply-to address, so client replies land where you expect.
Was this helpful?
More in Automations
Automations 101: What they are and how they work Getting started: enabling Automations and building your first one Trigger reference (the "when")Conditions: running only when it mattersStill need help? Ask the team