The Problem
A pest control company asked me to replace everything still tied to the lead vendor it was leaving, without breaking its website forms, lead notifications or automations, and to add alerts for when something critical fails. The old vendor's webhook had started showing customers a "submission failed" message on the website form. When I looked, the account move had left gaps. Website leads pointed at a workflow that no longer existed, the Yelp app wasn't installed so Yelp leads had no way into GoHighLevel, and Thumbtack leads had no alert at all. Leads came in through several tools, and the team could take days to notice one, sometimes up to a week. By then a lead could have lost interest or gone to a competitor.
The Build
I set one rule first: every lead source lands in one GoHighLevel sub-account the same way, with a source tag, an opportunity and an alert, and I test every fix from the form to Slack. For the alert there were two options. GoHighLevel has its own Slack action, but it doesn't support Slack's Block Kit, so I couldn't design the alert itself: its layout, the details it shows, or buttons that open the lead. In a private channel it also posts as the person who connected Slack instead of as a bot. So a GoHighLevel workflow sends each new lead to Zapier, and Zapier posts the alert to Slack from a bot, with buttons that open the lead. The website form, Thumbtack and Yelp all feed that path, and referral app leads come through their own Zap. If a step fails, the Zap tries it up to 3 times, then emails two people on the team so the lead doesn't sit unseen. Each lead is also added to the company's field-service software, so nobody has to retype it.
Screens
The Outcome
I measured three weeks of real leads. From when a lead was created in GoHighLevel to its Slack alert, the median was 13 seconds, and 9 in 10 alerts arrived in under 30 seconds. The team now has one place to check and one alert for every lead.


