Rolling Suds

Leads came in from Google Ads, Google Local Services, the website, Meta, phone calls, HOA communities and referrals. They were answered by hand and often late, and nobody could say which campaign paid off. The job was to centralize all of it in GoHighLevel without replacing Workiz, the tool the crews already use.

• Configured (most of it): the 8-stage pipeline; source, community and campaign tags; business-hours routing for two branches; the post-job workflow with owner-approved templates; CSR permissions; and the reporting dashboard.
• Built: a community landing page, written so it can be copied for the next HOA community.
• Built: a quote form with hidden fields that write the community, campaign, page URL and campaign phone onto the contact.
• Built: the Workiz “estimate accepted” webhook, which stores the job ID on the GoHighLevel contact.
• Built: the past-customer import with de-duplication.
• Wrote the handoff documents.

1. 01

   A trigger that silently skipped leads

   A test HOA lead never entered its workflow. The “Contact Created” trigger checks its tag filter only at the moment of creation, and the tag was added a moment later, so any source tag applied after a contact exists enrolled in nothing. Zapier now creates each contact with its tags in a single write.

2. 02

   An A/B split that bypassed the HOA message

   The 50/50 split sent half of all business-hours HOA leads past the community-specific message. I added the same HOA condition to the B branch so every HOA lead gets it.

3. 03

   Dashboard numbers that looked right but weren't

   An audit of the dashboard found four metrics that looked plausible but were silently wrong. I checked all ten against live pipeline and contact data before handing over.

• GoHighLevel: pipeline, tags, workflows, permissions and the reporting dashboard.
• Workiz: field-service jobs, connected by an “estimate accepted” webhook.
• Zapier: creates contacts together with their tags in one write.
• Lead sources: Google Ads and Local Services, website form, HOA landing pages, referrals.
• Google Business Profile reviews (copied by hand) and CompanyCam (designed).

• Ran the HOA business-hours test live inside Florida working hours and read the execution log for the branch taken.
• Used the workflow test runner to test a path whose form had no tag field.
• Checked that a known repeat customer merged into one contact with tags from both jobs, and that the CSV import fires no live outbound automation.
• Checked all ten dashboard metrics one by one against live pipeline and contact data.
• Submitted the landing-page form and confirmed the community field, tags and opportunity appeared within seconds.

Finished: business-hours routing (HOA priority test passed live), the Workiz webhook, pipeline and tags, the post-job workflow, the dashboard (7 of 10 metrics plus revenue by campaign), CSR permissions, handoff documents, and the landing page and form, verified end to end.

Still open or blocked: Meta and phone lead sources; the Clarity phone integration (which also blocks the average-response-time metric); SMS to real phones, pending a business number and A2P registration; Google Local Services API access, pending a Google Ads Manager account; an agency-level dashboard, which needs a second sub-account; a real ad-spend figure for the ROI tile; and the before/after photo library.