Skip to main content

Export CSAT Dynamics and Interaction Intensity Dynamics values into separate columns

Update report export for CSAT Dynamics and Interaction Intensity Dynamics.

Currently, each summary is exported into a single Excel cell as a structured JSON-like value containing multiple individual metrics.

For analytical purposes, each value inside these summaries should be exported into its own separate column.

Current Behavior

CSAT Dynamics is exported as one column containing multiple values, for example:

  • enter_CSAT

  • exit_CSAT

  • peak_CSAT

  • other available CSAT Dynamics values

Interaction Intensity Dynamics is also exported as one column containing multiple values, for example:

  • enter_intensity

  • exit_intensity

  • peak_intensity

  • intensity_indicators

This makes further calculations and correlation analysis in Excel significantly more difficult.

Expected Behavior

Each individual metric contained in CSAT Dynamics and Interaction Intensity Dynamics should be exported as a separate report column.

Example structure:

CSAT Dynamics

  • CSAT Dynamics - Enter CSAT

  • CSAT Dynamics - Exit CSAT

  • CSAT Dynamics - Peak CSAT

  • separate columns for other available CSAT Dynamics fields

Interaction Intensity Dynamics

  • Interaction Intensity Dynamics - Enter Intensity

  • Interaction Intensity Dynamics - Exit Intensity

  • Interaction Intensity Dynamics - Peak Intensity

  • Interaction Intensity Dynamics - Intensity Indicators

The values should no longer require parsing a JSON structure from a single Excel cell.

Expected Result

Instead of:

CSAT Dynamics | Interaction Intensity Dynamics

containing structured data inside individual cells, the export should provide flat analytical columns that can be immediately used for:

  • formulas;

  • correlation analysis;

  • filtering;

  • pivot tables;

  • external reporting.

Acceptance Criteria

  1. Each CSAT Dynamics metric is exported into a separate column.

  2. Each Interaction Intensity Dynamics metric is exported into a separate column.

  3. Add a dedicated column to the report export - only if data present

  4. Values correspond to the correct conversation.

  5. Numeric values are exported as numeric values where applicable.

  6. Text values, such as intensity indicators, are exported into dedicated text columns.

  7. Missing values follow the existing export behavior for empty data.

  8. Exported fields can be used directly in Excel calculations without additional JSON parsing.

  9. Existing report filters and selected date ranges continue to apply to the exported data.

Status: Completed1 comment

Log in to comment and vote

Comments1

  • John

    Team•

    Sep 14

    Need to clarify, why it didnt move to Done, once linked Issue in Github marked as Done/Merged