We were already running Gong Foundation when we made the decision to add Engage, and the rollout was shockingly painless. We had our 25-person sales team fully onboarded and integrated in under a week. For a team mid-cycle, that kind of zero-friction implementation is genuinely rare.
The UI is where Gong separates itself most visibly from competitors. New sales reps pick it up fast without hand-holding. It's not dumbed down, it's just well-designed. When you're onboarding folks who need to be productive immediately, that matters more than any feature list.
On the performance side, our team's ability to make high call volumes quickly improved significantly after switching. We came from a direct competitor, and beyond the capability improvement, the cost came in slightly lower. That's an easy business case to make.
The real unlock, though, is the integrated AI suite. Having Engage live inside the same ecosystem as Gong's conversation intelligence means the AI context is already there. You're not stitching together insights across disconnected tools. The rep who made the call, listened to the summary, and gets AI-assisted follow-up sequences is working in one place with one coherent data layer. That's where the ROI compounds in ways that are hard to quantify but easy to feel. Review collected by and hosted on G2.com.
The biggest challenge right now is that Gong is expanding fast and the product is starting to outpace its own documentation. There are a lot of AI tools available, but there's no real in-depth walkthrough of how to use them effectively. For admins trying to drive adoption across a team, that gap shows up quickly.
Permissions and role-based settings are also underdeveloped. I have VPs of Sales who need different access and visibility than SDRs, but the admin controls don't reflect that cleanly. It feels like the role differentiation wasn't fully thought through, and it makes setup more manual and more fragile than it should be.
On the UI side, nothing is a dealbreaker, but there are enough friction points that the team notices. Navigating call history is clumsier than it should be, especially when trying to track down a previous dial or understand whether something is tied to a contact versus an account. Sync times can lag. And there are continuity issues in Engage flows where a rep finishes the last step and then has no clear indication of what happened or where to go next. Separately, jumping from Engage to a new tab just to find something in the company library is the kind of small thing that adds up across a team doing high-volume outreach.
None of this has made us regret the switch. But there's meaningful room to grow on the admin control and in-product guidance side. Review collected by and hosted on G2.com.



