Ringura
Sign in Book a demo

Integrations

Deliver call recordings to your CRM as files

Keep each call recording on the call record in your CRM: what each CRM supports, and what stops applying once a file is there.

Last checked For: Administrators

Steps

  1. Know what it does

    Off by default. When it is on, each connector you switch on receives the call recording as a file on the call or activity record. A signed link that expires goes instead where the CRM cannot take the file. This has not been tried against a real CRM account yet: it has run against test doubles built from each CRM's published API reference. Try it on a test record first.

  2. Know what stops applying

    A file in your CRM is your own copy. Our retention periods, consent withdrawals and erasures do not reach it, so you delete it in the CRM. Add your CRM to your own retention and erasure procedures before you switch this on.

  3. Check what your CRM supports

    HubSpot: a private file attached to the call record, up to 100 MB. Salesforce: a File published to the call Task, up to 100 MB. Zoho CRM: the attachments of the Calls record, up to 20 MB. Pipedrive: a file tied to the call activity, up to 50 MB. Zendesk: attached to the ticket in an internal note, up to 50 MB. Generic and back-office connectors cannot take a file and get the signed link.

  4. Switch it on for the account

    Open CRM write-back. Under Recording files in your CRM, tick Allow recording files to go to CRMs for this account.

  5. Switch it on per connector

    On each connector, tick Deliver the recording file to this CRM and save. For HubSpot and Zoho CRM, connect the connector again afterwards so that the CRM grants the extra access.

  6. Check the deliveries

    The deliveries table under the connectors shows each call with its Status: Queued, Sending, Delivered, Signed link sent instead or Not sent, with a Reason. Choose Try the file again on a call that got a link or was not sent, for example once a connector has the extra access.

Good to know

  • Both switches and the contact's recording consent are read again before each file is sent. A contact who withdrew consent before that gets no file: the delivery shows Recording consent withdrawn.
  • A file larger than the CRM takes gets the signed link instead. A signed link never outlives the recording's retention.
  • Revoke recording links stops the links a connector received. It does not remove a file already in the CRM.
  • Every outcome is written to the audit log.
  • The recording stays in Ringura as well, under your retention settings.

Still stuck?

Write to hello@ringura.com, or use the contact page, and say which guide you were following.

ContactHelp centre