A silent client usually becomes a lost job or a cancellation. Here is the workflow that tells a named person on your team to reach out before that happens.
Short answer: Build a workflow that starts on the Customer Replied trigger, holds the contact in a wait step for however many days count as quiet for that kind of customer, then uses an if/else branch to check that they are still silent. If they are, send an internal notification and create a task for a named person. HighLevel describes this same pattern in a recent tip post and uses 30 days as its example. The trigger is the easy part. What decides whether it works is how you define silent and who gets the task.
A client who has not answered in 30 days is a reasonable alert for a retainer or a maintenance contract. It is far too slow for a quote you sent on Monday. If you use one window for everything, the alerts either arrive after the job is gone or fire so often that your team learns to ignore them.
Start with the stages you already have in your pipeline and set a different window for each. These are starting points, not benchmarks. Adjust them after a few weeks of real alerts.
| Situation | Clock starts when | Starting quiet window | Task goes to |
|---|---|---|---|
| Open quote | Customer last replied | 3 to 5 days | Estimator or owner |
| Booked job, details unconfirmed | Customer last replied | 2 days | Office manager |
| Job in progress | Customer last replied | 7 days | Project lead |
| Recurring or retainer client | Customer last replied | 30 days (HighLevel's example) | Account manager |
The build is small. Most of the effort goes into the decisions around it, not the steps.
If the if/else cannot tell whether the customer replied again during the wait, give it a marker to read. One option is to update a tag or a custom field in the same workflow every time a reply comes in, and have the condition read that marker instead of guessing.
A notification that goes to "the team" is a notification nobody owns. Assign the task to one user, with a due date of today or tomorrow, and put the customer name, the last thing they said and the pipeline stage in the task body using merge fields. The person who opens it should know what to do without opening three other screens.
Also move the opportunity. A stage called Gone quiet gives you a list you can sort in the pipeline view, and it gives the owner one place to look on Friday. If the customer replies later, a second small workflow can move the opportunity back to its previous stage, so quiet does not become a permanent label.
Re-entry is the first problem. If a client replies on day two of a seven-day wait, does the clock restart, or does the first run fire anyway? The answer depends on your re-entry settings and how you wrote the condition. Run a test contact through it: reply once, reply again mid-wait, and watch the execution log before you trust it with real customers.
The second problem is replies that are not replies. A client who phones you, or answers on a channel your trigger does not watch, can look silent when they are not. Have staff add a tag or change the stage whenever they log a call, and have your condition respect it.
The third problem is mixing the alert with customer-facing messages. It is tempting to add a "just checking in" text at the end of the workflow. Do that in a separate workflow, with consent confirmed and a stop-on-reply rule, or you end up with the pattern we cover in why GoHighLevel keeps sending follow-ups after a customer replies. If a workflow reports success and still does the wrong thing, this debugging post walks through where to look.
The silent alert tells your team that a person has gone quiet. It does not write the follow-up. For open quotes you probably want both: a sequence that nudges the customer, and an alert that fires if the sequence ends and nothing came back. We cover the customer-facing side in quote follow-up automation for contractors, and the stage movement in GoHighLevel pipeline automation.
If your real problem is the first reply rather than the quiet weeks after it, the speed matters more than the alert. That one is in speed to lead in GoHighLevel.
We would list your pipeline stages and write down, for each one, how many days of silence is normal and who owns the next move. Then we would build one workflow per stage group, test each with a contact that replies twice, and turn it on for a single pipeline before the rest. That is a small, fixed-scope piece of work, and it sits inside our GoHighLevel automation service. If you want to talk it through first, you can book a free 30-minute discovery call.
Yaakov (Koby) Oranski, Founder and CEO of Yotomations
Certified GoHighLevel Admin and Partner. Koby designs CRM migrations, two-way integrations, billing systems and AI agents for service businesses, and writes from the engagements described on this site.
Not as a single switch that we know of. HighLevel's own tip post describes building it from workflow parts: a customer reply trigger, a wait action and conditional logic, then a notification to your team. You assemble it yourself or have someone build it.
It depends on the job. A sent quote might be quiet after three to five days, while a retainer client might be fine for 30. Pick the window by asking how long a normal customer in that stage takes to answer, then adjust after a month of real alerts.
It can, but keep that separate from the team alert. A customer-facing message needs consent, stop-on-reply logic and a check that nothing else has already contacted them. Start with the internal alert so a person decides what to say.
Only if your workflow knows about the call. A phone conversation does not necessarily look like a reply to the trigger, so a client who phoned you may still be flagged as silent. Add a tag or opportunity stage change when staff log a call, and have the condition respect it.
You have 2,000 or 20,000 old leads sitting in a CRM. How to import them without duplicates, message them differently from new leads, let AI qualify the replies, and route the live ones to a pipeline your team works.
Learn more
If your pipeline only moves when someone remembers to drag a card, the numbers in it are fiction. Here is how to make GoHighLevel move stages on its own, and what breaks when you skip a step.
Learn more
The seven-touch quote follow-up sequence we use for contractors, with timing, channel and the line that gets a callback instead of silence.
Learn moreBook a 30-minute call. We look at the account live and tell you what is broken, what we would fix first and what it would cost.
No pitch deck. We look at your current setup and tell you what we would do and what it would cost.Need more than GoHighLevel? Yotomations, our parent company, also builds AI agents, custom software and websites.
