Skip to main content

GoHighLevel use cases and scenarios

Updated this week

This article provides 10 ready-to-deploy scenarios with complete integration settings and agent instructions, plus 15 high-value use cases demonstrating how the Newo.ai AI Employee turns GoHighLevel into a lead generation and CRM orchestration powerhouse.

Ready-to-deploy scenarios

Each scenario includes the exact integration settings to configure in the Newo.ai Builder and the agent instruction to paste into the AI Employee's scenario configuration.

Scenario 1: Speed-to-lead closer

Goal: Convert web leads into booked appointments instantly. When a lead submits a form, the AI Employee calls within seconds, qualifies the lead, and books a meeting.

Integration settings:

Setting

Value

Calendar Selection Logic

Single (select the main sales calendar)

Pre-load Availability

True

Update Pipeline Stage

True

Select Pipeline

Select the main pipeline

Stage Selection Rules

"Appointment Booked": "If user confirms a slot"

GHL Workflow Action settings:

Set the AGENT INSTRUCTION field to:

During the session, follow *Speed-to-Lead Outbound Call* scenario.
Additional details: Job type: #{{contact.integration_1}}

πŸ—’οΈ NOTE

You can use any GoHighLevel custom fields to pass additional information to the AI Employee via the AGENT INSTRUCTION field.

Agent instruction:

**Goal:**
Quickly build trust and understand the user's intent, clearly present available
options, and confidently guide the conversation toward the next logical step β€”
ideally scheduling an appointment or arranging a follow-up with a manager.### Step 1.0: Initial greeting and intent framingGreet the user politely by **User Name**, introduce yourself using your
**Agent Name**, briefly mention the **Business Name** and its specialization,
reference the user's service request or inquiry to demonstrate awareness, and
offer to guide the user through the next steps.### Step 1.1: Intent clarification and qualificationClarify the user's intent and address any hesitation calmly and concisely,
providing only relevant information and guiding the conversation toward a
clear next step while assigning the correct qualification outcome.#### Decision logic- If the user **confirms interest in booking**, acknowledge positively
  and proceed to the **Schedule Appointment** scenario.
- If the user is **qualified but not ready to schedule**, offer a follow-up
  or manager assistance and go to the **Finish Conversation** scenario.
- If the user is **open to talking with a manager**:
  - **Working hours** β†’ Regular Transfer
  - **Non-working hours** β†’ Relaying Message to the Manager**Important:**- Never initiate booking without clear confirmation of intent.
- Do not promise discounts, pricing changes, or outcomes.### Step 1.2: Finish conversationFollow the **Finish Conversation** scenario.

Scenario 2: No-show revenue recovery

Goal: Re-book clients who missed their appointment. GoHighLevel detects a no-show status, and the AI Employee calls immediately to reschedule.

Integration settings:

Setting

Value

Calendar Selection Logic

Single

Check Existing Client

True

Enable Booking

True

Enable Availability Check

True

GHL Workflow Action settings:

Set the AGENT INSTRUCTION field to:

## Scenario 2: "Scheduling Appointment via Agent"
Additional details: Job type: #{{contact.integration_1}}"

Agent instruction:

## Scenario 2: "Scheduling Appointment via Agent"### Step 2.1: Follow the **Asking About the Services** procedure.(The calendar will be selected based on this.)### Step 2.2: Follow the **Reconfirming or Gathering ZIP code** procedure.(Optional.)### Step 2.3: Follow the **Gathering Preferred Date and Time** procedure.### Step 2.4: Follow the **Gathering Availability Information** procedure.### Step 2.5: Follow the **Reconfirming or Gathering First and Last Name**procedure.### Step 2.6: Follow the **Reconfirming or Gathering Phone Number** procedure.### Step 2.7: Follow the **Reconfirming or Gathering Email Address** procedure.### Step 2.8: Ask **if you can submit the booking now**.### Step 2.9: CRITICAL STEP β€” Submitting the booking.Say the special code-phrase: **"I'm submitting your booking right now.
Please give me a moment, and I'll get back to you shortly."**- This is a required phrase β€” without it, the booking will not go through.
- If the user changes the topic, briefly address it but remind them that the
  reservation is not yet submitted. Suggest completing the booking first.
- After clarifying any details, repeat the code-phrase: "Thanks. I'm
  submitting your booking right now. Please wait a moment, I'll get back
  to you shortly."You must **remain on this step** until you see a confirmation of successful
booking in the `<ActionsStates>` section. As soon as the confirmation
arrives, proceed to the next step.If you receive an error message in `<ActionsStates>`, apologize, inform the
user that the booking system is temporarily unavailable, and ask them to
complete the booking manually on the company's website.### Step 2.10: Proceed with the **Finish Conversation** scenario.

