Cobl connects to Gong so the call ends and the next step goes out the same day, in the buyer's words: recap, proposal, RFP response.
Gong is a revenue intelligence platform that records, transcribes and analyses sales calls. Revenue teams use it to review conversations, coach reps, track deal risk and understand what buyers are actually asking for across a whole pipeline. On a complex opportunity it holds several calls, each with a different set of people in the room and a different part of the picture.
Gong captures the most useful input a response can have: the buyer describing their own problem, in their own words, in a level of detail they will never put in writing. That input usually stays inside the call review. When the questionnaire or the proposal gets written, someone works from memory or from a rushed set of notes, and the specifics that would have won the deal never reach the pages being scored.
Cobl reads the Gong transcripts you connect to a deal and carries them as context inside the deal workspace. Requirements, constraints and objections raised on a call inform the questionnaire response, the technical memo and the sales proposal, in the words the buyer used rather than in internal shorthand.
Several calls on one opportunity feed one workspace. Discovery, the technical deep dive and the commercial conversation each surface something different, and the document reflects all of them instead of only the one the writer happened to attend.
An enterprise opportunity has run through four calls: discovery with the business sponsor, a technical session with the architecture team, a security review and a commercial conversation. Four transcripts, four sets of participants, and one bid manager who sat in two of them. Rather than reconstructing the other two from someone else's notes, those transcripts are connected to the deal workspace. The evaluation and the go/no-go come out first, built on what was actually said about scope, budget and timing. The technical memo then draws on the architecture session directly, in the language the architect used to describe their own environment.
The objections raised live get answered in writing. A concern handled verbally in week two is the concern an evaluator weighs in week six, and it is usually the first thing to vanish from a document written from memory. What the team stops doing is rewatching calls to find the three details that matter. Nothing leaves the workspace until someone has approved it.
Cobl reads the transcripts you connect to a deal and uses them as context for every document in that workspace. The call stops being something you review after the fact and becomes the input the response is built on, which is what it was always worth.
Requirements and objections come through as the prospect phrased them rather than translated into internal vocabulary. Evaluators score answers they recognise, and the fastest way to be recognised is to use the words they used.
Discovery, technical and commercial conversations on the same opportunity inform the same document. Nothing raised early gets dropped later because a different person ran the later call and never heard it.
Call context combines with CRM data from Salesforce and internal discussion from Slack, while approved company material comes from the Shared Drive. The document reflects the conversation, the record and what has already been cleared.
Yes. Cobl connects to Gong so call transcripts can be used as context for proposals, questionnaire responses and technical memos. The transcripts you connect to a deal become source material for every document in that workspace, alongside your CRM records and your approved company content.
The call transcripts and the meeting metadata attached to the deal you connect. Cobl works from the transcript rather than the audio, and it does not need access to coaching scores, rep performance data or anything else Gong holds for internal review purposes.
Yes, and on complex opportunities that is the point. Discovery, technical and commercial calls each hold part of the requirement. Connected to the same deal workspace, they inform one document, so nobody has to reconcile four sets of notes by hand before writing starts.
No. The transcript is context, not copy. The agents use what the buyer described to decide what the document should argue, then write it in the register the document needs, drawing the supporting material from the Shared Drive.
Yes. Call context works alongside records from Salesforce, HubSpot or Pipedrive, so a document reflects both the conversation and the deal record. More on how data is handled sits on the security page.