GoHighLevel manual actions are workflow-generated tasks that require a person to make a decision or complete a piece of work. They are useful when automation should pause for human judgment, such as reviewing a lead, making a call, sending a tailored message, or approving the next step.
In HiRise Design, these actions provide a visible queue of work that can be assigned, filtered, scheduled, completed, or reviewed after its due time. The important question is not simply how to create more tasks. It is whether each manual action represents a clear business decision, has one visible owner, and contains enough context to be completed correctly.
This guide explains the lifecycle of a manual action, how to use the task board, how to handle pending and missed work, and how to design manual steps that improve operations instead of creating another unmanaged inbox.
What is a manual action in GoHighLevel?
A manual action is a task-style item created by a workflow or related process that requires a user to do something. Unlike an automated action, it does not complete the work on its own. It places the next step in front of a person and records whether that step is still pending, has been missed, or is complete.
Typical examples include reviewing a new enquiry before contacting the person, calling a qualified lead, sending a personal follow-up, checking a service request, or approving a record before it moves forward. The task is normally associated with a contact or other CRM record, so the user can work from relevant context rather than relying on memory.
A manual action should represent a necessary human decision or action, not a vague reminder that a workflow could not define properly.
This distinction matters. If a workflow creates tasks without a clear reason, the board fills with activity but does not improve execution. A useful manual action tells the owner what outcome is expected, when it matters, and what should happen afterward.
The manual action lifecycle
Manual actions are easiest to manage when the team treats them as a controlled lifecycle rather than as isolated tasks. The usual sequence is creation, ownership, execution, status update, and review.
This sequence creates an operational control loop. If actions are created but not assigned, ownership is missing. If they are assigned but not completed, the issue may be capacity, priority, timing, or unclear instructions. If completed actions are never reviewed, the organization loses an opportunity to improve the workflow.
What the main manual action statuses mean
Status labels are useful only when they describe a meaningful business state. The following interpretations provide a practical way to understand the common HiRise Design views.
- No Task: No open manual action is present for the selected record, filter, or view. This does not necessarily mean the broader process is complete.
- Unassigned, pending: An action exists, but no individual has accepted responsibility for completing it. This is an ownership gap and should not be treated as a normal queue state.
- Assigned, pending: The action has an owner but still requires work. It should contain enough information for that person to act without reconstructing the process.
- Missed: The action was not completed within the relevant time window. A missed item is a signal to investigate, not simply a task to hide.
- Completed: The required action has been recorded as finished. Completion should mean the defined outcome occurred, not merely that someone opened the task.
A status should answer a management question. Pending asks what still needs attention, unassigned asks where ownership is missing, and missed asks where the process failed to meet its timing requirement.
How to work through the HiRise Design board
The task board is most useful when each user starts with a deliberate view of their work instead of scanning every available item. Select the relevant workspace or pipeline, then narrow the view by owner, status, and timing.
- Start with ownership. Filter for actions assigned to you or your team. Review unassigned work separately so it cannot disappear among owned tasks.
- Separate pending from missed. Pending actions require execution. Missed actions require both a recovery decision and a process review.
- Check the timeline. Look for actions due soon and for days where several tasks accumulate. A workload spike may indicate poor distribution or a workflow that creates actions too early.
- Open the record before acting. Confirm the contact, instructions, previous communication, and expected outcome before making a call or sending a message.
- Complete the work, then update the status. Do not mark an action complete simply to clear the board. The status is part of the operational record.
Exact screen labels and available filters can change as GoHighLevel develops. The durable operating principle is to use filters to answer a specific question: what do I own, what is late, what is due next, or where is the process blocked?
Manual actions versus automated actions
Manual actions and automated actions solve different problems. An automated action is appropriate when the rule is known, the data is reliable, and the outcome does not require judgment. A manual action is appropriate when a person must interpret information, choose between alternatives, or communicate in a context-sensitive way.
When the rule is repeatable
Use an automated step for predictable operations such as updating a field, sending a standard notification, applying a tag, or moving a record after a clearly defined condition.
When judgment is required
Create a manual action when a user must assess quality, choose a response, verify information, or make a decision that cannot yet be expressed as a reliable rule.
The wrong choice creates two common problems. Automating a judgment-heavy step can produce poor customer experiences or unreliable data. Creating a manual task for a simple rule increases workload and makes the CRM harder to maintain.
Before adding a manual action, ask: What decision is the owner expected to make, and what should happen after that decision? If the answer is unclear, the process needs definition before the task needs configuration.
Designing useful manual actions
A well-designed action is short enough to understand quickly but specific enough to guide execution. It should normally identify the subject, the required action, the timing, and the expected result.
- Name the outcome, not just the activity.
- Assign one accountable owner.
- Include relevant context or a direct path to the CRM record.
- Define when the action becomes late.
- State what the owner should do if the required information is missing.
- Define the next business state after completion.
For example, “Follow up with lead” is weak because it does not explain the purpose or acceptable outcome. “Review the pricing enquiry and call the contact to confirm requirements” gives the owner a clearer job. The workflow can then define what should happen after the call, such as updating qualification information or creating the next appropriate action.
An action is complete when the intended business outcome is recorded, not when the user has merely interacted with the task.
Handling unassigned, missed, and completed work
Unassigned actions
Unassigned actions are an early warning that the workflow has created demand without creating accountability. A team lead can assign them manually, or the underlying process can be redesigned to route work using a defined rule. If unassigned items occur regularly, investigate whether team structure, routing data, or workload assumptions are causing the gap.
Missed actions
A missed action should trigger a recovery decision. The team may need to complete the work late, reassign it, contact the customer with an updated expectation, or determine that the action is no longer required. Simply marking every missed item complete removes evidence of the problem.
Look for patterns by action type, owner, due-time rule, and workflow source. Repeated misses may indicate that the deadline is unrealistic, the action is generated too early, the instructions are unclear, or the assigned role does not have the required capacity.
Completed actions
Completed actions provide a useful operational record when completion has a consistent meaning. Review them to confirm that the process is producing the expected next state. For example, a completed call task might be expected to result in a documented outcome, an updated qualification field, or a scheduled next step. If none of these are visible, the task may be recording activity without improving data quality.
Practical scenarios for GoHighLevel manual actions
Scenario 1: New lead review
Suppose a form submission contains incomplete information and a sales user must decide whether the enquiry is genuine, urgent, or suitable for a particular service. A workflow can create a manual review action. The owner checks the record, completes the missing classification, and decides whether the lead should receive a call, a standard nurture sequence, or no further action.
Scenario 2: Service request follow-up
Suppose a customer request requires a person to confirm details before a resolution can be offered. A manual action can assign the follow-up to a service owner with a due time. If the task becomes missed, the team has a visible signal that the customer may still be waiting and that the process needs attention.
Scenario 3: Approval before automation
Suppose a change to a customer record should not trigger a broader campaign until someone verifies the information. The manual action becomes a controlled checkpoint. Once the owner confirms the data, the next automated step can proceed with less risk of sending the wrong communication.
Improving the operating model over time
Manual actions should be reviewed as part of the wider CRM operating model, not only as a productivity feature. Start by identifying which actions are frequently missed, repeatedly reassigned, or completed without a meaningful record. Then ask whether the issue is a workflow rule, an ownership rule, a data problem, or a capacity problem.
When the process is stable, automation can remove unnecessary manual work. If the same decision is made consistently and the required data is dependable, it may be possible to express the rule as an automated action. If the decision remains variable, keep the human step but improve its instructions and context. AI may assist with classification or preparation only when it has a defined job, a known input, and a human responsibility for the final decision.
For broader CRM architecture, routing, pipeline design, and workflow governance, see ConsultEvo CRM Consulting. If the manual action is part of a wider connected automation, systems, automation and AI implementation services can help align the process before tools are configured.
The goal is not to maximize the number of actions on the board. It is to create a reliable path from a real business event to a clearly owned decision, with enough visibility to improve the process when work is delayed or completed incorrectly.
Frequently asked questions
What is a manual action in GoHighLevel?
A manual action is a workflow-generated task that requires a person to complete work or make a decision, such as a call, review, approval, or personalized follow-up.
What does an unassigned pending manual action mean?
It means the action exists but no user is responsible for completing it. Treat it as an ownership gap and assign it before it becomes part of the normal backlog.
What should a team do with missed manual actions?
Review the item, decide whether the work is still required, assign or reassign it when appropriate, and investigate recurring misses caused by timing, capacity, routing, or unclear instructions.
When should a workflow use a manual action instead of automation?
Use a manual action when human judgment, verification, interpretation, or personal communication is required. Use automation when the rule and outcome are repeatable and reliable.
How can manual actions improve CRM operations?
They make human work visible, give tasks clear ownership, expose delays, and create a record that can be used to improve workflow timing, data quality, and handoffs.
Make CRM tasks easier to own and improve
If manual actions are creating confusion, missed follow-ups, or unreliable reporting, review the workflow behind them before adding more automation. ConsultEvo can help clarify the process, ownership rules, CRM structure, and automation logic.
