How to Figure Out Who to Call Next in GoHighLevel

The home services industry converts calls at 46 percent on average, but the gap between top-quartile and bottom-quartile contractors is mostly about which calls get prioritized, not which calls get made. [Invoca 2025 home services report]

GoHighLevel does a lot of things well. Telling a contractor "this is the call that matters most right now" is not one of them. The platform was built for marketing agencies running drip sequences, not for a CSR with 90 minutes between dispatch calls trying to figure out which 8 leads to call back.

The "who do I call next" question lives at the intersection of pipeline stage, last contact date, deal value, and source intent. GHL holds parts of that. Email and calendar hold the rest. This guide covers how to build the closest thing to a callback queue inside GHL, then where you'll need to step outside.

What GHL doesn't have (yet)

There is no "Next Call" view in GHL. The closest things are:

• Conversations inbox filtered by unread. Tells you who messaged you, not who you should call.
• Pipeline view sorted by last activity. Tells you what's stale, not what's hot.
• Smart List of opportunities by stage. Tells you the cohort, not the priority.

Owners and CSRs end up tab-switching between three or four views, plus their email, plus voicemail, plus the dispatch calendar, to figure out who to dial. That is the workflow this post is going to fix.

Step 1: Build the "Next Call" Smart List set

The trick is not one Smart List. It's five Smart Lists, each answering a different "why call?" question, and a daily habit of working them in order. [GHL Smart Lists guide]

Build these in Contacts → Smart Lists → New:

1. Hot replies (last 24h). Replied to an outbound SMS or email in the last 24 hours, opportunity stage is not "Won" or "Lost"
2. Untouched leads (last 4h). Contact created in last 4 hours, no outbound message yet, no call attempt
3. Stalled estimates worth calling. Stage = "Estimate Sent", last activity > 5 days, opportunity value > $1,500
4. Missed call no text-back. Inbound missed call in last 24 hours where the auto text-back workflow did not fire
5. Reactivation candidates ready. Tag status-active-customer, last service > 12 months, no opt-out tag. The full GHL-specific motion lives in revive cold leads in GoHighLevel.

Save each list. Pin them to the sidebar.

The order is the priority. Hot replies first because they're already engaged. Then untouched because you're losing them by the minute. Then stalled estimates because the money is already on the table. Then missed-call gaps because something broke. Then reactivation as the fill-in work between dispatch.

Text Clint: "Who should I call this morning across hot replies, untouched leads, and stalled estimates over $1,500?"

Step 2: Filter the Conversations inbox to "callback queue"

Conversations is the unified inbox: SMS, email, FB DM, GMB chat, voice. [HighLevel unified Conversations]

Set up these filtered views:

• Unread, unassigned, last 48h. Anyone who reached out and nobody has handled
• Snoozed, due today. Threads you punted earlier, now reappearing
• Tag "needs-callback". Manual flag for any thread where the team agreed "we're calling, not texting"

The snooze workflow is the one most contractors don't use enough. When a customer says "call me Tuesday," snooze the thread to Tuesday 9 a.m. instead of leaving it open. Tuesday 9 a.m. it pops back to the top of your inbox.

Step 3: Pipeline-based callback scoring

Inside the Lead pipeline, sort by:

• Last activity ascending (oldest first) within the "Estimate Sent" stage. The oldest stalled deals get priority.
• Opportunity value descending within the "Appointment Set" stage. The biggest upcoming jobs get the personal pre-call.

The pattern: every stage of the pipeline has a different "who do I call" sort. Estimate Sent sorts by staleness. Appointment Set sorts by value. New Lead sorts by source intent (Google LSA > Meta > organic).

The Pipeline dashboard widget shows pipeline value, opportunities count, conversion rate, funnel chart, and stage distribution out of the box. [GHL pipeline dashboard widget] The "who to call" sort happens inside the pipeline detail view.

Step 4: Use Tags as a callback intent layer

Tags add the "why" on top of the "what." A workable callback tag set:

• callback-hot: they asked us to call, snoozed in Conversations
• callback-quote-pending: quote is out, not yet replied
• callback-membership-renewal: service contract due in next 30 days
• callback-reactivation: past customer, ready for a check-in
• callback-vip: historical lifetime value > $10K, always answer their calls first

Workflows can apply these tags automatically. For example: when an opportunity moves to "Estimate Sent," apply callback-quote-pending. When a tagged customer's renewal date is 30 days out, apply callback-membership-renewal. We covered the wider tagging philosophy in 7 essential CRM tags every contractor should use.

