A searchable library of every sales call your team records

Transcribe your recorded calls once, then search every conversation your team has had and jump straight to the moment someone said it.

App
Azure AI SpeechGoogle DriveHubSpotSalesCustomer SupportMeeting WorkflowsDocument Processing
PromptCreate

I want a searchable call library app where my sales and support teams go to find what was actually said on past calls. It is built on Google Drive, where our recordings already live, Azure AI Speech for transcription, and HubSpot for filing summaries. This is a library people open and browse, not something that runs on a schedule. Nothing should be processed unless a person asks for it.

The landing view is the recording list. Use the Google Drive List Files operation to read our call folders, and show each recording as a row with the call date, the duration, the file name, and a transcription status badge that reads either Transcribed or Not transcribed. Anything not transcribed yet gets a Transcribe button on its row. Let the user pick which Drive folders count as call folders, and let them add more folders later.

When someone clicks Transcribe, the handler pulls the audio with the Google Drive Download File Content operation and runs the Azure AI Speech Fast Transcribe Audio operation with speaker diarization turned on, so speakers come back separated. Fast Transcribe Audio is the right operation here because it handles files up to two hours and 200 MB synchronously and supports diarization. Do not use Recognize Short Audio, which caps at 60 seconds. Show clear progress while a transcription is running, and flip the badge to Transcribed when the text has been stored.

Opening a call gives a transcript reader. Show the transcript as speaker labelled blocks with a timestamp on each block so it reads like a conversation rather than one undivided block of text. Beside the transcript, show an AI generated summary of that call broken into topics discussed, objections raised, and commitments made by either side. Generate the summary once when the transcript is first stored and save it with the call, so reopening a call is instant.

The most important view is search across every stored transcript at once. A rep types something like pricing objection or a competitor name and gets every matching call back, each result showing the call name and date with the surrounding quote and the matched phrase highlighted inside it. Let them filter results by date range and by folder. Clicking a result opens that call and jumps straight to that moment in the transcript with the matching passage in view. Search has to feel instant, so it runs against the transcripts already stored in the app and never goes back out to Google Drive or Azure to answer a query.

From an open call, the user can choose to push the summary into the CRM. Find the right person with the HubSpot Search Contacts operation, let the user confirm which contact is correct, then file the summary with the HubSpot Create Note operation associated to that contact. This only ever happens when the user chooses it. Never file calls to HubSpot automatically or in bulk. Show which calls have already been filed so nobody files the same summary twice.

Two persistence rules matter throughout. Store every transcript and its summary in the app once, keyed to the Drive file, so search is instant and the text survives independently of Azure. This matters because Azure batch transcription result files expire, so the transcript text must live in the app rather than being re-fetched. And never transcribe the same recording twice. Before offering a Transcribe button, check whether a stored transcript already exists for that file, and reuse it if it does.

What does this prompt do?

  • Lists the call recordings sitting in your Google Drive call folders with the date, length, file name and a badge showing whether it has been transcribed yet
  • Turns any recording into a readable transcript with each speaker separated and timestamped, next to a summary of the topics, objections and commitments from that call
  • Searches across every stored transcript at once, so typing a competitor name or a phrase like pricing objection surfaces every call that mentions it with the surrounding quote highlighted
  • Lets a rep file a call summary onto the right person in HubSpot when they decide it belongs there, instead of pushing every call into the CRM automatically

What do I need to use this?

  • A Google Drive account with your call recordings saved in one or more folders
  • A Microsoft Azure account with the Speech service enabled
  • A HubSpot login, if you want to file call summaries to your CRM
  • Recordings of up to two hours each, in a standard audio format

How can I customize it?

  • Choose which Google Drive folders count as call folders, and add more as your team grows
  • Change what the summary pulls out of each call, such as topics, objections, commitments or agreed next steps
  • Adjust the search filters, including the date range and which folders are included in results

FAQs

Will the same recording ever be transcribed twice?
No. Once a call has been transcribed, the full text is stored inside the app and reused everywhere it appears. The library checks what is already stored before it offers to transcribe anything, so you never pay to process the same recording again.
Can it tell who said what on the call?
Yes. Speaker separation is turned on for every transcription, so the reader shows each speaker as a separate labelled block with timestamps rather than one undivided wall of text.
How long can a recording be?
Each file can be up to two hours long and up to 200 MB, which covers the overwhelming majority of sales and support calls. Longer recordings should be split before they are added to the folder.
Does it push everything into HubSpot automatically?
No, and that is deliberate. Filing to HubSpot is a manual choice made from an open call. You pick the contact and confirm before a note is created, so your CRM only gets the summaries your team actually wants there.
Does this run on a schedule in the background?
No. This is a library you open and work in. Transcription starts when someone clicks Transcribe, and search runs when someone types a query, so nothing is processed unless a person asks for it.
How fast is the search?
Search is instant because it runs against the transcripts already stored in the app rather than going back out to Google Drive or Azure. The slow step is transcribing a call, and that only ever happens once per recording.

Related templates

Prospecting desk that builds account lists from the live web

Stop buying stale lists. Reps run a saved search, work the results like an inbox, and only the accounts they approve ever reach your CRM.

Hyperbrowser
HubSpot
Google Sheets
App
Plan a field sales day around drive time and neglected accounts

Pick a date, a starting point and a radius, then build a sequenced day of customer visits that lands straight on your calendar.

Geolocation
HubSpot
Google Calendar
App
Find ICP accounts, verify the emails, file them in HubSpot

One screen where reps filter for companies that fit, see who is actually reachable at each account, and save only the addresses that verify.

Hunter
HubSpot
App
Competitive battlecard workspace ranked by open pipeline

See every competitor battlecard next to the number of open deals that name that competitor, so the cards carrying real pipeline get refreshed first.

Guru
HubSpot
Slack Bot
App
Account coverage board that shows where you are single threaded

Score every target account against the buying committee you actually need, see the exact holes, and have an assistant fill them in your CRM.

Hunter
HubSpot
App
Turn Google Drive scripts into narrated audio, line by line

One desk to pull scripts from Drive, give every line its own voice, redo the one take that missed, and share approved audio in Slack.

Hume
Google Drive
Slack Bot
App

Every call your team recorded, finally searchable.

Stop paying a separate vendor just to find out what was actually said on a call you already recorded.