Gong

Your assistant can list the calls in a date range, pull the metadata for a specific one, and retrieve the full transcript with speaker labels, timestamps, and topic categorization. That means you can ask about a call you were not on and get the customer's own words rather than the rep's recollection of them. It reads only, and nothing in Gong changes.

What you end up with. The customer's words on a named call, attributed to the speaker and timestamped, without watching the recording.

Start with it bringing you the information and you deciding.

Never without. A transcript is a machine's account of a conversation. Names, product terms, and numbers are the words it gets wrong most often, so check any figure or commitment against the recording before quoting it to the customer.

Built on: Retrieve call data by date range v2 calls / Get Call By ID / Get Call Transcript / Retrieve filtered call details

Gong already runs keyword trackers across recorded calls, and the assistant can read which trackers exist, list the calls in a period, and pull transcripts to see the sentences around each mention. The question worth asking is not how many times a name came up. It is what the customer was doing at the moment they said it, which only the surrounding transcript answers.

What you end up with. The passages where a topic came up across a quarter of calls, quoted with the account and the date.

Start with it bringing you the information and you deciding.

Never without. Only calls Gong recorded are in this, so what you get is a pattern in the recorded set rather than in your pipeline. The deals that never got to a recorded call are the ones most likely to have been lost on the thing you are searching for.

Built on: Retrieve tracker details v2 settings trackers / Retrieve call data by date range v2 calls / Get Call Transcript / List Call Outcomes

Gong computes interaction statistics from calls where Whisper is enabled, including interactivity, question rate, longest monologue, and patience, and the assistant can pull yours for a date range and read them next to the transcripts they came from. Used on your own calls, the number is a prompt to go listen to the specific call where the monologue happened. That is where anything useful actually is.

What you end up with. Your own interaction figures for a period, with the specific calls behind the outliers named so you can go and listen.

Start with it bringing you the information and you deciding.

Never without. Never turn this into a ranking of your teammates. These figures move with deal stage, call type, and who else was in the room, and a rep running technical discovery will look worse on every one of them than a rep running a demo.

Built on: Get User By ID / Get Interaction Statistics / Retrieve call data by date range v2 calls / Get Call Transcript

It can list the Engage flow folders and the flows visible to a user, look up which flows a given set of CRM prospects are currently assigned to, and list the Engage tasks sitting against a person by status and action type. This is the check that stops two people from working the same contact from opposite ends, which is the most expensive form of duplicated effort in outbound.

What you end up with. A per-prospect view of which flows they are in and what outreach is already scheduled against them.

Start with it bringing you the information and you deciding.

Never without. Personal flows only show up for the user whose account you connected with, so what you see is your view of the flows rather than the company's. Someone else may still be running a personal sequence into the same contact.

Built on: List Flow Folders / List gong engage flows v2 flows / Get Flow Prospects / List Tasks

It can retrieve the public library folders, list the calls filed in a given folder, and pull the transcript for each one so you can check what a call actually contains before assigning it. Private and archived folders are deliberately not retrievable, so what comes back is the shared library rather than anyone's personal collection.

What you end up with. A named listening list from the library, each call with a short description of what happens in it and why it is worth an hour.

Start with it bringing you the information and you deciding.

Never without. Check what is in a library call before handing it to a new person. Library folders are curated for whoever built them, and a call filed as a good discovery example may also contain pricing or a customer detail you do not want repeated.

Built on: Retrieve library folders v2 library folders / List Folder Calls / Get Call Transcript / Get Call By ID

It can read who currently holds API-granted access to a call, grant individual access to named users, and remove access it previously granted. Gong is precise about the limits here, and they matter. Granting has no effect on someone who already has access another way, and the removal only reverses access given through this same API.

What you end up with. The named person able to open the specific call, with a written record of who was granted what and when.

Start with it doing the work and checking with you.

Never without. Never treat the removal as proof that access is gone. Gong states it can only remove access previously given by this API, so a person who also holds access through a permission profile or a share keeps it and the request still reports success.

Built on: Get user call access / Set User Call Access / Delete users from call access list

It can assign up to 200 CRM contacts or leads to a flow in one request, under a named flow instance owner who ends up holding the resulting to-dos, and it can unassign prospects from specific flows or from all of them. Both halves reach real people. The assignment queues outreach that will go out with someone's name on it.

What you end up with. The named prospects added to or removed from a flow, with the owning user and the flow named in writing.

Start with it doing the work and checking with you.

Never without. Confirm the exact prospect list and the flow instance owner with a person before it runs. Two hundred prospects per request means a wrong list is a wrong list at scale, and the to-dos land on a colleague who did not ask for them.

Built on: Get Flow Prospects / List gong engage flows v2 flows / Assign prospects to flow / Unassign Flows By CRM ID / List Tasks

There are two halves and both are worth running in order. The assistant can first show every element in Gong that references an email address or a phone number, including calls, email messages, meetings, and engagement events, and then erase all of it. Gong's own wording on the erase is direct: it permanently deletes all calls where the address appears as lead, contact, attendee, or speaker, the deletion is not immediate and may take several hours, and it cannot be undone.

What you end up with. A written inventory of everything Gong holds on that person before deletion, and the erasure submitted against exactly that inventory.

Start with it doing the work and checking with you.

Never without. Run the privacy lookup first and read the list, because erasing one person's email removes entire calls where they were merely an attendee, and those calls belong to your other customers too. Gong also instructs deleting the data from your CRM and email system beforehand so it is not re-imported afterward, and it says to contact support if the erasure fails rather than retrying it.

Built on: Retrieve data privacy info for email address / Data privacy for phone number / Erase data for email address / Erase data for phone number