Gong

The Gong integration reads your customer calls, uses AI to pull out the feature requests customers mention, and sends them to a Suggestions inbox in FeatureOS. An admin approves each one as a new post or as a vote on a matching post. Every request carries the deal name, stage and amount, and when the feature ships, the rep on the call gets an email.

Customers tell your sales team what they need on every call. Most of it never reaches the product team, and the part that does arrives as a vague "customers keep asking for X". The Gong + FeatureOS integration moves those requests into your feedback board with the evidence attached: a short quote, who said it, a link to the call, and the deal it belongs to.

The Gong integration is available on the Growth plan and above. Call analysis uses your existing AI credits, with no separate charge.

How to Connect Gong to FeatureOS

1. In FeatureOS, go to Settings > Integrations > Gong and click Connect.
2. Sign in to Gong as a technical administrator and click Allow. FeatureOS asks for read-only access: call details, call transcripts and users.
3. Choose your settings:
   • Workspace IDs limits the sync to specific Gong workspaces.
   • Tracker IDs limits it to calls where specific Gong trackers fired.
   • External calls only skips internal calls. It is on by default.
   • Create customers for unmatched participants adds call participants who are not yet in FeatureOS as customers. It is off by default.
4. Save.

How the Gong Sync Works

FeatureOS checks Gong every hour and picks up calls that ended about three hours earlier. Calls marked private in Gong are skipped. The sync is one-way: data flows from Gong into FeatureOS, and nothing is written back to Gong.

For each call, AI extracts the feature requests the customer made. For every request FeatureOS stores a short verbatim quote, the speaker, a link to the call, and the deal name, stage and amount. Full transcripts and call recordings are never stored in FeatureOS.

From Call to Shipped Feature

1. Suggestions inbox: extracted requests land here and nowhere else, so nothing reaches your public board without review.
2. Review: an admin approves a request as a new post, or as a vote on an existing post that already covers it.
3. Revenue on the post: each post shows the pipeline revenue tied to it. When requests come from deals in different currencies, the total is left blank rather than adding unlike currencies.
4. Close the loop: when the post's status moves to Completed, the rep on the call gets one email telling them it shipped.

Why Teams Use Gong with FeatureOS

Product managers see how much pipeline depends on each request, with the customer's own words next to it. Sales reps stop re-typing call notes into a spreadsheet and hear back when the feature they asked for ships. Leadership can rank the roadmap by revenue as well as vote count.