GHL Sprint Dashboard

Goozone · Seller Onboarding Circuit · v2 · July 2026 · English
🔍

Phase 0: Discovery & Strategy

0/5 Pending ▼
  • Read Marketing Brain HTML — extract focus cluster, brand DNA, buyer psychology
  • Select focus cluster: DM Merchants (Primary)
  • Select pipeline template: Product/Marketplace — Seller Onboarding
  • Define bot role: Internal FAQ assistant + workflow trigger robot
  • Review Strategy Brief and get team approval
Summary

Cluster: DM Merchants · Bot role: Seller FAQ Assistant + Workflow Trigger · Pipeline: Seller Onboarding (7 stages)

🏗️

Phase 1: Account Foundation

0/6 Pending ▼
  • Upload brand logo (horizontal for light, white for dark backgrounds)
  • Set brand colors: Primary #cfa31e · Secondary #111111
  • Create all tags in GHL (12 tags across 6 categories)
  • Connect WhatsApp Business API
  • Configure email sending (SMTP / GHL Email Service)
  • Invite team members with correct permissions
📋

Phase 2: Data Architecture

0/5 Pending ▼
  • Create 6 Contact custom fields (seller_stage, seller_profile, followup_priority, lead_source, registration_complete_date, store_url)
  • Create 3 Opportunity custom fields (package_selected, verification_status, products_published_count)
  • Create 5 WhatsApp templates and submit for Meta approval
  • Configure Business Profile (name, phone, address, hours)
  • Set up user calendars (Kriston + Admin only)
🔄

Phase 3: Pipeline & Imports

0/4 Pending ▼
  • Create pipeline "Seller Onboarding" with 7 stages
  • Import first batch of leads with correct tags (source, profile, priority)
  • Run 1 test contact through entire pipeline before importing 33 leads
  • Confirm manual stage movement workflow (Stages 3 and 6 — no webhooks)
#StageEntryExitWho Moves It
1Lead LoadedPablo uploads contact with 3 tagsCSR begins outreachPablo
2ContactedCSR sends signup link via WhatsAppSeller completes registrationSasha / Rosannah
3Account CreatedRegistration form submittedVerification approvedCSR (manual)
4VerifiedPablo/Sydney approve accountPayout + plan configuredSydney
5Payout & Package SetCSR configures with sellerFirst product publishedCSR
6First Product PublishedNew Arrivals QC checkFinal reviewLaura (product photo QC)
7Registration CompleteManual tag by Sydney/PabloWonSydney / Pablo
Note: No Wappsi webhooks available. Stages 3 and 6 are manual. Stage 6 uses the New Arrivals QC check.
🤖

Phase 4: AI Agent Bot

0/4 Pending ▼
  • Configure AI Agent 🧠 Personality prompt (Seller Support Assistant)
  • Set up 🎯 Objective: answer seller FAQs, escalate complex issues
  • Load knowledgebase: website scrape (4 pages) + 10 FAQ items + Marketing Brain HTML
  • Configure actions: workflow triggers, field mappings, stop bot, transfer to human
⚠ Defer to Phase 2. Do not launch the AI Agent bot during the 33-lead pilot. Validate the human process first. Deploy when Phase 2 opens (55–60 sellers).
🧠 Personality
You are Goozone's Seller Support Assistant. You are friendly, clear, and direct — matching the Goozone brand voice. You answer common questions from sellers about the marketplace. You do NOT handle complex issues. You always escalate to a human CSR when a question is outside your knowledgebase.
🎯 Objective
Answer seller questions about Goozone's marketplace — payouts, delivery, prohibited items, seller plans, how to get started. Your goal is to reduce the load on human CSRs by handling the most common questions instantly. If you cannot answer, transfer to a human.
📋 Full Flow
1. Greet the seller warmly
2. Listen for the question
3. Match against the FAQ knowledgebase
4. If matched: answer clearly with one CTA
5. If not matched: "I'm not sure about that one — let me connect you with someone who can help."
6. Tag conversation with the topic if possible
📢

Phase 5: Marketing Channels

0/3 Pending ▼
⚡

Phase 6: Automation Engine

0/13 Pending ▼
  • Build WF1: Lead loaded → Add to email drip campaign
  • Build WF2: Contacted → Auto-task "Follow up in 48h"
  • Build WF3: Account Created → Email 1 + Notify Sydney/Pablo
  • Build WF4: 24h unverified → Email 2 (Verify)
  • Build WF5: Verified → Email 3 (Payout & Plan)
  • Build WF6: First Product Published → Email 6 (Store is Live)
  • Build WF7: Tag "registro-completo" → Email 5 + Move stage + Notify Kriston
  • Build WF8: 5 days after Account Created → Email 4 (What to Expect)
  • Build WF9: 10–12 days after Account Created → Email 7 (Support Team)
  • Build WF10: 10 days after Registration Complete → Email 8 (Dashboard)
  • Build WF11: 20 days after Registration Complete → Email 9 (Selling Tips)
  • Build WF12: 18 days after Registration Complete → Email 10 (Logistics)
  • Test all 12 workflows with a test contact
#TriggerActionType
1Contact loaded with Stage = "Lead Loaded"Add to email drip campaignEvent
2CSR moves card to "Contacted"Auto-task: "Follow up in 48h if no account"Event
3Stage → "Account Created"Send Email 1 + Notify Sydney/PabloEvent
424h after "Account Created" if not "Verified"Send Email 2Time
5Stage → "Verified"Send Email 3Event
6Stage → "First Product Published"Send Email 6Event
7Tag "registro-completo" appliedSend Email 5 + Move to Stage 7 + Notify KristonEvent
85 days after "Account Created"Send Email 4Time
910–12 days after "Account Created"Send Email 7Time
1010 days after "Registration Complete"Send Email 8 (Newsletter 1)Time
1120 days after "Registration Complete"Send Email 9 (Newsletter 2)Time
1218 days after "Registration Complete"Send Email 10Time
🚀

Phase 7: Assets & Go-Live

0/6 Pending ▼