GoHighLevel Manual Actions in Workflows (2026)

By Dr Priya Jaganathan, GoHighLevel Certified Admin · HL Growth Partner, Australia · Updated 18 September 2026 · 8 min read

GoHighLevel manual actions are the human-in-the-loop steps inside a workflow. Instead of firing a message, the workflow stops, creates a task, and waits for a person to pick up the phone or write the text themselves.

They are also the most quietly broken part of the automation builder. Half the accounts I audit have manual actions sitting in a queue nobody has opened in months, with contacts frozen mid-workflow behind them. This post covers how HighLevel manual actions in workflows actually behave, who they get assigned to, and how to run a queue reps genuinely clear.

What GoHighLevel manual actions actually do inside a workflow

A normal Send SMS or Send Email action executes and the contact moves on. A manual action writes a task into a queue instead, and holds the contact at that step until a human deals with it. HighLevel's docs describe Manual Call as creating a call task for a user, and Manual SMS as generating a task the user finalises and sends themselves.

The two action types you actually get

People often ask about a Manual Email action. There isn't one. HighLevel's complete workflow action list (updated 3 June 2026) documents Manual Call and Manual SMS under Communication Actions, and the queue only filters by task type Call or SMS.

For a human-written email you use the Add Task action or an internal notification instead.

The Manual SMS step is more capable than most people realise. You can pre-load an SMS template, drop in custom values, embed trigger links, attach a file by URL, and send a test message first. The rep gets a drafted message to edit, not a blank box.

The rule that breaks most builds

A manual action only completes when the task is cleared from the Manual Actions tab. HighLevel's Manual Call documentation is explicit: calling the contact from the Contacts page or anywhere else in the platform will not complete the task or move the workflow forward.

This is the most common cause of "my workflow stopped working" tickets that turn out not to be bugs. The rep did the work, logged it on the contact record, never touched the queue — so the contact is still parked and everything downstream never runs.

The execution log says so plainly: it records "Manual Call added to the manual queue" and nothing after it. I cover reading those logs properly in the workflow execution log troubleshooting guide.

How the Manual Actions queue works for a sales rep

A rep opens Conversations → Manual Actions. HighLevel's refreshed HiRise layout gives them a collapsible filter sidebar and a task table showing contact name, phone, task type and date added.

They click Let's Start and work the queue one record at a time, logging the call outcome or SMS reply in the side panel, then marking the task Complete, Skip or Re-queue. Pressing Enter starts the next task, which matters when someone is doing fifty dials in a sitting.

Filters, statuses and shareable queues

Four filters do the real work: workflow source, task type (Call or SMS), status and assignee. Status options are Yet to Call, Completed and Skipped.

The URL-based filters are the sleeper feature for managers. Filter selections are written into the page URL, so you can build a view like "Manual Call tasks from the quote follow-up workflow, assigned to Sam, still Yet to Call", copy the address bar and paste it into team chat.

That is how you turn a queue into a shift — each rep gets a bookmarked link that is their list, not everybody's list.

Assigning manual actions: specific user, contact owner or round-robin

Every manual action has an Assign To field under Advanced Settings. Leave it empty and the task goes to the contact owner; pick a user and that user gets it instead. HighLevel documents the fallback logic precisely, and it is worth knowing because the failure is silent.

Unassigned tasks are where queues go to die. Nobody's filtered view includes them, so nobody sees them. If your reps are restricted to assigned contacts only, a permissions gap will quietly reroute or orphan tasks — which is why I treat sub-account permissions and user roles as part of the manual action build, not a separate job.

Round-robin is set upstream, not in the manual action

The manual action itself takes one user or the contact owner — there is no round-robin selector inside the step.

So you do the distribution first: an Assign User action earlier in the workflow, with multiple users selected and Split Traffic set to distribute equally. Every downstream manual action then inherits that owner automatically — one assignment decision, many manual steps, and reassigning the contact reassigns the whole trail.

