---
title: "Four onboarding follow-ups to stop sending by hand · Upclient"
description: "The thank-you after a signature, the nudge on an overdue task, the hand-off between stages. Four small workflows that cover most of the chasing in client onboarding."
url: https://upclient.app/blog/onboarding-follow-ups-to-automate
---

[← Blog](https://upclient.app/blog)

# Four onboarding follow-ups to stop sending by hand

Workflows · November 15, 2026

Client onboarding rarely goes wrong at the big moments. It goes wrong in the gaps between them: the contract was signed on Thursday and nobody opened the next task until Monday, or the questionnaire came in and sat unread for a week.

Those gaps are all the same shape. Something happened, and someone was supposed to notice and do the next thing. That is what a workflow is for.

In Upclient a workflow is one trigger and a short list of steps. Here are the four we would set up first. They are the same four that ship, switched on, with every template in the library.

## 1\. Agreement signed: open what comes next

**When** a client signs the contract, **then** thank them, tell the project lead, and open the next task in the stage.

This is the hand-off that most often waits on a person. The client has just committed and is ready to keep going, so the questionnaire or document request should be in front of them straight away, not when someone on your team next checks the project.

The step that opens the next task only acts on a task that is still a draft. If you already published it yourself, the workflow leaves it alone.

## 2\. Questionnaire in: get it reviewed

**When** a client submits a form, **then** move the task to In review, thank the client on the task, and nudge the lead if nobody has reviewed it after two working days.

A submitted form is only useful once somebody reads it. Moving the task to **In review** sends the reviewer the usual “Ready for review” email, and the two-day check carries an **Only if** condition: it is skipped when the task is no longer In review, so nobody is reminded about something already done.

## 3\. Stage finished: start the next one

**When** every task in a stage is done, **then** tell the lead and let the client know what happens next.

The end of a stage is where clients most often go quiet, because from their side everything on the list is ticked. One short message that says “Discovery is finished, here is what we are doing now and what we will need from you” keeps the project feeling alive while your team works.

## 4\. Task overdue: chase it once, then escalate

**When** a client task is a day overdue, **then** send the client a reminder, wait two working days, and tell the lead if it is still open.

Chasing is the follow-up people like least and skip most. A workflow does it at the same interval every time, with no awkwardness, and brings a person in only when the reminder did not work. That second step matters: a task that stays overdue after a reminder usually needs a conversation, not a third email.

## Why these four hold up

Automated follow-up earns a bad name when it is wrong: the reminder for something already finished, or two emails about the same thing. A few rules keep that from happening.

- **Roles, not names.** Steps point at “the project lead”, “the primary contact” or “the task that started this workflow”. The same workflow works in every project and keeps working when people change.
- **One message per client per event.** If two workflows react to the same event and both would message the same client on the same channel, only the first is sent. The other step is marked Skipped with the reason.
- **Client preferences count.** A client who turned off task emails in the portal is left out of reminder emails, and the run says who was left out and why.
- **Working days.** Waits can count working days and continue at a set time, using your workspace’s working hours, so a nudge does not land on Sunday morning.

## Check it before it sends anything

A new workflow is Off until you turn it on. Before you do, click **Test run**. It walks through the workflow against something that really happened in the project, or a made-up example, and shows each step as a sentence: “Would email Priya Natarajan (project lead)”. You can open each email as the recipient would get it. Nothing is sent.

Once it is on, every run is recorded: why it started, who each step reached, what was skipped and why. If a step fails, the run says so in plain words with a button to fix the cause, and you can retry from that step without repeating the ones that already ran.

## Where to start

If you use a library template, these four are already there. Open a project’s **Workflows** tab to read them, change the wording of the emails to sound like you, and run a test.

If you are building your own, start with the overdue chase. It saves the most time for the least setup, and it is the easiest to judge: either the task gets done or you hear about it.

The [workflows page](https://upclient.app/workflows) lists every trigger and action, and the [workflow docs](https://upclient.app/docs/projects/workflows) cover recipes, conditions and waits in detail. Workflows only help if the steps they connect are in a sensible order, so if you have not yet, read [the first week with a new client](https://upclient.app/blog/first-week-of-client-onboarding).

## Set up your first client in an afternoon

Start from a template, invite a client, and let the workflow do the chasing.

[Get started](https://app.upclient.app/signup) [Read the docs](https://upclient.app/docs)