How to Set Up a Discovery Call Follow-Up Workflow in Dubsado (That Stops Automatically)

A question came in from Jennifer — and I know she’s not the only one wondering this.

She wanted to know: how do you set up a follow-up sequence in Dubsado for someone who hasn’t booked their discovery call yet… and how do you make it stop the moment they actually schedule?

This is one of those workflows that sounds simple but has a sneaky technical reason why it’s trickier than it looks. Let me walk you through exactly how to build it in Dubsado 3.0.

Why this is trickier than it looks

Dubsado does have a “resend form after X days” option. But schedulers are not forms. They work differently, and that resend feature doesn’t apply to them.

So there’s no native “follow up on this scheduler link in 3 days if they haven’t booked.” You have to build that yourself — with timed email actions and a flow pause trigger that fires when the appointment is booked.

The good news: once you know how, it’s completely doable. And the result is a workflow that follows up for you and stops itself. You never have to think about it again.

Building the Inquiry Received flow

Start in Dubsado 3.0 under Flows > Flow Templates. Create a new template — call it something like “Inquiry Received.”

Your first action: Send a Scheduler with your clarity call (or discovery call) link. Send it via email. Use the smart field for their first name in the greeting — never their full name. (“Hey Lauren” feels human. “Hey Lauren Barr” feels like a mailing list.)

From there, build out a timed sequence. Something like:

• Day 0: Scheduler sent with a brief, warm intro email
• Day 2: Follow-up email — “Hey, just wanted to make sure you got the link! I’d still love to hear more about your business.”
• Day 7: Second call link — a fresh scheduler link in case they lost the first one

This is where a small but important detail comes in.

The two-scheduler workaround

For Dubsado to correctly pause the flow when an appointment is booked, it needs to know which scheduler triggered the booking. If both your Day 0 and Day 7 scheduler actions reference the same named scheduler, Dubsado can get confused about which one to watch for.

The fix: create two slightly differently named versions of the same scheduler. (The underlying availability and settings are identical — just the name is different.) Now your Day 0 action references Scheduler A, and your Day 7 action references Scheduler B. Dubsado can watch each one separately and pause correctly when either is booked.

Pausing the flow when they book

After your follow-up sequence, add two more actions:

1. Change project status to “Call Booked” — one action watching for Scheduler A, one watching for Scheduler B
2. Pause this flow — again, one action per scheduler

The moment a call gets booked (from either link), the flow pauses. No more follow-up emails. No awkward “Hey, want to chat?” messages to someone who is literally on your calendar.

One more option worth knowing: instead of automatically sending every follow-up, you can set emails to require manual approval before they go out. That’s how I have mine built — because sometimes an email conversation happens and the scheduler follow-up doesn’t make sense to send. Requiring approval lets me check before anything goes out, while still keeping the flow paused once they book. You can read more about how Dubsado workflows are structured in this setup guide if you’re newer to flows.

What happens after the call

This is the part people sometimes try to automate, and I want to talk you out of it.

Once the inquiry flow pauses (because they booked), that flow is paused. It won’t see that the call has ended. You can’t add an action like “start the proposal flow after the call wraps up” because the paused flow never gets that signal.

You could theoretically start a separate workflow the moment the call is booked — but then you’d have a contract and invoice sitting on their project before you’ve even talked to them. The invoice gets dated from when they booked the call, not when you’re actually ready to send it. And if they turn out to need a different service than what they originally inquired about (which happens more often than you’d think), you’ve got the wrong booking form already in motion.

My recommendation: after every discovery call, manually go into their project and start the right next workflow. Whether that’s sending a proposal, a “not a good fit” sequence, or a questionnaire — that manual step gives you the flexibility to actually respond to the conversation you just had. And if you’re not sure what a “not a good fit” workflow even looks like, there’s a whole post on that here.

One thing to try this week

Go into your current inquiry flow and check: is there a pause trigger that fires when a discovery call is booked? If not, add it. That one step will save you from accidentally following up with someone who already has a call on your calendar.

If you’re in your Dubsado right now thinking “I need this but I got lost somewhere in the middle” — that’s exactly what I help people with. You can book a free clarity call and we’ll look at what your inquiry flow actually needs.

With systems and a touch of magic on your side, Lauren ✨