VettedGaps
Free sample

You're reading one of the top pains on Gong Partner Ecosystem — a free sample of the catalog. Create a free account to browse all Shopify & Atlassian pains and the basic Chrome catalog.

Competition — unlock in Pro

Gong users get duplicate Salesforce tasks and contact roles from call syncs

.57
Demand — how loud & how many (score)
Willing to payImplicit
Momentum (7d)▼ 1.4%
Cluster11 posts · 10 people
MarketplaceGong Partner Ecosystem
Updated4h ago
The story

The pain

When Gong syncs calls with multiple participants to Salesforce, it creates a separate task for each contact on the call instead of a single task. This inflates our activity metrics and makes it look like we completed more meetings than we actually did. The same duplication happens with contact roles on opportunities, where batch syncing creates up to five duplicate roles for a single opportunity. We need a way to group unique calls or emails into a single Salesforce record.

Evidence

What people said · 11 complaints, 10 people

The problem is if there are multiple contacts from the prospect company on the call then it creates a task for each person. This skews reporting and shows us as having completed more meetings than we actually have.
ForumClaire.HummingbirdJun 13
Gong is creating multiple tasks for emails sent to multiple recipients, one task per recipient. This is inflating our activity metrics and I haven’t found a way to group unique emails together to solve for this.
ForumKelli SmithSep 1
We have tried implementing time delays, scheduled batches, separate flows, but the result is the same. There have been up to 5 duplicate contact roles created for a single opportunity and we can't find an easy solution.
ForumKatie-WatershedSep 6
Competition

Who's solving it

Competitor research is a Pro feature PRO

See who already ships against this pain, how they price, and exactly where the gap is.

Under the hood

Score breakdown

Reach
how many people
1.0
Recency
how fresh
.09
Engagement
upvotes & replies
.75
Willingness to pay
people said they'd pay
PRO
Next step

Turn this pain into a build brief

Export the pain — problem, evidence and market signals — as Markdown, PDF or JSON. The Markdown export ships with a built-in briefing you can hand straight to a developer or an AI agent.

Comments are a Pro feature PRO

Discuss this pain with other builders and see who's already shipping against it.