Keep recordings beyond the retention period
You set recordings to be deleted automatically after a few months. With a daily recordings backup every audio file also lands in your archive before the portal deletes it.
Management
A copy of your phone system data on your own server, every day
Phone system backups copy the call log, queue calls, operator sessions, campaign calls and recordings to your FTP, FTPS or SFTP server or an S3 bucket, every day, week or month.
Daily backup · SFTP archive
- 02:00Start: period of 14 Oct 2026
- 02:002026/10/14/calls-2026-10-14-daily.csv · 1,284 rows
- 02:012026/10/14/queues-2026-10-14-daily.csv · 742 rows
- 02:04recordings: 318 recordings copied
- 02:04Succeeded · copied until 15 Oct 2026
What it is for
Backups keep a copy of your phone system data wherever you want it: on the company server, in your back office archive, in an Amazon S3 bucket or a compatible service. Useful for keeping your own archive, for loading the data into other systems or simply for having it in house too.
You choose what to copy: the log of every call, queue calls with waits and operators, operator logins and pauses, campaign calls with their lead, and the recording audio files. Data goes into CSV files that open straight in Excel; recordings go into a folder of their own.
Each period (day, week or month) is copied once it is over, at the hour you choose in your time zone. If a backup fails it is retried, and missed periods are caught up on the next run without copying the same data twice. You get an email at the first failure.
A backup is a copy: nothing is deleted from the platform. And if you delete a backup or a destination, the files already copied stay on your server.
Use cases
Load calls into your back office every morning
At 2 am the previous day’s call log arrives as CSV on your back office SFTP server, in a folder per year, month and day. Its import script picks it up before the office opens.
File operator attendance at month end
A monthly backup of operator sessions writes, on the first of each month, the file with the previous month’s logins and pauses, ready for HR.
An S3 archive for compliance
Recordings and campaign calls go every week to an S3 bucket (or Wasabi, Backblaze, MinIO, DigitalOcean) with the retention rules your IT team sets.
How it works
Add a destination
In Backups press New destination and choose FTP, FTPS, SFTP or Amazon S3 / S3 compatible. Enter server and credentials, or bucket and keys. On save the portal tries to write and delete a small test file.
Create the scheduled backup
Press New backup, give it a name, pick the destination, the frequency (daily, weekly or monthly) and the hour.
Choose what to copy and how
Tick call log, queue calls, operator sessions, campaign calls and recordings. Set the folders with {yyyy}, {mm}, {dd} and the CSV separator.
Let it run
Once the period is over, the files are written to the destination at the chosen hour. The list shows how far it has copied and the next run; Run now starts it straight away.
Check the log
The Log shows the latest runs with period, result and files written. If something goes wrong you get an email and the backup is retried.
What you can set
Destination
- Name
- How you recognise the destination.
- Type
- FTP, FTPS (FTP over TLS), SFTP or Amazon S3 / S3 compatible. Plain FTP sends passwords and data in clear: use SFTP or FTPS if the server allows it.
- Server and Port
- Address and port of the FTP, FTPS or SFTP server.
- Username and Password
- The sign-in credentials. Passwords stay encrypted and are never shown; leave empty to keep the saved one.
- SSH private key
- For SFTP, instead of or as well as the password, in OpenSSH or PEM format.
- Folder
- The folder on the server where backups are written.
- Bucket and Region
- For S3: the bucket name and its region, for example eu-south-1.
- Endpoint
- Empty for Amazon S3; for Wasabi, Backblaze, MinIO or DigitalOcean the service address.
- Access key and Secret key
- The bucket access keys; the secret key stays encrypted.
- Prefix
- For S3: the path inside the bucket to write to.
- Test
- Checks the connection at any time: the destination shows as Verified or Not reachable.
Scheduled backup
- Name and Destination
- What the backup is called and where it writes.
- Frequency
- Daily copies the previous day every day; Weekly the previous week (Monday to Sunday) every Monday; Monthly the previous month on the first of each month.
- Hour
- The hour it starts, in your time zone, once the period is over.
- Folders
- Subfolders under the destination folder, with {yyyy} year, {mm} month and {dd} day of the period. Empty puts everything in the same folder.
- CSV separator
- Semicolon, which opens directly in Excel set to Italian and many other European languages, or comma, the standard.
- Active
- While paused the backup does not run.
What to copy
- Call log
- Every call, inbound, outbound and internal, as CSV.
- Queue calls
- Wait, answer and operator of each queue call, as CSV.
- Operator sessions
- Operator logins and pauses, as CSV.
- Campaign calls
- Campaign calls with their lead, as CSV.
- Recordings
- The audio files of recorded calls, in the "recordings" folder, named after the call.
Runs and monitoring
- Copied until
- The date up to which data has been copied, and the next run.
- Run now
- Starts the backup at once without waiting for the scheduled hour.
- Catching up missed periods
- If a backup fails or stays paused, the next run copies every skipped period, with no duplicates.
- Retries
- A failed backup is retried, waiting longer each time.
- Email alert
- The account owner gets an email at the first failure, not at every retry.
- Log
- The latest runs with period, status (running, succeeded, failed) and files written.
- Status
- Each backup is Active, Paused or Failing.
Frequently asked questions
What does the phone system backup include?
Whatever you choose among call log, queue calls, operator sessions and campaign calls, as CSV files, plus the recording audio files.
Where can I store backups?
On an FTP, FTPS or SFTP server, or in an Amazon S3 bucket or an S3-compatible service such as Wasabi, Backblaze, MinIO or DigitalOcean.
How often does the backup run?
Every day, week or month, at the hour you choose in your time zone. Each period is copied once it is over.
What happens if my server is unreachable?
The backup is retried and you get an email at the first failure. When the server is back, the periods left behind are copied too.
Does a backup delete data from the portal?
No. A backup is only a copy: everything stays on the platform. Even if you delete a backup, the files already copied stay on your server.
Can I restore a backup into the portal?
No, a backup is a copy for your own archives and systems. The original data stays in the portal anyway, where you can view it and export it from the reports.
Related features
Try it on your own phone lines
Sign up free and try this feature with your numbers, or message us on WhatsApp and we’ll show it to you.