GoHighLevel Opportunity Lost Reasons: Setup (2026)

By Dr Priya Jaganathan, GoHighLevel Certified Admin · HL Growth Partner, Australia · Updated 2 October 2026 · 10 min read

GoHighLevel lost reasons are the most under-used field in most sub-accounts I audit. Every pipeline has deals that die, but very few teams record why in a way they can actually report on, automate from or learn from.

This guide walks through the Lost Reason field from start to finish. You'll learn how to edit the options, design a short reason list your team will actually use, export and report on it, and trigger win-back workflows when an opportunity is marked Lost.

What the GoHighLevel lost reason field actually does

When someone on your team marks an opportunity as Lost, HighLevel asks them to pick a reason from a dropdown. That choice is saved on the opportunity record, next to its status, value, pipeline and stage.

For a long time the reason list was fixed, and agencies kept asking to change it. HighLevel now treats the lost reason as a managed field. That means each sub-account can tailor the options to its own sales process instead of putting up with generic labels that don't fit.

If you're still getting your head around how statuses, stages and pipelines fit together, start with our GoHighLevel pipelines and opportunities guide first. Lost reasons only make sense once your pipeline stages are clean.

Lost versus Abandoned

HighLevel gives you four opportunity statuses, and two of them sound similar. Getting the distinction right matters more than the reason list itself.

How to add, rename and delete HighLevel opportunity lost reasons

According to the HighLevel changelog entry for the Lost Reason field, the field now sits alongside your other opportunity custom fields. HighLevel released it through Labs, so what you see may depend on whether the feature has been switched on in your sub-account.

Step-by-step

1. Open the sub-account and go to Settings > Custom Fields.
2. Use the search bar to find "Lost reason".
3. Open the field's edit option.
4. Add the new reasons you want, rename any that are unclear and delete the ones you won't use.
5. Save, then mark a test opportunity as Lost to confirm the new list appears in the dropdown.

If you can't find the field

If the search returns nothing, check the sub-account's Labs area for "Lost reason for opportunities" and switch it on. Labs features can change over time, so if the screen looks different from what's described here, trust what's in your account and the current changelog.

Because this is a custom field, the same habits apply as for any other field you manage. Our custom fields setup guide covers naming conventions and folder structure that keep sub-accounts tidy.

A note on deleting reasons

Before you delete an old reason, export your lost opportunities first. Keep a copy of your historical data before you clean up the list, so last year's numbers don't go missing from your quarterly comparison.

Designing a clean lost reason list (6–8 options)

A list of 20-plus reasons fails because reps just pick whatever is closest to the top.

Aim for six to eight reasons. Each one should point to a different follow-up action. If two reasons would lead to exactly the same next step, merge them.

Write reasons from the buyer's point of view

"Rep didn't follow up" is a coaching note, not a lost reason. Keep the dropdown about the buyer's decision, and handle rep performance in your one-on-ones.

Making the lost reason mandatory in your team process

There's a long-running feature request on the HighLevel ideas board for making custom fields required before an opportunity changes stage or status. Until something like that is available in your account, treat completeness as a process rule rather than a system setting.

Here's the routine I set up for clients:

• Written rule: nobody marks an opportunity Lost without choosing a reason and adding a one-line note.
• Weekly check: the sales lead filters lost opportunities from the past seven days and spots blanks or "Other" with no note.
• Automated nudge: a workflow creates a task for the opportunity owner when an opportunity is marked Lost with "Other" selected.

For the nudge, use a workflow with an If/Else branch on the lost reason. Our workflow If/Else conditions guide shows how to build branches that check field values without creating duplicate workflows.

Exporting and reporting on GoHighLevel lost reasons

Once your reasons are clean, the data starts paying for itself. HighLevel's changelog confirms that the lost reason now appears as a column when you export opportunities, which makes spreadsheet analysis easy.

Exporting lost opportunities

1. Go to Opportunities and open the pipeline you want to review.
2. Filter the status to Lost and set the date range, such as the last quarter.
3. Export the filtered list to CSV.
4. In your spreadsheet, build a pivot table with lost reason as rows and count and total value as values.

Look at count and value together. Five deals lost on price at $500 each tell a very different story from two lost to a competitor at $15,000 each.

Lost reasons in dashboards and smart lists

For a live view, add opportunity widgets to a custom dashboard and filter them by status and pipeline. Our dashboards and reporting guide walks through building widgets your team will actually open each week.

Filter options can vary between the opportunities view, smart lists and dashboard widgets. If you can't filter directly on lost reason in one place, a reliable workaround is to have your Lost workflow add a tag such as lost-price or lost-competitor to the contact. Tags filter cleanly in smart lists, so you can build a "Lost on price – last 90 days" list for re-offers.

