C4UChat4U Docs
Integrations

Social insights and metrics

Measure customer-message activity, team handoffs, and time to the first human reply without confusing handoff share with resolution.

3 min read

Where to do this in Chat4U
  1. Project
  2. Insights

Select the date range and assistant, then review Social metrics in Summary or Answer quality and open conversation evidence.

Look forSummaryAnswer qualityDate rangeAssistant scopeRefresh
Open Chat4U
What you’ll accomplish

Use Overview and Handoffs for current work. Use Insights to understand historical channel demand and your team's handoff workload.

Finish with
Social measurements interpreted with their dates, scope, and conversation evidence

Where to look

AreaUseful for
OverviewCurrent conversations needing takeover and customers waiting while your team controls the chat
HandoffsOpening those conversations, taking over, and sending or checking replies
Insights → SummaryHistorical Social conversation volume, team involvement, and volume by channel
Insights → Answer qualityFirst human reply time, unanswered handoffs, channel counts, and recorded handoff reasons

Social measurements sit alongside the project's other insights. They do not replace main conversation analysis or put live inbox status at the top of Insights.

Read the metrics precisely

MeasurementDefinitionImportant limit
Social conversationsDistinct conversations with a verified, processed customer message in the selected periodNot messages, unique people, or connected accounts
Handed to peopleConversations in that activity group with a handoff started in the same periodMultiple handoffs in one conversation count once here
Handoff shareHanded-to-people conversations divided by Social conversationsNo activity means no percentage; it is not resolution, satisfaction, or deflection
Handoff episodesIndividual transfers to the team started in the selected periodOne conversation can have several episodes, including manual takeovers
Median first human replyMedian elapsed time from handoff start to its first provider-accepted human reply, among episodes with oneNot working hours; unanswered episodes are excluded
Unanswered handoffsEpisodes in the period without a recorded qualifying first human replyClosing or resuming is not a human reply
Channel and reason breakdownsActivity volume by channel and episodes grouped by channel or recorded reasonConversation counts and episode counts use different groups

Provider acceptance does not establish that the customer read a message. This report does not infer satisfaction from delivery status or a lack of further messages.

Illustrative Social metrics showing conversation activity, team involvement, and channel volume.

Illustrative platform screenshot. Sample numbers are not a promise of performance or production results.

Scope and evidence

Choose the project, date range, and assistant before comparing values. Activity uses customer-message receipt time; episodes use handoff start time. Assistant scope follows the conversation's assigned assistant, including older conversations that retained a previous assignment.

A handoff near a date boundary can belong to a different period from the latest customer message. A quiet manual takeover can appear in episode counts without increasing activity-based handoff share. Channel totals for conversations and handoffs therefore need not describe the same group.

Open available conversation evidence before changing a policy. Refresh updates Social metrics along with other insights. Zero means no recorded activity in the selected scope; an unavailable report or a metric with no qualifying sample is not zero.

Operational metrics come from message and handoff records. Optional AI conversation analysis has separate eligibility, coverage, and completion states. The handoff report does not prove every attachment or conversation has been analyzed.

Last updated on