Uploading conversations
#
CSV formatThis format is useful if you have bi-directional conversations (i.e.: client & agent interactions_) that contain one or more utterances per conversation. The format consists of a CSV file in which each line contains 4 columns delimited by comma describing a single utterance that is part of a conversation.
#
Columns- Column 1: A unique identifier of the conversation. If the conversation contains multiple utterances, the utterances should share the same identifier
- Column 2: The date at which the utterance was made by the client or expert. This date should be a Unix epoch timestamp with millisecond precision.
- In Excel, you can use the following formula to convert a date to the proper format:Â
=(A1-DATE(1970,1,1))*86400000
. Example: 08/27/2020 at 5:28pm should have value 1598549339000
- In Excel, you can use the following formula to convert a date to the proper format:Â
- Column 3: The source is the person who did the utterance in a conversation. This value must be set to either client or expert
- column 4: The utterance text
#
Example#
Humanfirst JSON formatHere's an example of conversations defined in our JSON format. Consult the JSON format documentation for more details and advanced capabilities.
Notice the use of context.context_id
in each example, this is the conversation id used to group these examples into a single conversation.
The conversation message order is determined by the created_at
timestamp.
#
Example#
GzippingAll supported formats can be uploaded as gzipped files (.gz).