AI workers for Gong

What is an AI worker for Gong?

An AI worker for Gong is an AI agent scoped to one revenue-conversation job, such as summarizing what was committed on a call or reporting the deals whose language has turned cautious. It reads calls through your connected Gong account within the scope you grant, and private calls are guarded separately, so marking them off limits does not depend on any other setting.

What these workers do

Summarize what was committed on a call

Returns the promises made on both sides, the objections raised, and the next step that was actually agreed rather than assumed.

Surface deals whose language has cooled

Reads recent conversations on open deals and flags the ones where the customer's own words have turned tentative.

Pull the objections nobody answered

Collects the concerns raised across calls that received no real response, which is usually the same short list every week.

Prepare the next conversation

Reads the history with an account and returns what was promised, what is outstanding, and what to avoid repeating.

How an AI worker runs in Gong

This is the connection where the firewall earns its keep

Private calls are their own decision

What calls are actually good for

Gong questions, answered.

Can an AI worker read every call in our Gong workspace?

Only what you scope it to. This connection is broad by nature, which is why the scoping matters: you choose the calls in reach and that decision is enforced before the worker receives anything, rather than being an instruction it is trusted to follow.

What happens with calls marked private?

Private calls are protected by their own control, independent of your other access settings. Widening scope elsewhere does not quietly bring them into reach, which is the behaviour you want from a guard on sensitive conversations.

Does it change anything in Gong?

These workers are normally read only, with their output going to your CRM, a chat channel, or a digest. The conversation record itself stays as it was, which keeps Gong authoritative about what was said.

Can it see calls belonging to other sellers?

Only if you scope it that way. A manager's reporting worker and a seller's own preparation worker are different setups with different reach, and the narrower one cannot see beyond its scope regardless of instructions.

What AI workers can do in Gong

The tools a worker can be granted in Gong once you connect it. A kit grants only the ones its job needs, and you can narrow them further on the worker.

List Calls

List recorded calls newest first, each with title, host, participants, timing, classification, trackers and the AI summary (`brief` / `keyPoints`); the verbatim `transcript` is never included here, fetch it with gong_get_transcript. Filter by date range, `workspaceId`, `primaryUserIds`, or `query` (keyword match over title and AI summary), and default to the last 30 days when no range is given. Access may be limited to a lookback window and to specific workspaces or customers, and calls marked private in Gong are withheld unless private access is granted, so a short or empty `calls` list with a non-null `accessInfo` means a rule limited what is visible, not that no calls exist; render `accessInfo` verbatim. Paginate with the response's `nextCursor` into `cursor` and stop when `hasMore` is false.

Get Call

Get one call with its metadata, participants, topics, tracker hits, interaction stats, CRM context and AI summary. The verbatim `transcript` is not included; use gong_get_transcript for that. AI content (`brief`, `keyPoints`, `outline`, `highlights`, `callOutcome`) is present only once Gong has generated Spotlight for the call, so its absence means Spotlight has not run rather than that access was denied. Recording URLs (`media`) ride the response only when granted, and expire 8 hours after Gong issues them. Any field masked off comes back null or empty with an explanatory `accessInfo`; render it verbatim.

Get Transcript

Get one call including its verbatim `transcript`: speaker-attributed monologues, each with per-sentence start/end times in milliseconds, alongside the same summary and metadata gong_get_call returns. Speaker names resolve from the call's participants when those are visible; otherwise only `speakerId` is set. The transcript is a separately governed, higher-sensitivity tier needing BOTH the `get_transcript` operation AND the `transcript` field: when either is missing the whole request is denied rather than returning the call with a null transcript, so fall back to gong_get_call for the summary. Render the denial's `accessInfo` verbatim; it names which grant is missing.

List Workspaces

List the Gong workspaces in scope, each with `id`, `name` and `description`. Use an `id` as the `workspaceId` filter on gong_list_calls, gong_list_library_folders, gong_list_trackers and gong_get_stats.

List Library Folders

List the library folders calls are filed into, each with `id`, `name`, optional `parentFolderId` and `updatedAt`. Gong's API exposes public folders only, so private and archived folders never appear here.

List Users

List the Gong seats, each with `id`, `emailAddress`, name, `title`, `active` state and `managerId`. Use an `id` as `primaryUserIds` on gong_list_calls or `userIds` on gong_get_stats. Paginate with the response's `nextCursor` into `cursor` and stop when `hasMore` is false.

List Trackers

List the tracker definitions, each with `id`, `name`, `type` (KEYWORD or SMART), `workspaceId` and its `phrases`. This is the definition list only: how often a tracker fired on a given call, and where, rides gong_get_call.

Get Stats

Read per-user activity or interaction stats over a date range; each row carries the user's id, email and name, the period covered, and a `metrics` map of Gong's measures for the requested `statsType`. Gong computes these aggregates over every call a user was on, so they are readable only where Gong access is not scoped down to particular workspaces or customers; a scoped connection is denied outright and `accessInfo` says so. Paginate with the response's `nextCursor` into `cursor` and stop when `hasMore` is false.