Manual actions, wait steps, if/else branches and re-entry

Because a manual action is a blocking step, it changes how everything around it behaves.

• Wait steps after a manual action are measured from when the task is cleared, not from when it was created. A rep who clears Monday's queue on Thursday shifts the entire downstream sequence by three days.
• If/else branches placed after a manual action can only read data that exists once the task is done. If the branch checks a disposition custom field, someone has to actually write to that field.
• Wait steps before a manual action are your friend: they stop the queue filling at 11pm and let you release tasks at the start of a shift.
• Re-entry is the real hazard. If a workflow allows contacts to re-enter, a lead who fills in two forms can generate two identical call tasks sitting side by side in the queue.

For anything customer-facing I set re-entry deliberately and gate the manual action behind a tag or custom field check, so the workflow can only create one open task per contact at a time.

Manual action vs automated send vs Task vs internal notification

These four get used interchangeably and they are not interchangeable at all. The deciding question is simple: does the workflow need to wait?

The rule I give teams: use a manual action when the workflow must not continue without a human, and a Task or notification when the work matters but the sequence should keep running. Mixing those up is how you either freeze a pipeline or let a lead get automated at while nobody has called them.

The Add Task action also works without a contact attached, which makes it the right tool for internal jobs a manual action can't express.

When a manual action beats automation

Automation wins on volume. Manual actions win when the value per conversation is high enough that a template would cost you the deal.

• High-value leads. Enquiries above a deal-size threshold go to a named rep as a Manual Call, not into a nurture sequence.
• Quote follow-up. The second and third touch after a quote should reference the actual numbers. A rep reading the opportunity before dialling converts better than any drip.
• Reactivation of old enquiries. Cold lists respond to a human. I pair a light automated opener with a Manual Call step for anyone who so much as opens it — the approach I use in a database reactivation campaign for cold leads.
• Complaint handling. Never automate a reply to an unhappy customer. Route it to a Manual Call and let the workflow wait.
• Compliance-sensitive messages. Anything where wording carries risk gets human eyes before it sends.

The compliance argument for manual SMS in Australia

Under the Spam Act 2003, commercial electronic messages need consent, accurate sender identification, and a functional unsubscribe — and ACMA's guidance on avoiding spam requires that the unsubscribe facility and your sender details remain valid for at least 30 days after sending.

ACMA reported that businesses paid more than $20 million in spam penalties in the 18 months to October 2024. Where consent is inferred rather than express, a manual action is cheap insurance: the rep sees the contact's history before the message leaves, and the LeadConnector or Twilio send is a deliberate act rather than a bulk one.

Building a rep's daily call queue out of a workflow

The build is less about clever steps and more about discipline. The pattern I use:

• One workflow per queue purpose — new enquiry calls, quote chasers, reactivation — so the workflow source filter is actually meaningful.
• Assign User with equal split traffic at the top, so ownership is decided before any manual step exists.
• A wait step that releases tasks at the start of the shift rather than overnight.
• The Manual Call step named for what the rep is meant to say, not "Manual Call 1". "Call: quote sent 48h ago" reads properly in a queue.
• An if/else immediately after, branching on a call-outcome custom field the rep fills in.
• A tag on completion, so smart lists can show you who has and hasn't been reached.

For genuinely high-volume outbound, don't build a huge manual queue at all — that is what a GoHighLevel power dialer setup is for. Manual actions are for considered calls; the dialler is for throughput.

Reporting on whether reps actually cleared the queue

There is no dedicated manual actions dashboard, so you build the reporting out of the parts that exist.

The fastest health check is a saved URL filter set to status Yet to Call with no assignee filter. If that list is longer on Friday than it was on Monday, the queue is losing. Then filter by assignee to see whose column is growing.

Watch the Skipped count as closely as the Completed count. A rep clearing forty tasks a day by skipping thirty of them looks productive and performs terribly, and only the status split reveals it.

