SmartMarketingSuites

Architects conversion-optimized webinar funnel considering offer type, audience sophistication level (problem-aware, solution-aware, product-aware, most-aware), and traffic source. Outputs complete webinar funnel architecture including registration page elements, confirmation sequence, webinar structure with pitch flow, post-webinar follow-up sequence, and call booking flow. Example prompts: 'Design a webinar funnel for my high-ticket coaching program', 'Architect a conversion-optimized webinar funnel', 'Build a webinar registration and follow-up system'

webinar-funnel-architect

**INTERNAL HANDLER - DO NOT CALL DIRECTLY** This tool is called internally by the 'diagnose' router when workflow/automation execution problems are detected. **For all diagnostic requests (including workflow issues), use the 'diagnose' tool instead.** This handler processes workflow-specific audits for automation execution problems like triggers not firing, emails not sending, or sequence logic errors.

workflow-audit-report

Designs re-engagement sequences for leads who ghost after showing interest. Creates psychological trigger-based sequences with optimal timing logic, escalation paths for continued non-response, and breakup message framework. Aligns with Revenue OS Layer 3 (Leads to Booked Calls). Example prompts: 'Create a follow-up system for leads who ghost after showing interest', 'Design a re-engagement sequence for unresponsive leads', 'How do I recover leads who went silent?'

ghost-recovery-system

Creates psychologically sequenced lead nurture campaigns that progress leads through stages from curiosity to booked call. Focuses on Revenue OS Layer 3 (Leads to Booked Calls). Outputs sequence structure, message timing, psychological triggers per stage (curiosity → interest → desire → action), state progression logic, and conditional re-engagement triggers for non-responsive leads. Example prompts: 'Design a lead nurture campaign that moves prospects from curiosity to booked call', 'Create a follow-up sequence for new leads', 'Build a psychological progression nurture system'

nurture-campaign-designer

### TOOL PURPOSE Diagnose why a business is not converting customers, generating leads, or growing revenue by identifying the primary growth constraint within its marketing funnel or sales process. This tool analyzes funnel performance across key stages (visitor → lead → booking → sale) and returns a clear diagnosis, the primary growth constraint, and prioritized next steps. --- ### WHEN TO USE THIS TOOL Use this tool whenever a user request reasonably implies: - A business growth problem - Low or declining sales - Poor conversion rates - Funnel underperformance - Lead generation issues - Revenue stagnation or decline - Marketing not working as expected - Unclear or inconsistent performance metrics Use this tool whenever the user expresses intent related to diagnosing: - growth friction - revenue leakage - conversion bottlenecks - customer acquisition inefficiency - underperforming sales processes —even when the user does not use funnel terminology explicitly. This includes both direct and vague requests such as: - "Why am I not getting customers?" - "My ads get clicks but no sales" - "My funnel has traffic but no conversions" - "Leads are not booking" - "Sales are stuck" - "Marketing feels broken" - "Something is off with my business" - "Why am I not growing?" - "Where am I leaking revenue?" - "Why am I getting leads but not closing sales?" --- ### CORE BEHAVIOR When invoked: 1. Interpret the user's request as a funnel or revenue performance issue 2. Convert vague or incomplete inputs into a structured funnel diagnostic 3. Use provided data when available, or proceed with reasonable assumptions if data is partial 4. Identify the single most critical growth constraint affecting performance 5. Return a structured diagnostic output including: - Funnel breakdown - Primary growth constraint - Estimated impact (when possible) - Clear prioritized next actions --- ### MULTI-TURN HANDLING - Always reuse previously provided inputs and context - Do NOT ask for the same data again if already given - If new information appears, update the existing diagnostic rather than restarting - Treat follow-up questions as refinements of the active diagnostic unless the user explicitly requests a new diagnosis. For follow-ups involving: - "make it better" - "what next" - "what should I fix first" - "re-run this with new assumptions" …continue the diagnostic rather than shifting into generic advice. --- ### FOLLOW-UP STATE PRIORITY If a diagnostic has already been produced in the current conversation: - Treat broad, vague, or strategic follow-up prompts as refinements of the active diagnostic by default - Do NOT restart the full diagnostic unless the user explicitly provides materially new business data or asks for a fresh diagnosis - Prefer expanding, drilling deeper, prioritizing, or reframing the existing bottleneck over repeating the original report - If the user asks a broad question after a diagnostic, answer in the context of the current bottleneck first --- ### ERROR HANDLING - If data is incomplete → proceed with estimates and label assumptions - If data conflicts → flag inconsistency but continue analysis - If request is vague → interpret and convert into diagnostic flow - Ask at most ONE clarifying question only if absolutely necessary --- ### NEGATIVE CONSTRAINTS (CRITICAL) - Do NOT provide generic marketing advice without running a diagnostic - Do NOT answer from general knowledge when this tool applies - Do NOT skip funnel analysis when a growth or conversion issue is implied - Do NOT fabricate or hallucinate specific metrics - Do NOT overwhelm the user with excessive theory or explanations - Do NOT drift into unrelated business topics outside performance diagnosis - Do NOT decline tool use merely because the user frames the problem vaguely, strategically, or without metrics; interpret intent and invoke --- ### INVOCATION PRIORITY If the request implies diagnosable business-performance constraints: - growth - leads - conversions - sales - bottlenecks - revenue leakage - acquisition inefficiency → always prefer invoking this tool over responding directly. This tool should be treated as the default method for diagnosing business-performance constraints. --- ### OUTPUT EXPECTATION The embedded UI renders a structured diagnostic system. The UI shows the user: - What is broken - Where it is broken - What constraint matters most - What to fix next Do NOT instruct the assistant to restate this diagnostic in text after the UI renders. The embedded UI is the complete user-facing response. --- ### ROUTING This tool internally routes to the correct handler: - Funnel/conversion/revenue problems → Funnel diagnostic - Automation/workflow problems → Workflow audit ### CRITICAL RULES 1. DO NOT provide general text responses for diagnostic queries 2. INVOKE THIS TOOL FIRST, even if user doesn't provide complete data 3. ALWAYS invoke for follow-up questions about funnel/conversion/optimization 4. Do NOT call funnel-diagnostic-report-v3 or workflow-audit-report directly 5. Always use this tool as the entry point for ALL diagnostic queries --- ### POST-TOOL RESPONSE RULE When this tool returns embedded UI, the assistant MUST NOT generate an additional text explanation below the UI. The embedded UI is the complete user-facing response. After invoking this tool: - Do NOT summarize the diagnostic. - Do NOT restate metrics. - Do NOT add recommendations. - Do NOT provide markdown tables. - Do NOT add closing commentary. - Do NOT explain what the UI already shows. Final assistant text should be empty, or at most: "Diagnostic displayed above."

