Voxjar can connect with your existing FTP servers to download call recordings and metadata for quality assurance.

The connection allows Voxjar to download call recordings and metadata from your server on a schedule or when manually triggered.

You can create multiple FTP server connections by creating multiple integrations.

To create a new FTP integration, go to Settings>Integrations (app.voxjar.com/settings/integrations) and click on SFTP.

You'll need your FTP server url or ip address, port, username, and password. Ideally the username/password are unique to Voxjar.

The provided user must have permission to list and download files from your server.

Name this integration so you can identify it later; enter your url, port, and credentials; and click "check access".

Your FTP server must contain files to complete the connection tests. Voxjar has to verify that it can read and download those files.

After your connection has been tested, you'll need to provide the path to your audio files.

There are two supported conventions.

Option 2 is preferred if you do not purge your data on a regular interval. Otherwise the data build up could prevent Voxjar from completing a data pull within our 1 hour time limit.

Metadata lets Voxjar label your call recordings with standard and custom fields. This is useful for filtering results, identifying specific calls, linking calls to agents, and selecting which call recordings should be evaluated.

There are three options when you integrate your SFTP server:

For CSV and JSON file paths there are two supported conventions. The same as with audio file paths.

Option 2 is preferred if you do not purge your data on a regular interval. Otherwise the data build up could prevent Voxjar from completing a data pull within our 1 hour time limit.

Parsing metadata from your call recording file names is the simplest way to start if you don't have detailed metadata files.

Voxjar will extract metadata from your file names based on rules you set in the next step.

If you save your metadata in a CSV file you can provide the path to those files the same way you provide a path to your audio files.

Only 1 CSV file will be downloaded on every data collection run. That means that if you schedule data to be pulled every 7 days, all metadata for that 7 day period needs to be stored in a single CSV file.

Each row in a CSV metadata file should represent 1 call.

Voxjar will only download calls that are included in your CSV file and that match the rules you set in your Queues.

Your CSV file must contain a column that references the call recording's file name so Voxjar can link the data to the call. You do not need to provide the full call recording path in the CSV file since you have already provided that. Just the file name.

During set up, make sure that there is at least 1 CSV file with data at the path your provide so you can map your columns to metadata fields in Voxjar.

Any changes to your CSV columns could break this integration. When you make changes you will need to create a new integration and map the new metadata fields.

If you save your metadata as JSON files you can provide the path to those files the same way you provide a path to your audio files.

Each JSON metadata file should represent 1 call.

Voxjar will only download calls that have a matching JSON file and that match the rules you set in your Queues.

Your JSON file must contain a field that references the call recording's file name so Voxjar can link the data to the call. You do not need to provide the full call recording path in the JSON file since you have already provided that. Just the file name.

During set up, make sure that there is at least 1 JSON file with data at the path your provide so you can map your fields to metadata fields in Voxjar.

Any changes to your JSON fields could break this integration. When you make changes you will need to create a new integration and map the new metadata fields.

Metadata lets Voxjar label your call recordings with standard and custom fields. This is useful for filtering results, identifying specific calls, linking calls to agents, and selecting which call recordings should be evaluated.

There are three options for AWS S3:

​

Voxjar will parse as many CSV columns or JSON fields as it can from your provided files to give you flexibility in labelling your calls.

You can assign each one to a Standard or Custom Voxjar metadata field.

Custom metadata mapping uses the field or column name as the label in Voxjar and requires that you select a data type so Voxjar can treat it correctly.

Currently, only the String/Text type custom fields are used to filter your Queues.

Supported data types are:

The standard Voxjar fields are:

​