> ## Documentation Index > Fetch the complete documentation index at: https://docs.asapp.com/llms.txt > Use this file to discover all available pages before exploring further. # Transmitting Data to SFTP SFTP supports **one-time data transmissions**, typically for sending training data files during the implementation phase prior to initial launch. ASAPP customers can transmit the following types of training data via SFTP: * Conversation transcripts from messaging or voice interactions * Recorded call audio files * Free-text agent notes associated with messaging or voice interactions ## Getting Started ASAPP will require you to provide the following information to set up the SFTP site. * An SSH public key. This should use RSA encryption with a key length of 4096 bits. ASAPP will provide you a username to associate with the key. This will be of the form: `sftp` where the company marker will be selected by ASAPP. For example a username could be: `sftptestcompany` In your network, open port 22 outbound to sftp.us-east-1.asapp.com. ## Data File Formatting and Preparation **General Requirements:** * Encode files in UTF-8. * Escape control characters. * You may provide files as CSV or JSONL format, but we strongly recommend JSONL where possible. (CSV files are just too fragile.) * If you send a CSV file, ASAPP recommends that you include a header. Otherwise, your CSV must provide columns in the exact order listed below. * When providing a CSV file, you must provide an explicit null value (as the unquoted string: `NULL` ) for missing or empty values. ### Call Center Data File Structure The table below shows the required fields to include in your uploaded call center data.

FIELD NAME	REQUIRED?	FORMAT	EXAMPLE	NOTES
customer\_id	Yes	String	347bdddb-d3a1-45fc-bbcd-dbd3a175fc1c	External User ID. This is a hashed version of the client ID.
conversation\_id	No	String	21352352	If filled in, should map to ASAPP's system. May be empty, if the customer has not had a conversation with ASAPP.
call\_start	Yes	Timestamp	2020-01-03T20:02:13Z	ISO 8601 formatted UTC timestamp. Time/date call is received by the system.
call\_end	Yes	Timestamp	2020-01-03T20:02:13Z	ISO 8601 formatted UTC timestamp. Time/date call ends. Note: duration of call should be Call End - Call Start.
call\_assigned\_to\_agent	No	Timestamp	2020-01-03T20:02:13Z	ISO 8601 formatted UTC timestamp. The date/time the call was answered by the agent.
customer\_type	No	String	Wireless Premier	Customer account classification by client.
survey\_offered	No	Bool	true/false	Whether a survey was offered or not.
survey\_taken	No	Bool	true/false	When a survey was offered, whether it was completed or not.
survey\_answer	No	String		Survey answer
toll\_free\_number	No	String	888-929-1467	Client phone number (toll free number) used to call in that allows for tracking different numbers, particularly ones referred directly by SRS. If websource or click to call, the web campaign is passed instead of TFN.
ivr\_intent	No	String	Power Outage	Phone pathing logic for routing to the appropriate agent group or providing self-service resolution. Could be multiple values.
ivr\_resolved	No	Bool	true/false	Caller triggered a self-service response from the IVR and then disconnected.
ivr\_abandoned	No	Bool	true/false	Caller disconnected without receiving a self-service response from IVR nor being placed in live agent queue.
agent\_queue\_assigned	No	String	Wireless Sales	Agent group/agent skill group (aka queue name)
time\_in\_queue	No	Integer	600	Seconds caller waits in queue to be assigned to an agent.
queue\_abandoned	No	Bool	true/false	Caller disconnected after being assigned to a live agent queue but before being assigned to an agent.
call\_handle\_time	No	Integer	650	Call duration in seconds from call assignment event to call disconnect event.
call\_wrap\_time	No	Integer	30	Duration in seconds from call disconnect event to end of agent wrap event.
transfer	No	String	Sales Group	Agent queue name if call was transferred. NA or Null value for calls not transferred.
disposition\_category	No	String	Change plan	Categorical outcome selection from agent. Alternatively, could be category like 'Resolved', 'Unresolved', 'Transferred', 'Referred'.
disposition\_notes	No	String		Notes from agent regarding the disposition of the call.
transaction\_completed	No	String	Upgrade Completed, Payment Processed	Name of transaction type completed by call agent on behalf of customer. Could contain multiple delimited values. May not be available for all agents.
caller\_account\_value	No	Decimal	129.45	Current account value of customer.

