GHL/ManyChat Automation Expert Needed - Lead Booking System Build

Project Overview AOC (AI Operators Collective) is an outbound/AI consulting agency. Inbound leads come from Instagram and TikTok (via ManyChat) and a warm email list of 1,200 people who downloaded a lead magnet ("the playbook"). We need someone to build out the connective infrastructure between ManyChat, GoHighLevel (GHL), and calendar bookings so leads flow automatically from "engaged" to "booked call" without manual intervention. Current state: ManyChat is set up for comment-triggered DM automation on IG/TikTok, with tagging logic already rebuilt and working correctly (sequential flow: Send Message → Action/Tag → Condition → Split). GoHighLevel is active but underused — no live booking-to-show workflow, no nurture sequence running, no structured pipeline. A five-email nurture sequence for the 1,200-person warm list has been drafted and needs to be built/automated in GHL. There is an existing bug: internal/existing clients manually added to appointments have been receiving external-facing confirmation emails. Needs a tag-based filter fix. Goal: A lead who engages via ManyChat or opens a nurture email should be able to end up as a booked, confirmed, reminded appointment on the calendar with zero manual work from our side. Scope of Work 1. ManyChat → GHL Integration Connect ManyChat to GHL so that tagged/qualified leads (e.g., "clicked-playbook," "qualified-DM") are automatically created/updated as contacts in GHL with the correct tags carried over. Map ManyChat custom fields to GHL custom fields where relevant (e.g., which lead magnet, which platform — IG vs TikTok). Test that tag-based triggers in GHL fire correctly off this handoff. 2. GHL Booking-to-Show Workflow Build a full workflow covering: Booking confirmation — sent immediately on booking. Reminder sequence — e.g., 24hr and 1hr before the call. Personal video touch — a step to include a Loom/personalized video link in the confirmation or reminder (we'll supply the video; you build the automation step). No-show recovery — automated follow-up sequence triggered if a contact doesn't show (rebooking prompt, sequence of 2–3 follow-ups). Client tag filter — contacts tagged "Client" must be excluded/bypassed from this entire external-facing sequence (fixes current bug where existing clients get prospect-facing emails). 3. Pre-Call Sales Assets As part of the booking confirmation/reminder flow, automatically deliver pre-call assets to anyone who books a call — e.g., case studies, results gallery/pricing page link, a short "what to expect on the call" note, testimonials. We'll supply the assets; contractor builds the automated delivery (email attachment/link, or a dedicated pre-call landing page triggered by the booking). Goal: the prospect shows up to the call already warmed up and informed, not cold. 4. Five-Email Nurture Sequence (Warm List) Build the five-email sequence (copy will be provided) as an automated GHL email campaign. Trigger: import/tag of the existing 1,200-contact list. Include appropriate delays between emails (we'll confirm cadence). Sequence should end with a clear CTA to book a call, feeding into the booking workflow above. 5. Pipeline Setup Build a GHL pipeline with clear stages (e.g., New Lead → Booked → Showed → Proposal Sent → Won/Lost — exact stages TBD with contractor input). Ensure contacts move through stages automatically where possible (e.g., booking a call = auto-move to "Booked" stage), with manual stage changes available for the rest. Set up a re-engagement view/segment for past sales-call contacts who didn't convert, so they can be pulled into a follow-up campaign. 6. Email Deliverability Audit sending domain(s)/inbox setup used for GHL email sends (SPF, DKIM, DMARC configured correctly). Ensure the nurture sequence and booking/confirmation emails are set up in a way that protects deliverability — proper authentication, sensible sending volume/warmup if a new domain or inbox is involved, clean formatting (no spam-trigger patterns, excessive links/images). Flag if a separate sending domain (distinct from the primary business domain) is advisable for the 1,200-list send, and set that up if needed. Confirm we're not landing in spam/promotions before the sequence goes live — send test emails across major providers (Gmail, Outlook) and check placement. 7. QA and Handover Full end-to-end test: simulate a lead from ManyChat entry through to booked/confirmed/reminded appointment, and confirm no-show and client-exclusion logic work. Short Loom walkthrough (10–15 min) of everything built, so it can be handed to a future team member/VA without the contractor. Brief written documentation of each workflow (what triggers it, what it does, where to edit copy/timing). Technical Requirements Proven experience integrating ManyChat with GoHighLevel (not just GHL alone — this is the differentiator, ask for examples). Strong GHL workflow builder skills: triggers, conditions, tags, pipelines, calendar/appointment automations. Comfortable with webhooks/Zapier/native integrations as needed to bridge ManyChat and GHL if native integration has gaps. Solid understanding of email deliverability — SPF/DKIM/DMARC setup, domain warmup, and avoiding spam filters at volume. Able to work from existing draft copy (emails, confirmation messages) rather than writing it themselves.