The Problem
They had a big list of leads in GoHighLevel, most of them parked in pipeline stages. Nobody could say which leads needed nurturing again, which didn't fit, which shouldn't be contacted, and which were good. So the team didn't know who to call, and cleaning it up manually ate hours. Under that, nobody could explain how the account ran. Workflows had piled up, and no one knew which automation did what. Earlier fixes made it harder to follow.
The Build
I started with their GoHighLevel workflows, rebuilding the existing ones or starting over from scratch, and tested them end to end. Then I built workflows that sort the leads into those groups. Bad fits all run off one tag, NGMI. A bad-fit form answer, a match on the spam Do Not Call list, or a manual disqualification adds the tag. Six workflows fire from there: opportunities get deleted across every pipeline, active workflows stop, DND turns on, and the contact is blocked from coming back in. Each use case gets its own workflow. Cramming all six into one is bad practice, and one tag keeps it simple for the team to run.
Screens
The Outcome
Bad fits leave active outreach as soon as the tag lands. Removing the tag reverses the chain: DND goes off and the contact can come back in.
Stack
GoHighLevel
Zapier
Aloware
Slack
Calendly