Feature Requests

This feature previously allowed assigned collaborators (Followers, Managers, QA) to listen to call recordings on a file—vital for coaching, QA, and compliance. Its removal blocks day-to-day management, slows conversion, and forces error-prone workarounds; please restore limited, role-based access for users explicitly assigned to that file. What changed: Call recordings can no longer be played by assigned Followers, Managers, or QA within the CRM; only the primary caller (ISA/agent) can listen. Why it matters: Coaching & Performance: Managers must review real calls to coach tone, objection handling, and next-step setting. Without access, feedback becomes guesswork. QA & Compliance: Recorded calls are an auditable trail. Restricted access prevents QA checks for required disclosures, consent, fair-housing language, and script adherence. Pipeline Conversion: Fast call review enables quick course-corrections on live campaigns (lists, scripts, offers). Slower feedback = fewer appts, fewer listings. Operational Reality: ISAs/agents are often in power-dial sessions; asking them to export/re-upload files for every review is slow, manual, and breaks focus—reducing outbound volume. Requested solution (tight scope): Access model: Recordings playable by users explicitly assigned to the file (Owner ISA/Agent), Followers added to the file, Team Managers, and QA role. Controls: Only users already granted CRM access to the same file see/play the recording. Respect existing role permissions (view only; no delete unless already granted). Log each playback event (who/when/file/recording id) for audit. Optional org toggle: “Allow assigned Followers/Managers/QA to play recordings.” Security notes: This does not broaden global access; it enforces least-privilege at the file level, with audit trails. No external sharing required. Business impact (example metrics): +10–20% improvement in appointment set → kept, driven by rapid coaching on live campaigns. 100% reduction in manual export/re-upload workflow (minutes saved per call x hundreds of calls/day). Reduced compliance risk via routine QA spot checks. Faster ramp for new hires with real-call reviews. Workarounds are not viable: Exporting audio and re-uploading per file is slow, inconsistent, and creates fragmented data trails (and potential PHI/PII risk if files are mishandled). Urgency: High. Please restore with the guardrails above so managers and assigned followers can resume coaching/QA immediately.

I am trying to limit my phone calls per phone number to 50 each and then move on to my next phone number. Would love a way to automatically do that rather than manually checking back and forth, there is a spam protection feature but this allows us to cap the amount of calls per number and keep dialing seamlessly which would be great!

It'd be super helpful if you could copy and paste this info... currently I have to take a screen snip in several sections to copy the transcript over to chat gpt when I want to analyze a specific call structure for coaching/immediate feedback

Would love a "playback speed" button for when we listen to past recorded calls in the conversations.

I need the URL for each call recording to automate the process of listening and transcribing calls using AI. This feature would allow us to integrate with Go High Level and automate the call listening and scoring process. Without the URL, we can't transcribe the recordings as needed for our workflow.

I would like the ability to send call transcriptions directly to Go High Level. This feature would streamline our workflow by allowing us to manage transcriptions within our existing system, rather than manually downloading and uploading them.

Some dialers offer dialing up to 14 people at a time!

On the little modal telling you who you're dialing and their number, it would be helpful to have the current progress listed. If you're on 20/55 or 50/55 and near the end would be helpful information for our reps.

We make calls on behalf of several clients and would like to be able to register Spam Protection Caller ID for each of them and not have them all combined under the same business entity.