sFTP Integration

Principle

• You regularly upload audio files to an sFTP server accessible to Raisetalk
• Raisetalk regularly retrieves the files and analyzes them

Connection

• ➜ Provide the following information:
  • sFTP IP address or domain
  • Port
  • Username
  • Password
  • Base path (e.g.: /depot/audio/)

sFTP Deposit

• From the base path, you expose directories by date, for example: 20260211 or 2026_02_11
• You deposit files in the appropriate directories
• You indicate the desired import frequency for Raisetalk.

Files & Metadata

• Raisetalk can extract data from file names to build metadata (context data)
• Example: 2026_02_11_15_20_33_Jean-Pierre_Dupont_Entrant_478_0682316817_163.mp3
  • Jean-Pierre: advisor's first name
  • Dupont: advisor's last name
  • Entrant: channel
  • 478: advisor's extension
  • 0682316817: called line
  • 163: contact reason (requires providing a mapping matrix between the IDs on your recorder & Raisetalk labels)
• ➜ Provide the naming convention used, making sure that the agreed separator (_ in the example) cannot appear within any of the data fields.

On-the-fly User Creation

• Raisetalk can create advisors on the fly during conversation ingestion.
• ➜ Provide
  • The default team in which to place a user upon creation
  • A connector name, for example Recorder
  • An email creation format, mandatory.
  • Example: %firstname%.%lastname%@%domain%.com

Picking

• If desired, Raisetalk can limit the conversations to analyze at each execution:
  • as a % of provided conversations
  • as a maximum number of conversations per advisor

sFTP + CSV Integration

• If desired, you can choose to associate a CSV file defining the metadata for each call, in addition to or instead of metadata in the file name.
• Example:
  • File: 88fds22fq3zf44fds82s.mp3
  • In the CSV file, the row for this call could be:

• ➜ Provide:
  • the CSV structure,
  • the separator used (e.g.: ,, ;, ...)
  • the enclosure character (e.g.: ")
  • the rows to skip (generally only the first row containing headers)