Full	Abbreviated
Agent: Choose an option from the list below Agent: (A) 1-way ticket (B) 2-way ticket (C) None of the above Customer: (A) 1-way ticket	Agent: Choose an option from the list below Customer: (A)

Full

Abbreviated

Agent: Choose an option from the list below

Agent: (A) 1-way ticket (B) 2-way ticket (C) None of the above

Customer: (A) 1-way ticket

Agent: Choose an option from the list below

Customer: (A)

#### 2. Provide the Public Key to ASAPP Save the public and private key. Only send the public file for your key pair to ASAPP. This is not a secret and can be emailed. #### 3. Upload Files Use an SFTP utility such as Cyberduck (available from [Cyberduck](https://cyberduck.io/) ) to upload files to ASAPP. Click **Open Connection**, add sftp.us-east-1.asapp.com as the Server, and add `sftpcompanymarker` as the Username. Choose the private key you generated in step 2 as the SSH Private Key and click **connect**. The following screenshots show how to do this using Cyberduck.

A pop-up window appears. Click to allow the unknown fingerprint. You will then see the `in` and `out` directories.

Double click the `in` directory and click **Upload** to choose files to send to ASAPP. ### Mac/Linux Users If you are using a Mac or Linux, follow the steps below: #### 1. Generate an SSH Key Pair If you are using a Mac or Linux, you can generate a key pair from the terminal as follows. If you already have an `id_rsa` file in the `.ssh` directory that you use with other applications, you should specify a different filename for the key so you do not overwrite it. You can either do that with the `-f` option or type in a `filename` when prompted. `ssh-keygen -t rsa -b 4096 -C sftp; -f filename` For Example: `ssh-keygen -t rsa -b 4096 -C sftptestcompany -f keyforasapp` Where the filename will be the name of two files generated - `filename` (the private key you must keep to yourself) and `filename.pub` (the public key which ASAPP needs) If you do not have an `id_rsa` file in the `.ssh` directory, you can go with the default filename of `id_rsa` and do not need to use the `-f` option. `ssh-keygen -t rsa -b 4096 -C sftp` #### 2. Provide the Public Key to ASAPP Send the `.pub` file for your key pair to ASAPP. This is not a secret and can be emailed. #### 3. Upload Files You can upload files using the terminal or you can use [Cyberduck](https://cyberduck.io/). This section describes how to upload files using the terminal. To login to the ASAPP server, type one of the following: If you used the default id\_rsa key name: `sftp sftp@sftp.us-east-1.asapp.com` If you specified a different filename for the key: `sftp -oIdentityFile=filename` `sftp sftp@sftp.us-east-1.asapp.com` For Example: `sftp -oIdentityFile=keyforasapp` `sftptestcompany@sftp.us-east-1.asapp.com` You will see the command line prompt change to `sftp>` If the `sftp` command fails, adding the `-v` parameter will provide logging information to help to diagnose the problem. Use terminal commands such as `ls, cd, mkdir` on the remote server. * `ls:` list files * `cd:` change directory * `mkdir`: make a new directory `ls` will show two directories: `in` (for sending files to ASAPP) and `out` (for receiving files from ASAPP). To create a transcripts directory on the remote machine to send transcripts to ASAPP, type: ```json theme={null} cd in mkdir transcripts cd transcripts ``` To navigate on the local machine, prefix terminal commands with l * `lcd`: change the local directory * `lls`: list local files * `lpwd`: to see the local working directory Use `get` (retrieve) and `put` (upload) to transfer files. `get` will fetch files from the remote server to the current directory on the local machine. For example: `get output.csv` will transfer a file named output.csv from the remote server. `put` will transfer files to the remote server from the current directory on the local machine. Navigate to local directory with transcripts and type: `put transcripts.csv` will transfer a file named transcripts.csv to the remote server. or `put *` will transfer all files in the local directory. or `put -r ` works recursively and will transfer all files in the local directory, all sub directories, and all files within them to the remote machine. For example: `put -r sftptest` will transfer the sftptest directory and everything within it and below it from the local machine to the remote machine. To end the SFTP session, type `quit` or `exit`.