GoHighLevel Automation Specialist — SMS Workflow Audit & Repair

GoHighLevel Automation Specialist — SMS Workflow Audit & Repair About the role We're an early-stage insurance-technology company. We run a lead-generation and outreach system in GoHighLevel that sends SMS to property owners and landlords. The system is live and currently misfiring: contacts are being enrolled in sequences they should be excluded from, including contacts that have already been verified and moved to a different stage. We need someone who can find out why, fix it, and then make sure it can't happen again. What you'll do first (the test project) 1. Audit every active workflow, trigger, and automation touching our SMS sending, and produce a written map: what fires, on what trigger, with what filters, and what stops it. 2. Trace a specific set of contacts that received messages they shouldn't have, and tell us exactly which workflow enrolled them and why. 3. Identify the root cause. We expect this to be one or more of: overlapping trigger conditions across workflows, re-entry settings, trigger filters vs. workflow-level filters being confused, tag logic that doesn't account for stage changes, or if/else branches falling through to an unintended path. 4. Recommend a fix — including a segmentation and tag architecture that makes exclusions enforceable rather than hopeful. Deliverable: a short written findings document plus a proposed rebuild plan. We'll pay for this regardless of whether we continue. What you'd do ongoing - Rebuild and maintain SMS and email workflows from written specs we provide - Own tag and custom-field architecture, pipeline stages, and smart list logic - Build and maintain suppression logic: opt-outs, do-not-contact, stage-based exclusions, and quiet-hours windows - Set up and QA new sequences in a sandbox sub-account before anything goes live - Email deliverability work: separate sending domain setup, SPF/DKIM/DMARC, warmup, bounce and suppression hygiene - Document everything so we're not dependent on any single person's memory Required experience - 2+ years working in GoHighLevel specifically. You should have built and debugged multi-branch workflows at volume. - Demonstrated understanding of consent and opt-out handling in SMS: STOP/HELP keywords, global suppression across workflows, and why per-workflow opt-out is insufficient - Comfortable working from a written spec and flagging ambiguity before building - Clear written English, you'll be documenting your work and we'll be reading it Strong plus - Prior work on TCPA-sensitive or otherwise regulated outreach (healthcare, finance, insurance, lending, housing) - Experience with Make.com or similar (our stack includes it) - Experience with two-way SMS conversations routed to human agents Not a fit if: - You've only worked in HubSpot/ActiveCampaign/Klaviyo and are planning to learn HighLevel on this project - You'd import a purchased contact list into an SMS campaign Please answer these in your proposal (we read them; generic proposals are skipped) 1. A contact replies STOP mid-sequence while enrolled in four different workflows. Walk me through exactly what happens in HighLevel, and what you'd configure to make sure it's handled everywhere. 2. Describe a time a workflow fired to the wrong segment. What was the root cause, how did you find it, and what did you change so it couldn't recur? 4. What do you check first when a contact was enrolled in a workflow you didn't expect them to be in? Terms - Paid test project: approximately 4–6 hours, at your quoted hourly rate - Ongoing engagement is hourly, weekly invoicing, no long-term commitment on either side - We own all workflows, documentation, and snapshots produced - NDA required before account access To apply: send your rate, your availability this week, and your answers to the four questions above. Please include one specific example of a HighLevel build you're proud of and what made it non-trivial.