Every forgotten call disposition is a sale leaking to a competitor. GoHighLevel now lets a rep close out a call with one click — and that click becomes a GoHighLevel AI employee that fires the tag, the pipeline move, the follow-up text, even an AI callback. Set it up once and your post-call admin runs itself. Here’s how we build it.
This post distills Nuno Tavares’s video, The GoHighLevel Call Automation Setup Every Agency Needs.
What’s a call disposition in GoHighLevel?
A call disposition is the human’s verdict on a call — “not interested,” “requested appointment,” “sold,” “wrong number.” It’s different from a call status, which is the technical result the phone system records on its own: answered, busy, voicemail, hung up.
Here’s the diff. The status is what the line did. The disposition is what you decided to do next. GoHighLevel now lets a rep pick that disposition from a one-click dropdown right after a call in the auto-dialer — and each choice can kick off its own automation in the background.
That’s the whole trick. The dropdown is free and built into the platform. The value is the system you wire behind it.
Why does forgotten follow-up quietly kill your sales?
Picture a rep 20 calls into the day. After each one they’re supposed to tag the contact, move them in the pipeline, and send a follow-up text or schedule a task. The reality: about 80% of the time, it doesn’t happen. There’s no time.
Every skipped follow-up is a lead that drifts to whoever calls them back first. And the manual version isn’t free either:
- Add a tag: ~15 seconds
- Create the follow-up task by hand
- Send the “just following up” text by hand
- Move them in the pipeline and add notes
Add it up and you’re looking at about 90 seconds of admin after every single call. Across 50 calls a day, that’s over an hour a rep spends clicking instead of selling — assuming they remember to do it at all. Most don’t.
“After 20 calls, the last thing I want to do is go into the system and update every single one. If I feel like that, imagine what your salespeople feel like.”
One-click dispositions cut that 90 seconds down to about two. That’s the point of building it.
How to build one-click call dispositions in GoHighLevel
The setup has three parts: create the dispositions, build the automation behind each one, then load your list into the auto-dialer. We’ll walk each.
Step 1: Create the dispositions
In GoHighLevel, go to Settings → Phone System → Voice → Custom Dispositions. You’ll see a few defaults already there. Add your own with the Add Disposition button, and rename any you don’t like with the edit pencil.
At this stage the name is only a name — the actions come later. A solid starter set:
- Requested appointment
- Follow-up / needs info
- Call back requested
- Not interested
- Already a customer
- Wrong number / wrong person
- Do not call
Keep it to five to eight options. More than that and your reps freeze at the end of a call trying to pick the right one. Simple wins.
Step 2: Build the automation behind each disposition
This is the part that turns a label into a GoHighLevel AI employee. In Automations, make a folder called “Call Dispositions” so they don’t scatter. Each disposition gets its own workflow, and they all follow the same shape — learn one and you can build the rest.
The trigger is always the same: add a Call Details trigger, add a filter on Custom Disposition, and set it to the disposition you’re wiring. That’s the domino that starts everything else.
Then add the actions you’d normally do by hand. A few examples straight from the video:
- Not interested → move the opportunity to “Not a fit,” add a “not interested” tag, and (optionally) flag Do Not Contact so they don’t get dialed again.
- Requested appointment → send an SMS like “Hi [first name], I see you asked for a follow-up. Mind if my AI calls to book it?”, then hand off to Conversational AI to actually book the slot.
- Sold on call → tag them as a customer, drop them into your onboarding pipeline, and fire a welcome email so onboarding starts before the rep hangs up.
Use square-bracket merge fields like [first name] in your messages — GoHighLevel fills them in per contact. Publish each workflow when it’s done.
Step 3: Load contacts into the auto-dialer
Dispositions live in the auto-dialer, so you need contacts in it. Two things make this smooth:
First, build a tiny workflow — call it “Uploading Call List” — whose only job is a Manual Call → Add to Auto-Dialer action. Leave its trigger empty so you can push contacts straight in, or add a “dialer” tag trigger so anyone who gets that tag lands in the queue too.
Second, import your list. It has to be a CSV with at least first name, last name, email, and phone. On the import screen, map the fields (GoHighLevel usually auto-maps them) and send the contacts directly into that “Uploading Call List” workflow. They’ll queue up in the dialer, waiting to be called.
One quiet, useful move: at the end of a “not interested” or “call back later” workflow, add another Manual Call → Add to Auto-Dialer action. Now leads you didn’t close automatically re-queue for a future round instead of dying in the CRM.
How does a disposition become an AI employee?
The “requested appointment” flow is where this stops being admin and starts being an actual team member. Instead of a rep chasing the booking, the disposition sends the text, and Conversational AI takes the reply, confirms the customer wants a call, and hands off to an outbound voice bot to book the appointment — or just drops your calendar link if you’d rather keep it simple.
That’s the same pattern behind AI that answers the phone and follows up on its own: a human makes the judgment call in two seconds, and the system does the 90 seconds of work behind it. The rep stays on the phones. The follow-up never gets skipped.
The honest gotcha
Be careful with the Do Not Contact toggle. It’s tempting to slap it on every “not interested” disposition — but once it’s on, you can’t reach that contact again on that channel, even if they come back into your queue warm weeks or months later. If your sales cycle has any re-engagement in it, leave DND off “not interested” and reserve it for genuine “do not call” requests. One wrong default here can wall off leads you’d have closed.
Frequently asked questions
What’s the difference between a call status and a call disposition?
A call status is the technical outcome the system logs automatically — answered, busy, voicemail, hung up. A call disposition is the human’s decision about what happens next — not interested, follow-up, sold. In GoHighLevel, the disposition is what triggers your back-end automations.
Do I need the auto-dialer to use dispositions?
The one-click disposition dropdown shown here lives in the GoHighLevel auto-dialer, so that’s where reps pick it after each call. The workflows behind each disposition are standard automations, so the automation logic works regardless — but the fast, one-click experience is an auto-dialer feature.
How many dispositions should I create?
Five to eight. Enough to cover your real call outcomes, few enough that a rep can pick the right one instantly at the end of a call. Too many options and people stall or guess, which defeats the purpose.
What do I need to actually place the calls?
An A2P-registered phone number. Once that’s set, go to Conversations → Manual Actions, and your queued contacts appear with the disposition dropdown ready. Pick a disposition, hit next, and it dials the following contact automatically.
Get it built right the first time
The disposition dropdown is the easy 10%. The value is the automation system underneath it — mapped to your actual pipeline, your messaging, and your follow-up cadence. Wire it wrong and you either annoy leads or lose them to a stray DND toggle.
That’s the work we do every day. We’re 12x HighLevel Award winners with 1,000+ builds shipped, and we install this kind of call-follow-up system so your reps sell and the CRM handles the rest — backed by four written guarantees: zero downtime, on-time delivery, a 14-day money-back window, and no long-term contract.
Want your sales calls to disposition themselves? Book a scope call and we’ll map it to your setup.