Integration · Data & Reporting

Call Recording Cloud Storage in Your Own AWS, Google Cloud or Azure

Push call recordings and logs to storage buckets you own, so retention, access and data location follow your rules rather than a vendor's.

  • AWS, Google Cloud or Azure
  • Recordings and call logs
  • Your retention and access rules

How it works

What the cloud storage integration does

Recordings are an asset and a responsibility. Keep them where you control them.

Use your own bucket

Deliver recordings and call logs to your AWS, Google Cloud or Azure storage account.

Link media to the call

Each recording keeps a reference to the call, agent, campaign and contact.

Set retention and access

Your team defines how long recordings are kept, who can retrieve them and how they are deleted.

Plan data location

Choose storage regions around your regional and regulatory obligations.

Workflow

How recordings reach your storage

From a recorded call to a file in your bucket.

  1. 1

    Call recorded

    A call is recorded in Dialog where recording is enabled.

  2. 2

    File delivered

    The recording is pushed to your storage account.

  3. 3

    Reference kept

    The call record points to the stored file.

  4. 4

    Policy applied

    Your retention and access rules govern the file.

Cloud storage questions

Where are call recordings stored with Dialog?

You can deliver call recordings to cloud storage you own on AWS, Google Cloud or Azure. The destination, region and access model are scoped during implementation.

Who controls recording retention?

You do. Retention periods, access rights and deletion processes are set by your organisation in your own storage account.

Does storing recordings make us compliant?

Storage is one part of it. Consent, notification, security and industry rules remain your responsibility, so involve your compliance advisers.

Keep recordings in your own cloud

Tell us which systems, fields and events you need, and we will scope the workflow with your team.

Scoped with your team · API v2.2 · Webhooks