❗❗ IMPORTANT

The booking code-phrase ("I'm submitting your booking right now. Please give me a moment, and I'll get back to you shortly.") is required for the booking system to process the request. The AI Employee must say this exact phrase at the booking step.


Scenario 3: After-hours virtual front desk

Goal: Handle 100% of calls after business hours. The AI Employee answers FAQs, takes messages, and books appointments for the next business day.

πŸ—’οΈ NOTE

This scenario is inbound-only. No GHL Workflow Action settings are needed β€” the AI Employee handles calls as they come in, rather than being triggered by a workflow.

Integration settings:

Setting

Value

Calendar Selection Logic

Single

Save Conversation History

True

Sync Call Status

True

Enable Booking

True

Enable Availability Check

True

Enable Cancellation

True

Check Existing Client

True

Agent instruction:

Copy the full agent instruction from Scenario 2 ("Scheduling Appointment via Agent," Steps 2.1 through 2.10). No modifications are needed β€” the AI Employee follows the same step-by-step procedure to gather information, check availability, and submit the booking with the required code-phrase.


Scenario 4: Multi-service dental triage

Goal: Route emergency calls to an urgent care calendar and routine calls to a hygienist calendar based on what the caller describes.

Integration settings:

Setting

Value

Calendar Selection Logic

Name

AI Selection Instructions

"Pain/Emergency β†’ Dr. Smith Urgent; Clean/Checkup β†’ Hygienist"

Enable Booking

True

Enable Availability Check

True

Enable Cancellation

True

Check Existing Client

True

Agent instruction:

Copy the full agent instruction from Scenario 2 ("Scheduling Appointment via Agent," Steps 2.1 through 2.10). In Step 2.1, add an explicit instruction telling the AI Employee to state the duration of the service or procedure in minutes. This helps the AI Employee confirm the correct calendar match based on the caller's description.


Scenario 5: MedSpa VIP up-sell

Goal: Increase revenue per call by recognizing VIP clients and offering premium add-ons before booking.

Integration settings:

Setting

Value

Check Existing Client

True

Save Conversation History

True

Enable Booking

True

Enable Availability Check

True

Enable Cancellation

True

Agent instruction (adapts the booking flow from Scenario 2):

## Scenario 2: "Scheduling Appointment via Agent"### Step 2.1: Identification.1. Check User Profile tags.
2. If tag = 'VIP': "Welcome back, [Name]! Since you're a VIP member,
   I can add a free collagen mask to your facial today. Should I do that?"
3. If no tag: Proceed to Step 2.2.### Step 2.2: Follow the **Asking About the Services** procedure.### Step 2.3: Follow the **Gathering Preferred Date and Time** procedure.### Step 2.4: Follow the **Gathering Availability Information** procedure.### Step 2.5: Follow the **Reconfirming or Gathering Phone Number** procedure.### Step 2.6: Ask **if you can submit the booking now**.### Step 2.7: CRITICAL STEP β€” Say: \*\*"I'm submitting your booking right now.Please give me a moment, and I'll get back to you shortly."\*\*### Step 2.8: Proceed with the **Finish Conversation** scenario.

Scenario 6: HVAC seasonal tune-up blitz

Goal: Run an outbound calling campaign to fill the schedule during slow seasons by reactivating past customers for seasonal maintenance.

Integration settings:

Setting

Value

Calendar Selection Logic

Single

Update Pipeline Stage

True

Stage Selection Rules

"Appointment Booked": "If user confirms a slot"

Enable Booking

True

Enable Availability Check

True

GHL Workflow Action settings:

Set the AGENT INSTRUCTION field to:

## Scenario 2: "Scheduling Appointment via Agent.
Additional details: Last check-up: #{{contact.integration_1}}"

Agent instruction (adapts the booking flow from Scenario 2):

## Scenario 2: "Scheduling Appointment via Agent"### Step 1.1 β€” The pitch1. Say: "Hi [Name], it's time for your winter furnace check-up. We're in
   your area next week. Want to prevent any breakdowns this winter?"
2. If Yes: Go to Step 2.2.
3. If No: "No problem. I will make a note to try again next month."
   β†’ Proceed with **Finish Conversation**.### Step 2.2: Follow the **Asking About the Services** procedure.### Step 2.3: Follow the **Gathering Preferred Date and Time** procedure.### Step 2.4: Follow the **Gathering Availability Information** procedure.### Step 2.5: Follow the **Reconfirming or Gathering Phone Number** procedure.### Step 2.6: Ask **if you can submit the booking now**.### Step 2.7: CRITICAL STEP β€” Say: \*\*"I'm submitting your booking right now.Please give me a moment, and I'll get back to you shortly."\*\*### Step 2.8: Proceed with the **Finish Conversation** scenario.

