VIEW_CASE_SUMMARY
Updated
The Omnichannel Case Summary view provides a single, consolidated record per case across all channels. It includes case identifiers, creation and closure details, participating agents, response counts, first and average response times, and overall case KPIs.
This view serves as a central case-level dataset for customer experience and operational analysis. Teams often use this as a base table for executive reporting and holistic case analysis.
Below are some of the scenarios where this Report is beneficial:
Omnichannel Case Performance Analysis: Analyze case volumes, response times, closure durations, and overall case KPIs across all channels to measure service performance and customer experience.
Executive and Operational Reporting: Use a consolidated case-level view to create dashboards and reports that track case trends, agent participation, resolution efficiency, and business outcomes.
Customer Experience and Journey Insights: Track the complete lifecycle of cases, including customer interactions, agent involvement, and response patterns, to identify opportunities for improving service quality and operational effectiveness.
Field Mapping/ Glossary
The report will include the following information:
Field Name
|
Description
|
Data Type
|
Nullable/Default
|
PII Field
|
Unique Key
|
ACCOUNT
|
Identifier of
|
VARCHAR
|
NO
|
No
|
|
ALL_ENGAGED_AGENTS
|
Comma-separated
|
VARCHAR
|
YES | NULL
|
No
|
|
ALL_RESPONDED_AGENTS
|
Comma-separated
|
VARCHAR
|
YES | NULL
|
Yes
|
|
ASSOCIATED_BRAND_MESSAGE_COUNT
|
Total number of
|
NUMBER
|
YES | NULL
|
No
|
|
AVERAGE_CASE_RESPONSE_TIME
|
Average response
|
NUMBER
|
YES | NULL
|
No
|
|
BRAND_MESSAGE_COUNT
|
Total number of
|
NUMBER
|
YES | NULL
|
No
|
|
CASE_ASSOCIATED_CUSTOMER
|
Identifier of
|
VARCHAR
|
YES | NULL
|
Yes
|
|
CASE_ASSOCIATED_MESSAGE_COUNT
|
Total number of
|
NUMBER
|
YES | NULL
|
No
|
|
CASE_BRAND_RESPONDED_FLAG
|
Indicator
|
BOOLEAN
|
YES | NULL
|
No
|
|
CASE_CLOSURE_DURATION
|
Total time taken
|
NUMBER
|
YES | NULL
|
No
|
|
CASE_CLOSURE_TIMESTAMP
|
Timestamp
|
TIMESTAMP
|
YES | NULL
|
No
|
|
CASE_NUMBER
|
Unique
|
VARCHAR
|
NO
|
No
|
Yes
|
CASE_TOTAL_RESPONSE_TIME
|
Total response
|
NUMBER
|
YES | NULL
|
No
|
|
CHANNEL_TYPE
|
Channel through
|
VARCHAR
|
NO
|
No
|
|
CREATED_TIME
|
Timestamp
|
TIMESTAMP
|
NO
|
No
|
|
CURRENT_PREDICTED_CSAT_SCORE
|
Latest predicted
|
NUMBER
|
YES | NULL
|
No
|
|
FIRST_ASSOCIATED_CUSTOMER_MESSAGE_TIME
|
Timestamp of the
|
TIMESTAMP
|
YES | NULL
|
No
|
|
FIRST_ASSOCIATED_USER_BRAND_MESSAGE_CREATED_TIME
|
Timestamp of the
|
TIMESTAMP
|
YES | NULL
|
No
|
|
FIRST_ASSOCIATED_USER_BRAND_MESSAGE_TIME_EXCLUDES_IMPORT
|
Timestamp of the
|
TIMESTAMP
|
YES | NULL
|
No
|
|
FIRST_BRAND_RESPONSE_TIMESTAMP
|
Timestamp of the
|
TIMESTAMP
|
YES | NULL
|
No
|
|
FIRST_CASE_RESPONSE_DURATION
|
Time taken to
|
NUMBER
|
YES | NULL
|
No
|
|
INITIAL_PREDICTED_CSAT_SCORE
|
Predicted CSAT
|
NUMBER
|
YES | NULL
|
No
|
|
IS_BRAND_RESPONDED
|
Flag indicating
|
BOOLEAN
|
YES | NULL
|
No
|
|
IS_USER_BRAND_RESPONDED
|
Flag indicating
|
BOOLEAN
|
YES | NULL
|
No
|
|
LATEST_ASSOCIATED_BRAND_MESSAGE_TIME
|
Timestamp of the
|
TIMESTAMP
|
YES | NULL
|
No
|
|
LATEST_ASSOCIATED_CUSTOMER_MESSAGE_TIME
|
Timestamp of the
|
TIMESTAMP
|
YES | NULL
|
No
|
|
ROUTED_TO_AGENT_FLAG
|
Indicator
|
BOOLEAN
|
YES | NULL
|
No
|
|
STATUS
|
Current status
|
VARCHAR
|
NO
|
No
|
|
TIMESTAMP_SINCE_CASE_WAS_CREATED
|
Time elapsed
|
NUMBER
|
YES | NULL
|
No
|
|
Intended Use and Prohibited Uses
DataStream is intended solely to support operational efficiency, service delivery, business intelligence, and process optimisation. The product is not designed or intended for employee monitoring, workplace surveillance, performance evaluation, profiling of individuals, or making decisions that materially affect an individual's employment, rights, opportunities, or access to services.
DataStream does not process biometric data for the purpose of identifying individuals and does not perform emotion recognition, affect detection, or emotion inference in the workplace.
Customers must not use DataStream in a manner inconsistent with these intended purposes and remain responsible for ensuring compliance with applicable legal and regulatory requirements as well as with Sprinklr's Acceptable Use Policy.