Select comparable reporting windows and avoid acting on incomplete or differently scoped data This guide keeps the work focused on Analytics periods and provides a repeatable path that a new Humind user can follow without changing unrelated configuration.

Humind analytics helps teams inspect conversations, questions, pages, topics, and Agent performance. Each view answers a different question and depends on its selected period and available data. Analytics supports investigation and prioritization, but a chart should be checked against conversations and business context before it drives a change.

Before you begin

Access: Analytics read access is required.

• Identify the decision date and expected measurement delay.
• Choose comparable business days or campaign windows.
• Record deployments, incidents, and catalog changes that may affect the period.

Work in the smallest owning area described below and keep the current customer-facing state available while you prepare the change. Before clicking any final action, confirm the active company, Agent, store, language, and market shown in Humind. A missing control can indicate read-only access or a capability that is not configured for this company. In that case, record the intended task and ask an administrator to review the exact permission or dependency. Do not bypass the boundary by sharing an account, copying data into another area, or promising a capability that the workspace does not expose.

Step-by-step workflow

1. Confirm the scope and current state

   Set the current period, timezone, Agent, and channel explicitly rather than relying on a remembered dashboard default.

   • Confirm the active company and Agent before editing.
   • Record the current state so the result can be compared after the change.
   • Stop if the screen or permission does not match the intended task.

2. Prepare the change

   Choose a comparison window with similar length and business conditions, noting holidays, promotions, or outages.

   • Use the smallest change that completes the customer task.
   • Keep authoritative information in its owning source.
   • Review labels, dates, language, and customer-visible wording before saving.

3. Save and allow required processing to finish

   Check visible freshness indicators and allow recently completed conversations or events time to arrive before drawing a final conclusion.

   • Wait for the interface to confirm that the change is saved.
   • If synchronization, indexing, or publication is required, wait for its final state.
   • Reload the area and confirm the saved values persist.

4. Test the complete customer journey

   Save or report the exact filters with the result, then revisit after the expected data window closes.

   • Use a fresh session and a realistic customer scenario.
   • Check desktop and mobile when the result appears on a storefront.
   • Capture the exact failing step if the outcome differs from the expectation.

Important limits and operating notes

• A successful save confirms persistence, not every downstream synchronization or public update.
• Workspace permissions can hide an area or allow reading without allowing changes.
• Do not copy volatile catalog, account, or customer facts into narrative content as a workaround.
• Test only supported capabilities that are visible and configured for the current company.
• Keep changes in Analytics periods separate from unrelated Agent, Knowledge, catalog, Inbox, or Helpdesk work.

Verify the result

• Both periods use the same scope and timezone.
• The comparison accounts for major business differences.
• Recent data is labeled preliminary when appropriate.
• Another teammate can reproduce the result from the recorded filters.

Keep a short record of what you tested, which customer scenario you used, and what changed. This makes later troubleshooting more precise and helps another teammate reproduce the result without relying on memory.

Troubleshooting

Numbers change after a report was shared

Check whether the original period was still open or data was still arriving. Update the report with a clear as-of time rather than silently replacing the earlier value.

Two teammates see different totals

Compare company, Agent, channel, period boundaries, timezone, filters, and permissions. Align the full scope before investigating calculation logic.

Related guides

• understand humind analytics metrics and attribution
• use analytics to improve conversations
• how to see analytics
• complete your first launch checklist