Dubsado Workflow Mistakes I See in Almost Every Account

You built the workflows. You applied them to real clients. And something isn’t working — or you suspect it isn’t but can’t figure out where.

This is post seven in my Dubsado Workflow Series. If you’ve been building along with the series, you’ve set up your inquiry, booking, onboarding, delivery, and offboarding workflows. This post is for when something breaks.

Before we get started — hi, I’m Colie James, Certified Dubsado Specialist and host of the Business-First Creatives podcast.

I audit Dubsado accounts regularly. I go in as an admin, run through the entire client journey in real time, and watch what happens at every step. And after doing this across dozens of accounts — photographers, web designers, brand photographers, stationery designers, coaches — the same mistakes show up every single time.

I want to tell you what to avoid when you are ready to setup your own Dubsado workflow.

This post is that conversation.

Mistake 1: One Giant Workflow for Everything

This is the most common thing I find. One workflow that handles inquiry, booking, onboarding, delivery, and offboarding — sometimes 30, 40 steps long — all chained together.

It feels logical when you build it. One connected process, start to finish. Some tutorials even teach it this way.

Here’s why it breaks: when one step stalls — a to-do task nobody checked off, an approval you forgot to click, a form that didn’t get submitted — everything after it stalls too. And you can’t tell where it broke because you can’t see which step caused the chain to stop. Your client paid you and never got a booking confirmation. You have no idea why.

There’s also a practical problem: when someone picks the wrong session type on your inquiry form and you need to switch them to a different workflow, you’re now untangling a half-loaded proposal from a 40-step chain instead of just starting the right workflow fresh.

The fix is five separate workflows — inquiry, booking, onboarding, delivery, offboarding — each with a clear start, a clear end, and a clear handoff to the next one. When something breaks, you know exactly which phase it’s in. When a client’s situation changes, you swap one workflow without touching the others.

Mistake 2: Overusing “After All Previous Actions Complete”

If you have more than two or three “after all previous actions complete” triggers in a single workflow, you’re using it too much.

I say this in almost every audit I do. And people look at me like I said something wild, because it feels safe — you want things to happen in order, and this trigger seems like it guarantees that.

What it actually does is create a chain where any incomplete step blocks everything after it. Forever. A to-do task you forgot to check off three weeks ago? Everything below it is frozen. A form the client never submitted? Same thing. An approval that’s sitting in the queue because you got busy? Nothing moves.

The most common version of this I see: a booking confirmation email set to fire after all previous actions complete, with a to-do task somewhere above it that’s never been marked done. The client paid. They signed the contract. And they got nothing. Because of a to-do task.

The rule I give every client: if you’re using “after all previous actions complete” more than two or three times in a single workflow, go back through and ask what would actually break if that trigger weren’t there. Most of the time, nothing would.

For anything time-sensitive — booking confirmations, proposal follow-ups, onboarding emails — tie it to a project date or a specific form completion instead. Those triggers watch for one thing and fire when that one thing happens. They don’t care what else is sitting incomplete above them.

Save “after all previous actions complete” for the rare moments where the sequence genuinely cannot continue until everything before it is done. And even then, ask yourself if there’s a more specific trigger that would do the same job without holding everything else hostage.

Mistake 3: Sending the Proposal Manually

This one comes up in nearly every booking workflow audit I do.

You go into the project, find the proposal, and click send yourself — outside of the workflow. Maybe you wanted to review it first. Maybe you wanted to add a personal note. Maybe you just didn’t realize it mattered how it was sent.

It matters. The moment you send the proposal manually, Dubsado loses the ability to watch for “form not completed.” Which means your automated follow-up reminders won’t fire. Which means you’re back to chasing people yourself, checking in on proposals by hand, wondering who’s seen it and who hasn’t.

The fix is simple but non-negotiable: send the proposal through the workflow, every time. If you want to review it before it goes out — totally fine — add an approval step. The workflow loads it, pauses, you make your edits, you approve it, it sends. It still counts. The follow-up triggers still fire.

Sending it manually feels like a small shortcut in the moment. It isn’t. You just traded five minutes of convenience for a booking process you now have to babysit by hand.

Mistake 4: Payment Plan on the Proposal Instead of the Workflow

This one is subtle and it breaks things in ways that aren’t obvious until you’re trying to build something more sophisticated.

When the payment plan lives on the proposal template, you can’t use “first payment made” as a workflow trigger. Which means you can’t automate the email that goes out the morning after someone signs the contract but hasn’t paid yet. You can’t automatically start the onboarding workflow when the deposit comes in. You lose a significant chunk of what makes Dubsado’s automation powerful.

Move the payment plan to the workflow. Every time. It’s one of those changes that takes two minutes and unlocks a lot.

Mistake 5: Proposal Follow-Ups Using “All Previous Actions Complete” with an Approval

This one is so specific that I almost hesitate to put it in a general mistakes post — but I see it constantly so here we are.

The scenario: someone sets up proposal follow-up reminders and doesn’t want them to fire if the client has already booked. So they use “after all previous actions complete” with an approval on the reminder email, thinking the approval gives them a way to stop it if the client books first.

What they don’t realize is that “form not completed” already handles this. It watches the proposal. If the client has booked and completed the proposal, the trigger condition is no longer met and the reminder won’t send. You don’t need to approve anything. You don’t need to babysit it.

When you use “all previous actions complete” with an approval instead, you have to manually approve every single follow-up email before it sends. Which means you’re doing manually what you built the workflow to do automatically. The follow-ups still technically exist — they’re just sitting in a queue waiting for you.

The fix: use “form not completed” as your trigger for proposal follow-up reminders. Remove the approval. Let it run.

Mistake 6: Appointment Reminders Built Into the Workflow

This is one of those mistakes that looks completely fine when you build it and silently fails when a real client goes through it.

The setup: someone builds discovery call or session reminders into their workflow using appointment smart fields — {appointment_date}, {appointment_time}, that kind of thing. Makes total sense. The workflow sent the scheduler link, so the reminders should live in the workflow too, right?

Wrong. Appointment smart fields only work when the email is sent directly from the scheduler itself. An email sent from a workflow that tries to use those fields will either send with blank fields where the date and time should be, or it won’t send at all. Either way, your client isn’t getting reminded. And you have no idea because nothing in Dubsado flags it as an error.

The fix: all appointment reminders live in the scheduler settings. Not in the workflow. All the “see you tomorrow at 2pm” emails should come from the scheduler.

Mistake 7: Auto-Response Sent on a Delay

Last one, and it’s a quick fix.

I was in a photographer’s account recently and her inquiry auto-response was set to send 10 minutes after the form was submitted. She thought it was going out immediately. She’d never noticed the delay setting.

Ten minutes is long enough for someone to move on. To fill out another photographer’s form. To get distracted and forget they ever reached out to you. When someone submits your contact form, you have their complete and undivided attention right now — and a 10-minute delay is throwing that away.

Set it to immediate. Always.

If You Recognized Your Account in This List

These aren’t obscure edge cases. They’re the things I find in almost every account I audit — accounts that are mostly working, mostly running, but quietly losing bookings or creating extra manual work because of a few things that were set up slightly wrong.

If you want to know exactly which of these you have, a Client Experience Audit will tell you. I go through your account in real time, the same way I described in How to Improve Your Client Experience: A Breakdown of My Audit Process, and give you a specific list of what needs fixing and in what order.

If you’d rather rebuild properly from scratch: Systems in Session is where we do that together.

FAQ