Revenue AI connecting conversations, account briefs, trackers, deal context, coaching, and separately scoped outreach and forecasting.
Gong
Explore features, practical uses and pricing below.
Gong is a revenue AI platform that connects customer conversations with sales activity, deal context, coaching, and sales execution. It helps sellers and managers find relevant moments in recorded interactions, organize account information, and work with pipeline signals. Its broader product family includes foundational conversation capabilities and separately scoped offerings such as Engage, Forecast, and Enable.
Gong suits revenue teams that need to understand what happened across customer interactions rather than rely only on a short CRM note. A seller can prepare for a meeting, a manager can inspect a deal concern, and an enablement team can find examples of a discussion. The underlying evidence remains important: a generated summary or detected concept should lead to a clearer review of the conversation, not replace the team's judgment about the customer.
Gong's revenue-intelligence approach brings recorded conversations and other connected activity into the revenue workflow. Its usefulness depends on capturing the right interactions, associating them with the right records, and giving the relevant team members access. A missing or mislinked call can make an otherwise organized account view incomplete.
During setup, identify the conferencing, email, calendar, and CRM connections your team will use. Decide which meetings belong in the system and which should remain outside it. A company may want customer discovery and account reviews available for coaching while keeping unrelated internal discussions out of the sales library.
Review a representative set of imported interactions. Check the participants, account, opportunity, and date. If a company has multiple active deals, confirm that the relevant conversation appears against the correct one. Gong supports manually correcting a call's CRM association when the automatic link is wrong.
Once the records are connected, sellers can use the resulting context to prepare more focused questions. A past conversation may reveal an unresolved concern or an agreed next step. It should not be taken as evidence of a customer's current position without considering when it occurred and whether later interactions changed the situation.
The recording and consent guide describes organization-level consent profiles and individual recording settings. Depending on configuration, a profile can use a pre-call email, a consent page, or an audio announcement. The appropriate setup depends on the organization's policy and the rules applicable to its conversations.
Confirm the actual meeting route used by your team. A supported consent page relies on the configured conferencing provider and meeting links; an unusual provider or scheduling path may behave differently. Ask the administrator how a participant declines recording and how a meeting is handled when it should remain private. Give sellers a clear process to follow before the call.
After capture, call actions are controlled by permissions and the call's state. Authorized people can download media or transcripts, adjust privacy, correct associations, or delete a call. Private calls have a restricted audience, and changing that setting requires the appropriate authority.
A downloaded file is a separate copy, so manage it through the organization's normal handling process. Before sharing a clip or summary outside the team, check who may receive it and whether it contains sensitive customer information. The platform's sharing features make access convenient; the organization determines what sharing is appropriate.
Gong trackers help teams identify recurring topics in conversations. Keyword trackers look for specific wording, while AI trackers look for concepts or intent expressed in different ways. This distinction is useful when a precise product name matters in one analysis and a broader concern, such as uncertainty about budget, matters in another.
The current AI tracker guide describes question-based configuration with supporting details, conversation-party selection, filters, and lifecycle settings. A question should identify something observable in the conversation. Asking whether a customer expressed a particular concern is clearer than asking whether the whole deal is good.
Test the tracker against examples that should and should not match. Review the source moments to understand false positives and missed cases. Narrow a vague concept, add relevant context, or adjust the party being tracked if the result repeatedly includes a seller's pitch rather than the customer's response.
Tracker signals can appear in search, deal activity, coaching, and other configured views. They are useful for locating evidence and organizing review. A signal that a topic occurred does not establish that the customer agreed with it or that the seller handled it well. Listen to the surrounding discussion before drawing that conclusion.
Gong's brief types define structured summaries for calls, deals, or accounts. A brief can combine conversation sections, web information, and CRM or Gong data. Administrators can create the structure, test sections, preview the whole result, and publish it for the team.
A meeting-preparation brief might contain the customer's stated goals, open questions, and recent activity. Keep the sections narrow enough for someone to verify. If a section draws from the web, distinguish that public information from something the customer actually said. If a field comes from the CRM, confirm it reflects the relevant record and period.
Natural-language questions through Ask Anything help people explore account or deal context. The available evidence can be bounded by the surface and feature configuration. For example, mobile documentation describes a recent set of calls and emails, rather than an unrestricted search of every interaction ever recorded.
Ask a question that fits the evidence, such as which objections arose in recent discussions or what next step was agreed. Open the supporting interaction before turning the answer into a commitment. If the answer is incomplete, consider whether the relevant conversation was captured, accessible, or inside the period being considered.
Deal boards combine CRM fields with activity and configured AI insights. They can include deal value, stage, close date, contacts, warnings, brief access, and methodology-related information. Access to some columns or scores depends on the purchased product and permissions.
Configure a board around the questions a pipeline review must answer. A board for near-term opportunities may need next steps and expected close dates, while an expansion review may need account ownership and recent engagement. Limit the visible fields to those the team understands and uses; a dense board can hide the information that needs discussion.
The configuration guide describes adding CRM fields, trackers, playbooks, and suggested text-field updates. It also explains brief defaults for review and deal health. Review suggested updates before writing them back to the CRM, and retain the distinction between a detected activity signal and a seller's commercial assessment.
During a review, inspect the source of a warning or a changed assessment. An absence of captured activity could reflect a quiet deal, an unrecorded conversation, or a connection issue. Use the signal to ask a better question, then establish what happened before changing the plan.
Gong Forecast supports forecast-related views and processes, with access distinct from the foundational conversation offering. Its AI Revenue Predictor documentation describes projections based on closed-won revenue, weighted pipeline, and expected activity using historical patterns. The selected forecast-board configuration and historical period affect the estimate.
Check that the underlying definitions match the business. Confirm which opportunities qualify, whose deals are included, and what close-date range is used. A projection for one line of business should not be compared with a total company number unless the scope is aligned.
Historical patterns are useful context, but a material change in product, territory, pricing, or sales process can make a prior period less representative. Review the projection alongside known events and the current pipeline. Treat it as an estimate that helps frame discussion, with uncertainty and data coverage kept visible.
A forecasting rollout needs participation as well as configuration. Agree on submission timing, ownership, and how managers handle differences between a seller's judgment and a modeled signal. The software provides a shared analytical environment; leadership still owns the forecast process and the resulting business decisions.
Gong Engage handles sales-execution activities such as organized outreach and flows. The flow documentation describes a sequence of steps for contacting people, with personal and company flow permissions. Supported steps include manual or automated email, calls, LinkedIn-related tasks, and other work.
Choose the level of review for each step. A manual email step can provide an AI draft for the owner to edit before sending. An automated email follows a different execution path. A team should know which type it has configured before enrolling a large group of contacts.
Inline prompts can generate selected portions of a template using account context. They are intended for snippets or sections, such as an opening or meeting recap. Keep fixed policy language and important commercial conditions controlled, and inspect generated personalization for unsupported assumptions.
Flow automation can enroll contacts when defined conditions are met. Review the trigger, recipient selection, timing, and stop behavior. A detected topic in a conversation may justify a seller task without justifying an immediate customer email. Match the automated action to the confidence and significance of the trigger.
Gong Enable focuses on coaching and adoption of sales initiatives. Conversation evidence and structured evaluation help managers find examples for discussion. Trackers can direct attention to relevant moments, while scorecards and other configured processes support a consistent review.
Define what good performance means for the activity being coached. A discovery call may need clear questions and a shared understanding of the problem; a negotiation may require careful handling of terms. Avoid interpreting one conversational metric as a complete assessment of a seller's ability.
Choose examples with enough surrounding context for the lesson to make sense. A short clip can illustrate a question or objection, but the manager should understand what led to it. Give the seller a chance to explain information that occurred outside the recording, then agree on a specific practice to apply in a future conversation.
Enablement teams can use recurring topic review to see where a new message appears in conversations. Adoption is different from effectiveness: hearing a phrase does not prove that it persuaded the customer. Combine captured examples with the team's broader understanding of the sales process.
Suppose an account moves from one seller to another. Begin by checking the CRM associations and the relevant customer interactions. Generate a structured brief covering the stated goals, outstanding concerns, agreed next steps, and key participants. Review important points against the linked conversations and current records.
The receiving seller can ask focused questions about recent context, then prepare an agenda that acknowledges what the customer already discussed. Keep unresolved information visible, particularly if the customer has not confirmed a date or decision process. Do not turn a tentative comment into a firm commitment merely to make the brief concise.
A manager can inspect the deal board for activity and warnings, while the seller determines the appropriate follow-up. If Engage is part of the deployment, a reviewed flow or task can support the next steps. If Forecast is included, the team can consider whether the ownership change affects the forecast assessment.
For repeated handoffs, automated briefs can distribute context when supported CRM conditions occur. Choose recipients carefully and confirm the trigger scope. Test the handoff on a few representative accounts before making the automation routine.
The pricing page describes per-user licenses and a platform fee tied to supported users, with a customized proposal. The plans and seats guide distinguishes access across the product family. Ask for the exact modules and seat types your team needs instead of assuming a conversation subscription includes all forecasting and outreach features.
Some AI work also consumes Gong credits. Current tracker and automated-brief documentation explains relevant consumption. The tracker management guide describes pausing unused trackers and notes that insufficient credits can pause analysis. Review active scope, dates, and recurring automation when estimating usage.
Include implementation and operating ownership in the evaluation. Connections, consent settings, record associations, access rules, and shared templates require maintenance. Confirm the controls and support that apply to the purchased configuration, then establish who reviews them as the team changes.
Is Gong a replacement for the CRM? It connects revenue interactions with CRM context and supports updates through configured workflows. The existing CRM remains an important part of the deployment.
Are trackers the same as keywords? Keyword trackers identify wording; AI trackers interpret concepts. Inspect the relevant moments before treating a detection as evidence of agreement or successful selling.
Can AI summaries cover every interaction? Coverage depends on capture, permissions, associations, and the feature's evidence scope. Check those factors when an answer omits something the team expects.
Are Engage and Forecast included automatically? Product and seat access vary. Confirm the specific modules in the proposal and account.
What should we evaluate first? Test a real meeting-to-review workflow: recording setup, correct CRM association, evidence inspection, a useful brief, and the next action. Then assess usage and broader modules.