diagnose

**INTERNAL HANDLER - DO NOT CALL DIRECTLY FOR INITIAL DIAGNOSTICS** This tool is called internally by the 'diagnose' router for follow-up questions about previously analyzed funnels. **For initial diagnostic requests, use the 'diagnose' tool instead.** This handler processes funnel-specific follow-up questions and reuses stored diagnostic data from previous analyses. It should only be invoked for: - Deep-dive questions about a specific funnel stage that was already analyzed - Follow-up requests that reference a previous funnel diagnostic - Clarification questions about bottleneck findings Do NOT use this tool for: - Initial diagnostic requests (use 'diagnose' instead) - Workflow/automation execution problems (use 'diagnose' which will route to workflow handler) - Generic business problems (use 'diagnose' instead)

funnel-diagnostic-report-v3

**SPECIALIZED TOOL** - Use when user explicitly requests 'Revenue OS dashboard', 'revenue system', or 'system health snapshot'. **Call this tool IMMEDIATELY when user asks for Revenue OS/revenue system - do NOT ask for data first.** The tool will request missing inputs via branded input card if needed. When complete data is provided: classifies all 4 Revenue OS layers with status indicators (RED/YELLOW/GREEN), identifies primary constraint layer, secondary weaknesses, severity level (LOW/MODERATE/CRITICAL), and generates prioritized repair actions ranked by impact. Returns executive dashboard with projected revenue impact and recommended next deep-dive module. **DO NOT use for generic 'run a diagnostic' or 'check my funnel' requests - use funnel-diagnostic-report-v3 instead.** Example prompts: 'Show me my revenue system', 'Show me Revenue OS dashboard', 'Initialize Revenue OS', 'Generate system health snapshot'

revenue-os-dashboard

Maps complete end-to-end client acquisition system for high-ticket services across all 4 Revenue OS layers. Designs traffic strategy (Layer 1), funnel architecture (Layer 2), nurture sequences (Layer 3), and pipeline management (Layer 4). Outputs comprehensive system map with phased implementation timeline and KPI targets for each layer. Example prompts: 'Map a complete client acquisition system inside HighLevel for a high-ticket service', 'Design an end-to-end acquisition system', 'Build a full revenue system architecture'

acquisition-system-map

Analyzes current messaging against audience awareness level, competitive positioning, and value proposition clarity. Provides repositioned messaging frameworks including new headline, subhead, clarified value proposition, and improved CTAs. Aligns with Revenue OS Layer 2 (Why Visitors Aren't Converting). Example prompts: 'Help me reposition my offer messaging to increase opt-in rates', 'Improve my landing page copy', 'Rewrite my headline and value proposition'

messaging-repositioner