A deal closes on a Tuesday afternoon. The sales rep marks it won in GoHighLevel, sends a quick Slack message to celebrate, and moves on. The new client is sitting on the other side, excited, maybe a little nervous, waiting for something to happen. What fills that gap in the next seven days either sets up the relationship or quietly undermines it.
The GoHighLevel workflow I am going to walk through here does not replace the relationship. It makes sure the relationship gets the right inputs at the right time, automatically, without anyone having to remember. A human is still doing the meaningful work. The automation handles the scaffolding.
The Trigger: Pipeline Stage Moves to Won
Everything starts from a single trigger in GoHighLevel: the pipeline stage changes to Won. That is it. No manual flag, no separate onboarding form. The deal close is the signal, and the workflow fires from there.
To set this up, go to Automation in your GHL account and create a new workflow. Set the trigger to Pipeline Stage Changed, filter by your sales pipeline, and select the Won stage. If you have multiple pipelines, build one workflow per pipeline or use conditional branches inside a single one. I prefer separate workflows; they are easier to debug when something goes wrong at 10pm on a Friday.
One important detail: add a small 5-minute wait at the very top of the workflow, before the first action fires. This prevents the welcome email from arriving before the sales rep has had a chance to send their own congratulatory note. You want the automation to feel like a well-coordinated team, not a robot that jumped the gun.
Day Zero: The Welcome Block
The first block of actions fires on day zero, meaning within the first hour of the deal closing. This is what runs:
- Welcome email to the client. A warm, specific email introducing what happens next, who their point of contact is, and what they need to do (if anything) in the first 48 hours. Write this with real language, not a template that sounds like every other SaaS welcome email. Use their first name and the name of whatever they signed up for.
- Internal notification to the account manager. GHL can send an email or Slack notification (via webhook) to the assigned rep. The message should include the contact name, deal value, and a direct link to the contact record. The rep should be looking at the client record within minutes, not finding out from the Slack channel later.
- Task creation for the account manager. A task titled something like "Day 0: Send personal welcome message and confirm receipt" with a due date of same day. This is the human step, a personal note from the rep that no automation should replace. The task is the reminder that it needs to happen; the content is theirs.
Days One Through Three: Setup and Context
After the day-zero block, the workflow pauses for 24 hours and then runs the day-one sequence. This is where you confirm that the client has everything they need to actually get started.
Day one email should be short and functional: here is the login link (or the next step), here is how to reach us if something is not working, here is a link to the one resource they are most likely to need in week one. Do not send a 12-section onboarding guide at this stage. One link, one clear instruction, one contact point.
At day three (another wait step, set to +48 hours from the day-one action), a second task fires to the account manager: a check-in call or message. Not automated outreach at this point, an assigned task with a due date. The client has had three days to hit whatever the first friction point is, and a human asking "how is it going?" at exactly that moment catches roughly 80% of the early confusion before it turns into dissatisfaction. That figure is directional from my own experience across several accounts, but the pattern holds consistently.
Day Seven: The First Health Check
Day seven is the last automated touchpoint in this workflow sequence. Two things run here.
First, a brief check-in email to the client. This one should be genuinely informal: "You have been with us for a week. Anything you are still figuring out? Anything that did not go as expected?" Keep it two sentences. The goal is to surface problems that the client is too polite to raise on their own, not to run a formal satisfaction survey. If you want to include a short NPS or CSAT link, this is a fine place for it; just keep the ask light.
Second, an internal task to the account manager to review the client's activity data and flag any account that looks at risk: very low usage, no activation milestone reached, a support ticket that came in this week with no follow-up. This task is the human judgment call. The workflow can surface the signal; only the rep can interpret it correctly and decide whether to escalate.
What I Leave Out of the Automation
There are three things I deliberately do not automate in the first seven days, and I think the distinction matters.
The first real phone call or video call. Some teams try to automate a calendar booking link into the welcome email and call it a kickoff. That works fine for lower-touch accounts. For anything with meaningful contract value, the first call should be scheduled by a human and framed by a human. The automation can create a task that says "schedule kickoff call within 48 hours"; it should not be the thing that books it.
Any response to an inbound question. If the client replies to the welcome email with a question, that thread goes to a human. Do not route it into an AI draft queue for this window. The first week is not the time to let the client discover that their account manager is half a robot.
The day-three check-in content itself. The task fires automatically. The message the rep sends is entirely their own. I have seen teams turn check-in tasks into templated message sends, and it shows. A client who has just handed over real money and real trust can tell when they are receiving something written in bulk.
Building It in GoHighLevel
The complete workflow has roughly 12 to 15 steps: one trigger, three wait timers, four to five email actions, two to three internal task creation actions, and one or two webhook or notification steps for the rep alerts. None of it requires anything beyond GHL's native workflow builder.
Three configuration details worth writing down before you go live:
- Set wait steps to run only during business hours if clients are in a timezone-sensitive context. A day-one email at 2am is not a disaster; a day-three personal task firing on a Sunday is.
- Use contact tags to mark each client as they move through stages, so you can pull a clean list of "clients in first seven days" at any point.
- Build a re-entry check: if a contact already has the "onboarding-active" tag, skip re-entry. Without this, a deal cycled back to Won fires the workflow twice.
The goal of a well-built onboarding automation is that the client never notices it is automated. They notice that the team was on top of things, that nothing fell through the cracks, that every message arrived at exactly the right moment. The automation makes the team look better. The team is still the thing that keeps the client.
The Part That Compounds
The week-one workflow described here took roughly half a day to build and configure, including testing. It runs on every new account without any marginal effort from the team. The compounding effect is not speed; it is consistency. Every client gets the same quality of first-week experience regardless of whether the account manager had a busy month, was out sick on day three, or simply forgot.
That consistency is what turns an onboarding process from something people mean to do well into something that actually happens well, every time.
If you are setting this up and want to compare notes on trigger configuration or the conditional activation branch, drop me a line.
Comments