Your Chorus calls, put to work

A Chorus user who can see all recordings, because a key sees only what its user can see. A Chorus admin turns on API access for that user's role under roles and permissions, and the user creates the key in Personal Settings. API access depends on your Chorus plan. If Personal Settings shows no API access option, ask your Chorus customer success manager for the key. Each person who adds their own key needs a role with API access too.

Each person who adds their own Chorus key sees only the calls they can see in Chorus, in chat answers and in daily reports. A person without their own key sees nothing from Chorus, unless your admin gives them access to the workspace's calls. The admin who connects Chorus, and the Chorus user whose API key they connect, also see the workspace's calls. None of that access includes private calls, so private calls stay private. Someone who loses access to a call in Chorus also loses the reports that include it. When Chorus marks a call private later, Coworker deletes the call's text and leaves the call out of new reports. Earlier reports that include a call that turns private or is deleted close to everyone.

Each meeting and dialer call that Chorus records, with its summary, action items, transcript, trackers and participants, plus scorecards, shared moments and playlists. Coworker keeps a copy of that text to write its reports, and it never downloads audio or video. In chat, Coworker can also look up a call's sales qualification notes.

No. Coworker only reads from Chorus. It never adds, changes or deletes anything there, and Chorus keeps recording your calls the way it does today.

Chorus records each call, transcribes it and writes its summary and action items. Coworker reads that work and builds on it: a daily report for each person and each customer account, a view of who on your team talks with each account, and answers about your calls in chat.