# CRM Conversation Sync and Recordkeeping

Bring conversation summaries into your CRM. Understand the difference between CRM sync, transcript delivery and archiving native CRM records.

Source: https://commacompliance.com/crm-records-and-sync

---

CRM & Recordkeeping

# The conversation belongs beside the customer record.

Connect business communications to the CRM your team already uses. Keep the scope of your archive clear, too.

[See how your CRM connects](/get-in-touch)

## Put conversation context where your team works

A client conversation should not depend on someone remembering to copy it into the CRM. Comma’s outbound connectors match conversations to customer records and deliver summaries into the CRM. Matching rules, destination objects and supported fields depend on the provider.

HubSpot, Zoho CRM, Wealthbox, Slant, Close and Pipedrive have connector implementations. Connection and enablement are scoped to your organization. We confirm the setup path and supported behavior for your CRM during rollout.

Conversation summaries delivered into your CRM.

## Three requirements. Three different scopes.

| Your requirement | What to discuss with Comma |
| --- | --- |
| Bring conversation context into the CRM | Summary delivery, contact matching, supported last-touch fields and connection health. |
| Send conversation transcripts into the CRM | Separately enabled transcript delivery on selected connectors. Confirm provider support, length limits and destination visibility. |
| Archive records created inside the CRM | A separate archival requirement covering contacts, deals, notes, custom objects and change history. Outbound sync does not establish this coverage. |

## Configure delivery around your customer records

The connectors account for differences in how CRMs organize people and conversations. A contact, household and lead are different destinations. We establish the matching and visibility rules before delivery starts.

For supported connectors, historical delivery uses a preview before an administrator commits the run. Connection health and delivery exceptions help administrators identify work that needs attention. Creating missing contacts and delivering transcripts require their own configuration; neither should be assumed from connecting a CRM.

## Buying for records management?

Start with the records themselves. Specify the CRM, objects, attachments, change history, geography and retrieval requirements you need covered. We’ll distinguish implemented conversation delivery from any additional native CRM archival work required for your deployment.

For the sales workflow, see [Comma CRM](https://commacrm.com). For capture sources, explore [platform integrations](/platform-integrations). Meeting content has its own coverage considerations: [meeting recording archiving](/meeting-recording-archiving).

## Put your customer conversations to work.

Tell us which CRM you use and what your team needs to see in it. We'll walk through conversation delivery and any separate recordkeeping requirements.

[Book a CRM walkthrough](/get-in-touch)[Pricing](/pricing)