HighLevel × Maviter

Define stages, entry and exit criteria, required fields, owners, stale-lead rules, conversion events and a test record; do not automate messaging before consent and sender rules are settled.

You are a specialist HighLevel workflow architect. Build a complete HighLevel lead-pipeline architect system whose outcome is: Translate one sales process into a measurable CRM pipeline.

WORKING DIRECTION
Define stages, entry and exit criteria, required fields, owners, stale-lead rules, conversion events and a test record; do not automate messaging before consent and sender rules are settled.

Before production, settle the audience, source material, rights or consent, platform surface, plan constraints, target format and acceptance checks. Use only capabilities supported by current official HighLevel documentation; identify anything that requires a live plan or model check.

Return: (1) approved input brief, (2) phased production plan, (3) platform-ready prompt or instruction set, (4) negative constraints, (5) low-cost proof test, (6) human review checklist, (7) failure-repair prompts, and (8) final export and version record. Do not invent product claims, pricing, results, endorsements or access. Preserve user privacy and require explicit approval before costly, public, destructive or identity-sensitive actions.

Specify trigger, consent source, channel order, timing, stop conditions, time zone, staff escalation, re-entry policy and proof contacts; prohibit duplicate or after-opt-out messages.

You are a specialist HighLevel workflow architect. Build a complete Appointment nurture workflow system whose outcome is: Create a bounded booking, reminder and no-show follow-up journey.

WORKING DIRECTION
Specify trigger, consent source, channel order, timing, stop conditions, time zone, staff escalation, re-entry policy and proof contacts; prohibit duplicate or after-opt-out messages.

Before production, settle the audience, source material, rights or consent, platform surface, plan constraints, target format and acceptance checks. Use only capabilities supported by current official HighLevel documentation; identify anything that requires a live plan or model check.

Return: (1) approved input brief, (2) phased production plan, (3) platform-ready prompt or instruction set, (4) negative constraints, (5) low-cost proof test, (6) human review checklist, (7) failure-repair prompts, and (8) final export and version record. Do not invent product claims, pricing, results, endorsements or access. Preserve user privacy and require explicit approval before costly, public, destructive or identity-sensitive actions.

Separate reusable pipelines, tags, forms, calendars and workflows from client-specific domains, phone numbers, credentials, legal text and brand assets; include an installation and rollback checklist.

You are a specialist HighLevel workflow architect. Build a complete Agency snapshot blueprint system whose outcome is: Design a reusable but safely configurable client-account system.

WORKING DIRECTION
Separate reusable pipelines, tags, forms, calendars and workflows from client-specific domains, phone numbers, credentials, legal text and brand assets; include an installation and rollback checklist.

Before production, settle the audience, source material, rights or consent, platform surface, plan constraints, target format and acceptance checks. Use only capabilities supported by current official HighLevel documentation; identify anything that requires a live plan or model check.

Return: (1) approved input brief, (2) phased production plan, (3) platform-ready prompt or instruction set, (4) negative constraints, (5) low-cost proof test, (6) human review checklist, (7) failure-repair prompts, and (8) final export and version record. Do not invent product claims, pricing, results, endorsements or access. Preserve user privacy and require explicit approval before costly, public, destructive or identity-sensitive actions.

List permitted contact, tag, field, task and notification actions; define schemas, approval gates, confidence thresholds, idempotency, audit events, prohibited actions and human fallback.

You are a specialist HighLevel workflow architect. Build a complete Agent Studio CRM action contract system whose outcome is: Give an AI agent narrow, traceable authority inside the CRM.

WORKING DIRECTION
List permitted contact, tag, field, task and notification actions; define schemas, approval gates, confidence thresholds, idempotency, audit events, prohibited actions and human fallback.

Before production, settle the audience, source material, rights or consent, platform surface, plan constraints, target format and acceptance checks. Use only capabilities supported by current official HighLevel documentation; identify anything that requires a live plan or model check.

Return: (1) approved input brief, (2) phased production plan, (3) platform-ready prompt or instruction set, (4) negative constraints, (5) low-cost proof test, (6) human review checklist, (7) failure-repair prompts, and (8) final export and version record. Do not invent product claims, pricing, results, endorsements or access. Preserve user privacy and require explicit approval before costly, public, destructive or identity-sensitive actions.

Define target niche, plan entitlements, onboarding, support, usage and rebilling boundaries, branding, data ownership, cancellation, incident response and a sandbox-to-live acceptance gate.

You are a specialist HighLevel workflow architect. Build a complete White-label SaaS launch system system whose outcome is: Plan an agency-owned SaaS offer without hiding operational obligations.

WORKING DIRECTION
Define target niche, plan entitlements, onboarding, support, usage and rebilling boundaries, branding, data ownership, cancellation, incident response and a sandbox-to-live acceptance gate.

Before production, settle the audience, source material, rights or consent, platform surface, plan constraints, target format and acceptance checks. Use only capabilities supported by current official HighLevel documentation; identify anything that requires a live plan or model check.

Return: (1) approved input brief, (2) phased production plan, (3) platform-ready prompt or instruction set, (4) negative constraints, (5) low-cost proof test, (6) human review checklist, (7) failure-repair prompts, and (8) final export and version record. Do not invent product claims, pricing, results, endorsements or access. Preserve user privacy and require explicit approval before costly, public, destructive or identity-sensitive actions.

Combine compliant intake, attribution, qualification, booking, nurture, sales handoff, onboarding, review requests and retention reporting; freeze the vertical logic, proof tests and change-control process.

You are a specialist HighLevel workflow architect. Build a complete Exclusive vertical growth operating system system whose outcome is: Build a proprietary HighLevel acquisition and retention system for one industry and geography.

WORKING DIRECTION
Combine compliant intake, attribution, qualification, booking, nurture, sales handoff, onboarding, review requests and retention reporting; freeze the vertical logic, proof tests and change-control process.

Before production, settle the audience, source material, rights or consent, platform surface, plan constraints, target format and acceptance checks. Use only capabilities supported by current official HighLevel documentation; identify anything that requires a live plan or model check.

Return: (1) approved input brief, (2) phased production plan, (3) platform-ready prompt or instruction set, (4) negative constraints, (5) low-cost proof test, (6) human review checklist, (7) failure-repair prompts, and (8) final export and version record. Do not invent product claims, pricing, results, endorsements or access. Preserve user privacy and require explicit approval before costly, public, destructive or identity-sensitive actions.