About

Job Post (Safe for Competitors) GoHighLevel Automation Specialist — Multi-Branch SMS & Email Workflow Build I'm looking for an experienced GoHighLevel automation expert to build a structured, multi-step workflow for a moving-services business. All content is already written — you will not be writing scripts. This project requires someone who understands: branching logic inbound-sms triggers conditional tagging workflow merging reply detection multi-day follow-up automations integrating pipeline stages with automation 🔧 Project Overview (High-Level Only) You will build two connected GHL workflows. Details of the workflows, branches, and all messages will be provided in a secure document once hired. Workflow 1 — Lead Intake & SMS Follow-Up Trigger: A new contact enters the CRM. Includes: 1 opening message A conditional fork depending on whether the contact replies A unified SMS sequence after the fork Inbound keyword listeners that trigger short sub-sequences Logic to stop the workflow if the lead books, calls, or replies Several “micro-branches” based on user intent Tags that mark specific actions (Exact messages, words, and timing will be provided privately — nothing is included in this public job post.) Workflow 2 — Post-Estimate Follow-Up Trigger: A specific tag or pipeline stage change. Includes: Multiple SMS messages over several days Deposit-based CTA follow-up Route availability reminders Logic to stop automation when the lead takes action (Again — full scripts provided after hiring.) 🎯 What I Need Built Here is what the expert must be capable of, without revealing the internal framework: 1. A fork based on reply/no-reply SMS #1 → wait for reply If replied → go to Branch A If no reply → go to Branch B Then both branches merge back smoothly (Details will be provided privately.) 2. Keyword-triggered micro-branches Workflow must detect specific types of replies, such as: sending photos requesting a walkthrough requesting a phone call asking for pricing asking for timing postponing still deciding Each keyword triggers a separate short sequence (Exact keywords and messages are not written here for privacy.) 3. Route logic + tagging Depending on how the lead is categorized, workflow will send different follow-ups. Tagging structure is simple but must be built cleanly: Tag A triggers one response Tag B triggers another (Full mapping provided privately.) 4. Full clean build You must build: smart waits event-based stop conditions reply detection call/sms stop triggers proper “stop this workflow when X happens” logic all tags needed all custom fields needed 5. Zero duplication All long sequences should merge back into one consistent follow-up path, not multiple parallel ones. 📌 What You WILL Receive After Hiring All proprietary content will be delivered privately in a single Word document: You get: Every SMS and Email All timelines The full branching map Tags list Keywords list Exact conditions for each trigger The sequence logic Pipeline stage rules A visual map of the workflow A checklist for the entire build Nothing in this job post contains scripts or strategy. 🧠 Required Skills GoHighLevel (expert-level) Conversation-based automation Keyword/conditional logic Workflow building (multi-branch) CRM organization Pipeline management SMS deliverability / Twilio experience Strong attention to detail 💬 To Apply Please provide: Screenshots or Loom videos of complex GHL workflows you previously built One example of how you used conditional logic in GHL Confirmation you understand: You will not create content You will only build the workflow architecture