GoHighLevel Manual Actions: Setup, Assignment, Gotchas

A Manual Action is the one workflow step in GoHighLevel that does not run itself. You drop a Manual Call, Manual SMS, or Manual Email action into a workflow, and instead of GoHighLevel sending anything, it creates a task in the Manual Actions tab and waits for a person to do the work and close it out. The catch that trips up most agencies isn’t the concept — it’s that the workflow only moves past that step when the task is marked done inside GoHighLevel. A rep who calls the lead from their cell phone, texts from their own inbox, or handles it in a completely different tool has done the job in real life and left the workflow stalled indefinitely.

This is a setup guide for getting that right: where the action lives, how assignment actually resolves when your first-choice user isn’t available, what the Manual Actions tab shows you, and how to build the escalation GoHighLevel doesn’t give you natively for a task nobody ever touches.

The three Manual Action types

There isn’t one generic “Manual Action” block — there are three, and you pick the one that matches the channel you want a human to own:

All three land in the same queue and follow the same assignment and completion rules below — the difference is only the channel and the drafting fields (a Manual SMS step, for example, has a Message field with template and custom-value support plus a test-phone-number field for previewing before anything goes live).

Where to add one

Inside a workflow, add the step the same way as any other action: open the workflow, click the + under the trigger or an existing step, and choose Manual Action to Call (for Manual Call) or the equivalent Manual SMS / Manual Email action from the action list. Give it an Action Name that describes the task itself, not the workflow — the name is what a rep sees sitting in their queue, and “Follow-up call” across five different workflows is useless when someone is triaging twenty open tasks.

Assign To: the fallback chain that quietly dumps work into Unassigned

Every Manual Action has an Assign To field under Advanced Settings, and the resolution order is fixed:

• If you name a specific user and that user has access to the contact, the task goes to them.
• If the named user does not have contact access, it falls back to the contact owner automatically — no error, no notice, it just reassigns.
• If you leave Assign To blank, it defaults straight to the contact owner.
• If neither a valid named user nor a contact owner exists on that record, the task is marked Unassigned and sits there until someone claims it manually.

The failure mode here isn’t dramatic, it’s quiet: contacts imported without an owner, or a named user whose permissions changed after the workflow was built, land in Unassigned with nobody watching that view by default. If you route any real volume through Manual Actions, put someone’s job description on checking the Unassigned filter, not just the Assigned one.

The gotcha: completion happens in the tab, not in reality

This is the detail that costs agencies the most confusion, and it’s easy to miss because nothing in the workflow builder calls it out. A workflow parked on a Manual Action step does not evaluate whether the underlying call, text, or email actually happened. It evaluates one thing only: whether the task was explicitly closed out inside the Manual Actions tab. Dial the contact from your personal phone, and the task sits open. Reply to them from your own Gmail, same result. The task has to be opened from the tab and marked complete there for anything downstream — a tag, a pipeline move, a follow-up SMS three steps later — to fire.

In practice this means two things for how you design the workflow: train reps that “I called them” and “I closed the task” are two separate actions, and never build a Manual Action into a workflow whose downstream steps are time-sensitive (like a same-day appointment reminder) unless you trust the queue will actually get worked that day.

The Manual Actions tab: what you’re monitoring

Everything created by these three action types lands in Conversations > Manual Actions, filterable by assigned user, team, and status. The tab uses four statuses:

Treat this tab as a work queue an ops manager reviews on a schedule, the same way you’d review an open-tickets view in a help desk. Nothing about it self-manages.

Missed doesn’t page anyone — you have to build that

A task can sit in Missed indefinitely without triggering anything. There is currently no native workflow trigger that fires off a Manual Action going overdue — HighLevel’s own idea board still lists SLA-based, overdue-triggered automation as an open feature request, not a shipped one. If a rep goes on vacation with fifteen unclaimed Manual SMS tasks, nothing in GoHighLevel will tell you unless a human looks.

