# HighLevel feels full of glitches and bugs for me, how are you getting it stable?

I see a lot of potential in HighLevel, but I’m running into constant glitches and it feels like about half the features have bugs or other issues. Support will open a ticket, but then I don’t hear back, and the software isn’t usable for me right now. If you’ve dealt with similar problems, what helped you reduce failures or get support to actually follow up?

##### Post Metadata
- Posted at: 13 days ago
- Author title: Owner
- Net upvotes: 1


## Comments
### Comment 1

&lt;p&gt;I can understand why it might feel that way at first, especially if you&#39;re using a lot of the platform&#39;s features simultaneously. My experience has been quite different because we invested time in setting things up properly and following best practices instead of building everything in one go.&lt;/p&gt;&lt;p&gt;A few things that have made HighLevel very stable for us:&lt;/p&gt;&lt;ul&gt;&lt;li&gt;&lt;strong&gt;We keep snapshots and test changes first.&lt;/strong&gt; Before making major workflow or funnel changes, we test them in a duplicate environment. This has prevented most issues from reaching production.&lt;/li&gt;&lt;li&gt;&lt;strong&gt;We avoid unnecessary workflow complexity.&lt;/strong&gt; Rather than one massive workflow with dozens of branches, we split automations into smaller, modular workflows. They&#39;re easier to troubleshoot and perform more consistently.&lt;/li&gt;&lt;li&gt;&lt;strong&gt;We use native features wherever possible.&lt;/strong&gt; Native integrations tend to be more reliable than chaining together multiple third-party tools unless there&#39;s a specific need.&lt;/li&gt;&lt;li&gt;&lt;strong&gt;We stay on top of updates.&lt;/strong&gt; HighLevel ships new features and fixes very frequently. While that means occasional regressions can happen, it also means bugs are often resolved quickly. Reading release notes and knowing about feature changes has helped us avoid surprises.&lt;/li&gt;&lt;li&gt;&lt;strong&gt;We follow recommended implementation practices.&lt;/strong&gt; Things like keeping custom values organised, avoiding duplicate triggers, validating calendars and phone settings, and testing before going live have significantly reduced issues.&lt;/li&gt;&lt;/ul&gt;&lt;p&gt;No SaaS platform is completely bug-free—especially one that evolves as quickly as HighLevel—but in my experience, most of the challenges I&#39;ve encountered have been configuration-related rather than platform-breaking bugs. Once the account is structured well, it&#39;s been reliable enough to support day-to-day CRM, automation, communications, and client management without major disruption.&lt;/p&gt;&lt;p&gt;For me, the flexibility HighLevel offers outweighs the occasional issue, and the pace at which the team releases improvements has been a big positive.&lt;/p&gt;

##### Comment Metadata
- Posted at: 13 days ago
- Author title: Customer Success Advisor


#### Reply 1

No I&#39;m talking about bugs and glitches that have left me unable to use the website. Something simple as email sync has blown there mind and forced a ticket up the the senior tech support that has gone unanswered for over a week. Unable to move forward without basic functionating integration . 

##### Reply Metadata
- Posted at: 13 days ago
- Author title: Owner



## Related Product
[HighLevel](https://www.g2.com/products/highlevel/reviews)

## Related Category
[CRM](https://www.g2.com/categories/crm)

## Related discussions
- [How well does Trello scale into a larger team?](https://www.g2.com/discussions/1-how-well-does-trello-scale-into-a-larger-team)
  - Posted at: about 13 years ago
  - Comments: 6
- [Can we please add a new section](https://www.g2.com/discussions/2-can-we-please-add-a-new-section)
  - Posted at: about 13 years ago
  - Comments: 0
- [Quantifiable benefits from implementing your CRM](https://www.g2.com/discussions/quantifiable-benefits-from-implementing-your-crm)
  - Posted at: about 13 years ago
  - Comments: 4