Beyond the queue, the workflow execution log and enrolment history show where contacts stalled and why they exited. Pair that with pipeline movement in your opportunities to check that cleared tasks produce stage changes rather than just ticks.

Common mistakes to avoid

• Nobody owns the queue. This is the failure mode. Manual actions accumulate silently because no dashboard nags anyone, and hundreds of contacts sit frozen behind them. Assign a named owner and a daily zero-out ritual, or don't use manual actions.
• Assuming the call completes the task. The workflow only advances when the task is cleared from the Manual Actions tab. Train this explicitly — it is not intuitive.
• Leaving Assign To empty on contacts with no owner. The task becomes Unassigned and disappears from every rep's filtered view.
• Putting a manual action in front of something time-critical. Appointment reminders, receipts and confirmations should never sit behind a human step.
• Allowing unlimited re-entry. Duplicate enquiries create duplicate call tasks, and reps stop trusting the queue.
• Using a manual action when a Task or internal notification was the right tool. If the sequence shouldn't pause, don't pause it.

If you want your manual action queues designed, assigned and reported on properly — so reps actually clear them and no contact sits frozen mid-workflow — book a strategy call with the HL Growth Partner team.

Book Your Strategy Call →

Frequently asked questions

What are GoHighLevel manual actions?

Manual actions are workflow steps that create a task for a human instead of sending a message automatically. HighLevel offers Manual Call and Manual SMS, both documented under Communication Actions in the workflow builder. The task appears in Conversations → Manual Actions and the contact stays parked at that step until someone clears it.

Where do I find the Manual Actions queue in HighLevel?

From the left navigation, go to Conversations → Manual Actions. HighLevel's documentation confirms the page is available on both web and mobile. Click Let's Start to work through tasks, logging outcomes in the side panel and marking each one Complete, Skip or Re-queue.

Does a manual call action complete if I ring the contact from the contact record?

No. HighLevel's Manual Call documentation states that calling the contact from the Contacts page or any other area will not complete the task or move the workflow forward. The action only progresses when the task is explicitly cleared from the Conversations → Manual Actions tab. This is the most common reason a workflow appears to have stopped.

Can I assign a manual action to a specific user instead of the contact owner?

Yes, using the Assign To field under Advanced Settings. If the selected user has contact access the task goes to them; if they don't, it falls back to the contact owner. With no user selected it defaults to the contact owner, and if neither is available the task is marked Unassigned.

Is there a Manual Email action in GoHighLevel workflows?

No. HighLevel's complete workflow action list documents Manual Call and Manual SMS only, and the Manual Actions queue filters by task type Call or SMS. For a human-written email, use the Add Task action to create a to-do against the contact, or an internal notification to alert the right user.

What is the difference between a manual action and a Task in GoHighLevel?

A manual action blocks the workflow until it is cleared from the Manual Actions queue; a Task does not. Use a manual action when the next workflow step depends on the outcome of a human conversation. Use a Task when the work matters but the sequence should keep running — and note that the Add Task action can also create contact-less internal tasks.

How do I stop manual actions from piling up unnoticed?

Give the queue a named owner and a daily clear-down routine, because nothing in the platform will chase it for you. Build a saved URL filter for status Yet to Call and check it daily, since HighLevel stores filter selections in the page URL. Watch the Skipped count alongside Completed, and use Bulk Actions to reassign any backlog before it becomes unrecoverable.

Related Articles on HL Growth Partner

Workflow build and hygiene

• Premium workflow actions and what they cost
• Workflow folders and naming conventions
• AI workflows in GoHighLevel

Sales follow-up that needs a human

• Upsell workflow after job completion
• Referral request workflow setup
• Training Conversation AI to book appointments

Segmentation and reporting

• Tag strategy and structure
• Attribution reporting and lead sources
• Trigger links for tracking and automation

Source: HighLevel Support Portal — Workflow Action: Manual Call.