The practical workaround: don’t rely on the Manual Action step to signal its own delay. Run a parallel branch off the same trigger that starts a Wait step for whatever window counts as overdue for that task (four hours for a hot lead, one business day for a lower-priority one), independent of whether the Manual Action itself has been completed. When that Wait elapses, fire an Internal Notification action to the assigned user’s manager or a team channel. This doesn’t check the task’s status directly, so word the notification as “a task assigned around this time may still be open” rather than asserting it’s still pending — but it converts an invisible failure mode into a visible one, which is the whole point.

A working pattern: gate the first call on a human, automate everything after

The clearest use case for Manual Actions is a high-ticket or compliance-sensitive first touch, where you want automation to queue the work and a person to own the actual conversation:

1. Trigger the workflow on the event that qualifies the lead (a tag added, an opportunity created in a specific pipeline stage, a form submission above a lead-score threshold).
2. Add a Manual Call action assigned to a specific closer, with the Action Name naming the lead type, not the workflow.
3. Branch downstream steps so they only run after that step is marked Completed — a nurture sequence, a pipeline stage move, a follow-up SMS.
4. In parallel, add the Wait-plus-Internal-Notification branch above so an overdue task surfaces to a manager instead of aging silently.

This keeps the parts of the funnel that should be automated — reminders, nurture, tagging — fully automated, while forcing a human decision at the one point where your close rate actually depends on a real conversation, and it gives you a paper trail (the Completed timestamp) for anything where you need to prove a human, not a bot, handled the contact.

When a Manual Action is the wrong tool

Not every high-touch step belongs here. A Manual Action is a queue item for a person to act on outside the automation entirely — it isn’t a review-and-approve gate, and it isn’t a way to slow down a sequence without actually needing a human. If what you want is a pause before a fully automated message goes out (a cooling-off period, a business-hours restriction), that’s a Wait step or the workflow’s Time Window setting, not a Manual Action; adding a Manual Call step there just creates a task nobody expects to work. And if the contact might legitimately re-enter this same workflow later — say, they go cold and come back through the same trigger — remember that a stuck, incomplete Manual Action from the first pass does not resolve itself just because the contact re-enters; check your Allow Re-Entry and active-contact settings so a second pass doesn’t stack a duplicate task on top of one still sitting in someone’s queue.

Used narrowly — the one or two points in a funnel where a human’s judgment, voice, or compliance sign-off is the actual product, like the first call on a five-figure deal or a message that has to clear a regulated-industry review — Manual Actions give you a documented, assignable checkpoint without giving up the automation around it. Used broadly, as a default for anything that feels like it deserves a personal touch, they turn into an unmonitored task list that quietly bleeds leads.

Frequently Asked Questions

Does a Manual Action stop the whole workflow until someone completes it?

Yes, for that contact. Any steps placed after the Manual Action in the same branch wait until the task is marked Completed inside the Manual Actions tab. Steps in a separate parallel branch off the same trigger run on their own schedule and are not blocked by it.

What happens if the assigned user leaves the team or loses access to the contact?

GoHighLevel falls back automatically: it first tries the contact owner, and if there's no valid contact owner either, the task is marked Unassigned. It does not notify anyone that the reassignment happened, so it's worth periodically checking the Unassigned filter in the Manual Actions tab.

Can I set a deadline that automatically escalates a missed Manual Action?

Not natively. The tab will mark a task Missed once it passes its expected window, but no built-in trigger fires because of that status change — it's an open feature request on HighLevel's own idea board. Build the escalation yourself with a parallel Wait step and an Internal Notification action off the same trigger.

Is there a Manual Action for tasks other than calls, SMS, and email?

The three channel-specific actions — Manual Call, Manual SMS, and Manual Email — are what create entries in the Manual Actions tab. If you need a generic to-do unrelated to contacting the lead, that's a workflow Task action instead, which lives in the Tasks view rather than Manual Actions.

We build your GoHighLevel account for you

CRM, pipelines, funnels, SMS and automation — configured for your business, not left for you to figure out.

• Setup (one-time)$850
• Ongoing (per month)$38.80

Get my free setup quote

No obligation quote · reply within 1 business day

This site is independently operated and is not officially affiliated with, endorsed by, or sponsored by HighLevel LLC. We do not receive referral commissions — this is our own flat-fee implementation service.