The Smart List for "who do I call next" then becomes: any contact with any callback-* tag, sorted by tag priority and last activity.

Text Clint: "Show me GHL contacts tagged callback-vip with last contact over 30 days, with the reason for the call."

Step 5: Workflow-based call task creation

GHL Workflows can create tasks. Tasks land in the user's task list. The task list is the closest thing GHL has to a structured "to-do" surface.

Build a workflow:

• Trigger: Opportunity stage changes to "Estimate Sent"
• Action 1: Wait 5 days
• Action 2: If no reply received, create task assigned to the opportunity owner: "Call [Contact Name] about [Service]"
• Action 3: Apply tag callback-quote-pending

Now your CSR's task list shows callbacks they need to make today, with the contact and reason. [GHL workflows getting started]

The trap: GHL tasks don't have great mobile UX, and the task list lives in a different module than the Conversations inbox. People miss tasks. The workaround most contractors land on is firing an SMS to the rep when a task is created, with the contact name and a "Reply DONE when called" prompt.

Step 6: Missed call follow-up as a callback driver

The biggest leak in most contractor pipelines is the missed inbound call where nothing happens after.

Set up a Missed Call Text-Back workflow: inbound call goes unanswered → SMS within 60 seconds asking what they need. [Automate the Journey GHL missed call text back]

That auto-text starts a conversation. The follow-up call has to happen too, because some customers don't text. Build a parallel workflow that creates a "Return Missed Call" task assigned to the on-call CSR if the inbound call wasn't answered AND the auto-text gets no reply within 30 minutes.

Put the resulting tasks into your "callback queue" Smart List. We compared the build-vs-buy of missed call follow-up in AI missed call follow-up agent for contractors.

Step 7: The Conversation AI Auto Follow-Up trick

Conversation AI in GHL has an Auto Follow-Up feature that lets the bot send timely outbound messages to contacts who have gone inactive, asked for a follow-up, or stopped responding. [GHL Conversation AI auto follow-up]

Configured well, this is what removes the "low value" callbacks from your queue. The AI handles the gentle nudge. Your CSR only gets escalated when the AI has tried 2 or 3 times and the contact replied with intent or never replied at all.

The result: your callback queue gets shorter and higher-quality. You stop calling people who would rather text. You only get on the phone when the AI couldn't close the loop.

Step 8: Where GHL falls short

Honest list:

• GHL doesn't see your email outside GHL. If a lead emailed you from a personal address that's not in GHL, GHL doesn't know. You assume they ghosted. Really they're waiting on a reply you never sent.
• GHL doesn't see your phone outside GHL. If a tech took a call on a personal cell, GHL has no record. The lead's "last contact" timestamp lies.
• GHL doesn't see your calendar. A callback for 9 a.m. tomorrow is meaningless if you're already booked. GHL Tasks and the Calendar module live in parallel, not integrated by default.
• No multi-source priority scoring. Real callback priority is "this lead replied to your SMS, then opened your email, then visited your pricing page." GHL has pieces of all three but no single score.

These are the gaps Clint exists to close. We covered the wider problem in questions no dashboard will answer.

Step 9: How Clint actually answers "who do I call next"

Clint connects to GoHighLevel, Gmail, Google Calendar, and CallRail. The owner texts a question. Clint reads the data live across all four and answers.

• Text Clint: "Who should I call this morning?"

  Clint pulls hot SMS replies from GHL, unanswered emails from Gmail, missed calls from CallRail, calendar gaps where you have time, and ranks them by deal value, source intent, and time since last contact. Sends back a 5-name shortlist with the reason for each call.

• Text Clint: "What did Sarah Johnson last reply, and is there a quote out?"

  Clint reads the Conversations thread in GHL, the email chain with her in Gmail, the call log in CallRail, and the open opportunity. Answers with the full context.

• Text Clint: "Move my 11 a.m. and put me on calls. Build me a 90-minute callback queue."

  Clint pulls the priority list and texts you a sequenced 90 minutes worth of calls.

This is the field-ops layer that GHL was never designed for. We compared similar tools in Hatch vs Podium vs AI contractor texting.

Sources

• Smart Lists in GoHighLevel (HighLevel Support)
• Getting Started with the New Conversations Experience (HighLevel Support)
• Auto Follow-Up Action in HighLevel's Conversation AI (HighLevel Support)
• Pipeline Dashboard Widget (HighLevel Support)
• GoHighLevel Missed Call Text Back Setup (Automate the Journey)
• Invoca 2025 Home Services Call Conversion Benchmarks
• GoHighLevel Workflows Getting Started (HighLevel Support)