The Request:

Please add the call recording audio file URL as an available custom value when the "Transcript Generated" workflow trigger fires for LC Phone calls.

Current Situation:

The Transcript Generated trigger currently passes useful data — Call SID, duration, direction, timestamps, contact info, and the transcript text — but it does not expose the actual recording audio file URL. This means there is no way to access the recording file itself from within a workflow.

Why This Matters:

The native GHL transcription quality for LC Phone calls is not accurate enough for business-critical use. Many users (myself included) have found that third-party transcription tools like OpenAI Whisper, AssemblyAI, or Deepgram produce significantly more accurate results. However, because the recording URL isn't available in the trigger, there is no way to build an automated workflow that:

Detects a completed call

Sends the recording audio to a higher-accuracy transcription service

Processes the result (e.g., AI summary, CRM update, conversation thread entry)

This forces users into either accepting inaccurate transcripts or doing manual workarounds — neither of which is acceptable for a professional automation workflow.

What We're Asking For:

Simply include the recording file URL (e.g., {{trigger.recording_url}}) as an available custom value in the Transcript Generated trigger — the same way the transcript text is already available as {{full transcript}}.

The Impact:

This single addition would unlock a complete post-call automation pipeline for LC Phone users — accurate AI summaries, CRM enrichment, contact updates, and more — all without leaving the GHL ecosystem or needing a developer to build a custom integration.

This is a small change on the platform side with an outsized impact on usability for anyone doing sales or consultation calls.