Win-back workflows triggered by Opportunity Status Changed

This is where lost reasons go from a reporting field to a revenue tool. The Opportunity Status Changed trigger documentation describes a lost reason filter you can add to the trigger, so a workflow can fire only when a specific reason is chosen.

Build one workflow per reason

• Trigger: Opportunity Status Changed, with filters for the pipeline, status Lost and the lost reason you're targeting.
• Action 1: add a reason-specific tag to the contact.
• Action 2: wait the right amount of time for that reason.
• Action 3: send a short, personal email or SMS that acknowledges why they said no.
• Action 4: create a task for the owner if the contact replies.

Example timing by reason

Keep these workflows short and stop them the moment the contact replies or a new opportunity opens. If the deal was lost after a quote went out, pair this with your quote follow-up workflow so the two sequences don't double up.

When a win-back works, create a new opportunity rather than reopening the old one. Keeping the original Lost record intact protects your reporting history and shows you exactly which reasons are recoverable.

A quarterly lost reason review routine

I recommend a 45-minute review each quarter with the business owner and whoever runs sales.

1. Export last quarter's lost opportunities with the lost reason column.
2. Rank reasons by count and by total value.
3. Compare with the previous quarter. Which reason grew? Which shrank?
4. Read the "Other" notes and decide whether any deserve their own reason.
5. Pick one fix for the top reason, such as new pricing, a sharper proof asset or better ad targeting.
6. Check win-backs: how many lost contacts came back as new opportunities?
7. Update the list in Settings > Custom Fields if needed, and brief the team.

Common mistakes to avoid

• Building a reason list so long that reps pick the first option just to get through it.
• Using Lost when you really mean Abandoned, which mixes up decisions with silence.
• Deleting old reasons without exporting historical data first.
• Letting "Other" become the most-used reason because no note is required.
• Building win-back workflows without exit conditions, so contacts who've already re-engaged keep getting messages.
• Reopening old lost opportunities instead of creating new ones, which hides what's recoverable.

If you want your pipelines, lost reasons and win-back workflows set up properly from day one, book a strategy call with the HL Growth Partner team.

Book Your Strategy Call →

Frequently asked questions

Where do I edit lost reasons in GoHighLevel?

Go to Settings > Custom Fields in the sub-account and search for "Lost reason". Open the field's edit option to add, rename or delete reasons, then save. The updated list appears in the dropdown the next time someone marks an opportunity as Lost.

Why can't I see the Lost reason field in Custom Fields?

HighLevel released this feature through Labs under the title "Lost reason for opportunities". If the field doesn't show up when you search, check the Labs area of the sub-account and switch the feature on. The interface can change, so confirm against the current HighLevel changelog.

How many lost reasons should I have?

Six to eight reasons works well for most small businesses. Each reason should lead to a different follow-up action. If two reasons would trigger the same next step, merge them into one.

Can I make the lost reason mandatory?

Treat it as a team rule backed by a weekly check rather than relying on a system setting. Required custom fields on status changes have been requested on the HighLevel ideas board. Until that is available in your account, a short weekly review of lost opportunities catches any gaps.

Can I export opportunities with the lost reason included?

Yes. HighLevel's changelog confirms that lost reason is available as a column when you export opportunities. Filter the pipeline by Lost status and a date range, export to CSV and build a pivot table by reason.

How do I trigger a workflow when a deal is lost for a specific reason?

Use the Opportunity Status Changed trigger and add filters for the pipeline, the Lost status and the lost reason you want. Build one short workflow per reason, with timing and messaging that fit why the prospect said no.

What's the difference between Lost and Abandoned?

Lost means the prospect made a decision or you disqualified them, so you know the reason. Abandoned means the lead went quiet with no decision. Abandoned contacts are better suited to a reactivation campaign than a reason-specific win-back.

Should I reopen a lost opportunity if the client comes back?

It's usually better to create a new opportunity. Keeping the original Lost record intact protects your reporting history. It also shows you which lost reasons actually lead to recovered revenue.

Related Articles on HL Growth Partner

Pipelines and forecasting

• GoHighLevel Pipeline Setup: Forecast Revenue
• GoHighLevel Pipeline Automation
• GoHighLevel Proposals & Estimates Setup

Win-back and lead quality

• GoHighLevel Database Reactivation Campaign
• GoHighLevel Attribution Reporting: Lead Sources
• GoHighLevel Lead Scoring: Workflow Setup

Team process

• GoHighLevel Tasks: Team Workload Management
• GoHighLevel Contact Timeline & Activity History