Scenario 7: Failed payment recovery

Goal: Recover lost revenue by notifying customers about failed payments and providing a secure link to update their payment method.

Integration settings:

Setting

Value

Sync Call Status

True

Update Pipeline Stage

True

Stage Selection Rules

"Recovered": "If user updates payment", "Promised to Pay": "If user says they will pay later"

Agent instruction:

### General behavior guidelines- Tone: Professional, discreet, non-threatening.### Step 1.1 β€” The notification1. Say: "Hi [Name], this is a courtesy call regarding your subscription.
   It looks like the payment failed. Do you want to update your card
   details now?"### Step 1.2 β€” Resolution1. If "Yes": "Great. I will send you an SMS with a secure link right now."
   (Triggers the send SMS tool.)
2. If "I'll do it later": "Okay, please do so by Friday to avoid service
   interruption."### Step 1.3: Proceed with the **Finish Conversation** scenario.

Scenario 8: Real estate open house feedback

Goal: Call everyone who attended an open house, collect feedback, and identify hot leads ready to make an offer.

Integration settings:

Setting

Value

Update Pipeline Stage

True

Stage Selection Rules

"Hot Lead": "If user wants to make an offer", "Nurture": "If user is just looking"

Agent instruction:

### General behavior guidelines- Tone: Friendly, inquisitive, real-estate savvy.### Step 1.1 β€” Feedback1. Say: "Hi, thanks for visiting 123 Main St. What did you think
   of the kitchen?"### Step 1.2 β€” Qualification1. Ask: "Are you looking to make an offer, or just browsing?"
2. Logic:
   - Offer: "Exciting! I will connect you with the senior agent
     immediately." (Triggers the transfer call tool.)
   - Browsing: "Got it. I'll keep you updated on price changes."### Step 1.3: Proceed with the **Finish Conversation** scenario.

Scenario 9: Cleaning service duration estimator

Goal: Book the right amount of cleaning time by matching the property size to a calendar with the correct duration.

Integration settings:

Setting

Value

Calendar Selection Logic

Duration

AI Selection Instructions

"Studio/1BR β†’ 120 mins; House/3BR β†’ 240 mins"

Agent instruction:

Copy the full agent instruction from Scenario 2 ("Scheduling Appointment via Agent," Steps 2.1 through 2.10). In Step 2.1, add an explicit instruction telling the AI Employee to state the duration of the cleaning service in minutes based on the property type described by the caller (e.g., "Studio/1BR = 120 minutes, House/3BR = 240 minutes").


Scenario 10: GHL to Housecall Pro outbound call

Goal: Use GoHighLevel for lead capture and trigger outbound calls that book jobs directly into Housecall Pro.

Integration settings:

Setting

Value

Enable Booking

False (booking happens in Housecall Pro)

Enable Availability Check

False

GHL Workflow Action settings:

  1. Set up a trigger in GoHighLevel Workflows.

  2. Add the Newo AI Outbound Call action.

  3. Set the AGENT INSTRUCTION field to:

## Scenario 2: "Scheduling Appointment via Agent.
Additional details: Job type: #{{contact.integration_1}},
Zip code: #{{contact.integration_2}}"
  1. Configure the Housecall Pro integration module separately in the Builder.

Agent instruction:

Copy the full agent instruction from Scenario 2 ("Scheduling Appointment via Agent," Steps 2.1 through 2.10). The AI Employee follows the same step-by-step procedure, but the booking is created in Housecall Pro instead of GoHighLevel. Configure the Housecall Pro integration module separately in the Builder.

πŸ—’οΈ NOTE

The booking code-phrase remains required even when booking into an external system like Housecall Pro.

Next steps

After selecting a scenario and configuring its settings, continue with the following:

  • Build the workflow in GoHighLevel. Connect your scenario to a GoHighLevel trigger β€” such as a form submission, tag change, or pipeline stage update β€” using the Outbound Call or Send SMS Workflow Actions. See GoHighLevel workflow automation.

  • Verify each setting before publishing. Cross-check the integration settings from your chosen scenario against the full attribute reference to confirm dependencies and default values. See GoHighLevel settings reference.

  • Troubleshoot unexpected behavior. If the AI Employee selects the wrong calendar, skips the booking step, or does not sync call status, check the GoHighLevel FAQ for solutions to common issues.

Did this answer your question?