GHL Expert Needed for Home Services Brands Workflow & AI Agent Optimization

We run marketing operations for a portfolio of home-services brands (lawn care and pest control), each on its own GoHighLevel sub-account. We've just locked a standardized "master build" (pipelines, tags, custom fields, custom values, workflows) and cleaned the first brand's account to spec. We now need an experienced GHL builder to help push that first account over the finish line and then replicate the standard across the remaining brands. You'll work alongside an existing team (a technical reviewer and a scripted/API operator who handles bulk tag/field/value changes). Your lane is the GHL UI build work the API can't do: building, editing, publishing, pausing, and QA-ing workflows. The single most important rule These are live accounts with tens of thousands of real customer contacts. Nothing you build gets published or enabled without review, and nothing goes live that could send email or SMS to a customer base by mistake. Everything is built in draft and reviewed before it is switched on. No workflow is enabled, no bulk action is taken, and no trigger is added that could enroll or message large contact segments until it has been explicitly signed off. You understand how tag-add / tag-remove triggers can accidentally mass-enroll contacts, and you build defensively to prevent it. If you're the kind of builder who "just turns it on to test," this is not the role. Immediate goals (today / tomorrow) On the first brand's account, to definition-of-done, all built in draft and queued for review: Publish the core sales workflows (New Lead sequence, Contacted, Appointment Scheduled, Lost) repointed to the standardized custom values. Build the sales-assignment workflow: new leads routed to a default rep (with a clear path to switch to round-robin later), plus a task + escalation if untouched within a set time. Turn on the two internal lead-notification workflows (web-form and paid-social leads) that are already built but currently off, after confirming they only notify staff. Publish/finish the missed-call-text-back and appointment confirmation/reminder workflows. Publish the AI voice (Goodcall) workflows and wire their routing using the pre-built tag/field set. Pause (do NOT delete) roughly 50 legacy duplicate workflow drafts, per a provided list. Each item is handed to our reviewer before it goes live. Expect to work an in-account punch list and a shared tracker. Ongoing (after the pilot) Replicate the proven build into a clean master sub-account, then roll it out brand-by-brand. Maintain the standard as we onboard new brands. Required experience 2+ years hands-on building in GoHighLevel / HighLevel (agency or multi-location sub-accounts). Deep command of Workflows: triggers, wait steps, if/else, tag and pipeline automation, opportunity vs contact fields, custom values. Proven experience working in live accounts with large contact databases without incident. Comfortable with pipelines, custom fields/values, tags, calendars, and A2P/SMS considerations. Clear written communication and disciplined use of a task tracker. Nice to have Experience with Goodcall or another AI voice agent, DeepLawn or instant-quote tools, and Real Green or similar field-service CRMs. Snapshot creation and multi-account rollout experience. Home-services vertical familiarity (lawn, pest, HVAC, etc.). How we work Draft-first, review-gated. A reviewer signs off before anything is enabled. Daily check-ins and a shared tracker; you mark items "ready for review," not "done/live." We move fast but never at the cost of an accidental send. To apply, answer these Walk me through exactly how you would re-tag or migrate contacts across a live 18,000-contact account without triggering any workflow or sending any message. What specifically do you check first? Describe a multi-brand GHL rollout you've done. How did you keep builds consistent across accounts? Your availability in the next 48 hours (hours and timezone). One sentence: what's the fastest way to accidentally blast a whole customer list in GHL, and how do you prevent it?