Why Did CSAT Change

Sign Up To Add

Explain why CSAT moved, with the conversations behind the change.

Why Did CSAT Change Explain why CSAT moved, with the conversations behind the change.

Compares CSAT across time periods, isolates shifts by theme and channel, and links the conversations behind the movement.

Example insight report

CSAT dropped because delivery-delay contacts changed mix

The analysis isolates delivery-delay and billing-verification contacts as the biggest detractor sources, then links back to the conversations behind the shift.

CSAT movement
Critical
-0.4 pts
vs prior week
Detractor contacts
Warning
173
+39%
CSAT drag
DeliveryBillingReturnsOther

Includes

Zendesk

Connector

Reads tickets, macros, CSAT, escalations, and support history from Zendesk.

Gorgias

Connector

Reads ecommerce support tickets, customer history, and macros from Gorgias.

Gladly

Connector

Reads customer conversations, tasks, and support history from Gladly.

Dixa

Connector

Reads customer support conversations, queues, and handoffs from Dixa.

Snowflake

Connector

Adds warehouse-backed customer, operational, finance, and product data from Snowflake.

Slack

Connector

Reads team channels, standups, escalation threads, and handoff conversations from Slack.

Shopify

Connector

Adds order, customer, product, fulfillment, and ecommerce context from Shopify.

Stripe

Connector

Adds payments, subscriptions, invoices, disputes, and revenue context from Stripe.

Information

Category
Built by Applied Labs, CX, Operations, Analytics
Capabilities
Interactive, Read, Write, Notify
Developer
Applied Labs
Website
Privacy Policy
Terms of service