Chorus integration

What connects

The connection uses a Chorus API token generated in Chorus under Personal Settings → API Access. The token inherits the issuing user's visibility, so the account that creates it must be able to see the recordings that should be imported.

• A Chorus plan with API access is required for this connector.
• The connected user provides the API token and can reconnect it if Chorus rejects or revokes access.
• This is a token-based API connection for Chorus history; it does not provide live-call interception.

Information used

The inbound sync reads Chorus conversation records and, where available, transcript utterances embedded in each conversation's recording data. IntellaOne normalizes the available history into prior-conversation context.

• Conversation name, date, duration, participants, status, and recording URL where Chorus provides them.
• Transcript utterances with speaker name, speaker type or affiliation, timing, and text where the API returns them.
• The issuing Chorus user's visibility controls which calls and transcripts can be reached; a connected token is not a promise of workspace-wide coverage.
• Missing or unavailable transcripts remain a provider outcome rather than an invented transcript.

Why it is useful

Historical Chorus conversations can give a rep continuity around earlier participants, objections, commitments, and unresolved questions without requiring a manual search during the next conversation.

• Prior calls can add context before or during a later conversation.
• Transcript citations are grounded in the imported utterances rather than a claim that every Chorus recording has a transcript.
• This connector complements live guidance with history; it is not a live-call recording or interception path.

How the workflow behaves

The first sync looks back 90 days. Later syncs use a calls watermark with a short overlap, and scheduled runs continue incrementally rather than importing an unbounded history every time.

• A run follows Chorus cursor pagination and is capped at 30 list pages; an unfinished page window resumes from the saved cursor on a later run.
• Transcript retrieval uses a retryable backlog capped at 200 conversations per run. A provider failure leaves the item eligible for a later retry.
• Calls are deduplicated by the Chorus conversation ID, and a resync can replace transcript segments when Chorus has reprocessed them.
• Chorus is read-only in this integration: no calls, transcripts, or other records are written back to the provider.

Prerequisites and limits

Generate a Chorus API token under Personal Settings → API Access, use a Chorus plan with API access, and create it from a user whose Chorus visibility includes the recordings you want. API availability, rate limits, token state, provider processing, and transcript permissions can limit the imported history.

Availability still depends on the provider account, plan, permissions, and application setup; a catalog status is not a guarantee that every account can use every provider feature.

Security and privacy boundaries

Newly saved connector credentials are encrypted before storage.

Connected tools sync server-side under the user's own credentials. Requested permissions and data flows are connector-specific.

Availability still depends on the provider account, plan, permissions, and application setup; a catalog status is not a guarantee that every account can use every provider feature.

Chorus is an inbound, read-only history source here. The token's provider visibility determines what can be imported, and IntellaOne does not claim access to calls the token cannot see. Live-call audio interception is not part of this connector.

• Imported transcript text is processed and persisted server-side as part of IntellaOne's conversation context.
• No Chorus write-back or autonomous provider action is performed.
• A successful sync depends on Chorus accepting the token and returning the requested records; an API error is not treated as an empty history.

Frequently asked questions

What does beta mean for the Chorus integration?

Chorus is currently marked Beta in the integration catalog. The shipped path is read-only historical API access, so availability and transcript coverage still depend on Chorus API access, token visibility, and provider behavior.

Does Chorus import live calls?

No. The connector imports historical conversation records and available transcripts through the Chorus API. It does not intercept live calls or stream live call audio.

Are transcripts available for every Chorus call?

No. IntellaOne imports transcript utterances when Chorus returns them for a visible conversation. Missing, delayed, or permission-limited transcripts remain unavailable rather than being filled in.

How do I connect Chorus?

Generate an API token in Chorus under Personal Settings → API Access and provide it to the connector. The token inherits the issuing user's Chorus visibility.