Review thirty-day trends

Team trends summarize up to 500 recent communication events across a thirty-day window. They are directional management signals built from the evidence available to the workspace. This view requires an owner or manager account.

Check the window and volume

Start with the thirty-day window and total event volume. A small or uneven sample limits the conclusions you can draw. Missing events or incomplete analysis can also affect the view.

Review the channel mix

Compare the event counts for calls, voicemail, email, and SMS. The mix describes activity in the available sample. It is not a quality score for the team.

Investigate a specific question

Use intents and recurring topics to identify interactions worth reading. Labels can be incomplete or inaccurate. Open Conversations and inspect representative original sources before changing a workflow or coaching someone.

Keep the interpretation bounded

Record the question, period, sample, and sources behind any conclusion. Do not compare people or make employment decisions from aggregate sentiment, engagement, intent, topic, or volume signals.

If the view is unavailable, confirm that you have an owner or manager account and ask the workspace owner to check access. An empty view does not prove that no work occurred.

Establish the population behind the view

Start by recording the period and number of communication events available to the trend view. The thirty-day window includes up to 500 recent events, so a busy workspace's sample may not represent every interaction during that period. Keep that limit attached to any conclusion you share with the team.

Check the channel mix before comparing periods or groups. Calls, voicemail, email, and SMS serve different purposes and can produce different kinds of evidence. A shift toward one channel may reflect the work being done rather than a change in recruiter effectiveness. Investigate the operational context before assigning a cause.

Turn a recurring topic into a review question

A recurring topic can help identify where to read more closely. If start dates appear repeatedly, inspect relevant conversations to determine whether candidates are asking for clarification, clients are changing requirements, or the same unresolved issue is appearing in follow-ups. The topic label alone cannot distinguish those explanations.

Choose representative sources within your authorized scope. Include examples that might challenge the first interpretation, rather than reading only the interactions that support it. If available evidence is too sparse or uneven, record the limitation and postpone a broad conclusion.

Keep activity, quality, and outcomes separate

An event count describes the available communication activity. It does not measure completed placements, revenue, or time saved. Sentiment and engagement likewise require context and source review. Do not turn a change in one of these indicators into a claim about business performance without separate evidence.

For a fictional management review, repeated questions about a night-shift start date might justify improving the job brief. The manager would first check the job record and conversations to establish the actual missing information. That proposed process change is different from concluding that an individual recruiter performed poorly.

Record a bounded management decision

When the evidence supports a change, describe the specific workflow issue, the sources reviewed, and the person who will implement the next step. Define how the team will check whether the change helped, using a measure appropriate to that workflow. Keep private examples and approval records in the agency's approved workspace.

If Team trends is unavailable, confirm the owner or manager role and ask the workspace owner to review access. For an empty or unexpected view, check the period and available event volume before reporting a problem. Include the visible state and approximate time in a support request, without exporting unrestricted communication records merely to demonstrate the issue.