Find the call in the surrounding conversation
A customer discussion can move between messages, calls and voicemail. Comma’s Quo connector brings supported records from the workspace into the communications archive, so reviewers can follow the activity without treating the phone system as a separate investigation.
The connector requires team enablement. We’ll confirm the connection, available source content and rollout scope for your workspace before activation.
Match the archive to the records Quo provides
| Record type | What the connector supports |
|---|---|
| Call details | Inbound and outbound call records with participants, direction, status, duration and timestamps. |
| SMS | Inbound and outbound text messages associated with their conversation. |
| Voicemail | Voicemail records with audio and Quo-provided transcripts when available from the source. |
| Call recordings | Source-available recordings where recording is enabled in Quo. The current connector retrieves the first recording segment, not every segment of a multi-part call. |
| Call transcripts | Quo-provided transcripts when available to the workspace and supported by the connection. The connector does not generate a substitute transcript when Quo provides none. |
| MMS media | Media supplied with supported message events. Media missed by that delivery path is not recovered by the current text-message reconciliation path. |
A call record does not establish that its audio or transcript was available. Review the record types you need, including any multi-segment recordings, before relying on a particular collection.
Connect at the workspace level
A team administrator connects an enabled Quo integration using a workspace API key. The connector receives supported events and runs a daily reconciliation of recent records. No modified Quo client is required.
We’ll check the workspace’s capabilities and recording settings with you. Confirm the intended scope during rollout; the displayed capture-surface switches do not currently limit ingestion.
Establish the history and coverage you need
New connections receive supported events from activation, with a daily reconciliation covering the preceding two days. Older history requires a separate, operator-run import assessment; connecting the workspace does not automatically import its full history.
Quo’s AI call summaries, message edits and deletions, and internal team comments are not covered by this connector. Group texts also have participant-mapping limits. Include those requirements in the evaluation if they matter to your review.
Quo archiving questions
Does Quo capture include more than calls?
Does each call include a recording and transcript?
Can we connect our workspace immediately?
Will connecting import all our earlier records?
What does the screenshot show?
Bring your Quo records into the review.
Tell us which calls, messages and voicemail your team needs to find. We'll walk through source coverage and your workspace's rollout requirements.
Related reading