ChatSummary

  • Your organization's address on the channel.

  • The channel the chat runs on.

    values
    smswebemail
  • the date-time notation as defined by RFC 3339, section 5.6, for example, 2017-07-21T17:32:28Z

  • The person's address on the channel.

  • Where a chat run is in its life. After the conversation ends, a chat that started waits in post_processing while Resia writes its analysis; then it ends completed (the agent ended it) or cancelled (you cancelled it). failed means the chat never started.

    values
    pendingactivepost_processingcompletedfailedcancelled
  • the date-time notation as defined by RFC 3339, section 5.6, for example, 2017-07-21T17:32:28Z

  • The end-of-chat analysis, present once the chat has ended and Resia has written it. Null while the chat is open or post_processing, for a chat that never started, and when no analysis that fits the Chat Agent's analysis_schema could be written.

    Properties: 1
  • The database selected for this chat, or null when none was usable.

  • the date-time notation as defined by RFC 3339, section 5.6, for example, 2017-07-21T17:32:28Z

  • The stage this chat last reported, or null when it has reported none. One of the names its Chat Agent version declared in milestones.

  • When the conversation started: on sms, when the carrier confirmed delivery of the first text or the person first replied, whichever came first; for a chat the person started by texting your number, when that text arrived; on web, when the agent's first message was stored. Null while the chat is pending, and for a chat that ended before it started.

  • Open key/value labels on this record. Set any keys and any values. Filter a list by one key and value pair. Resia never interprets a tag. Do not put names, phone numbers, or any personal, health, credential, or secret information in a tag: a tag travels in URLs when used as a filter, and URLs appear in ordinary infrastructure request logs.

    Properties: 1