> For the complete documentation index, see [llms.txt](https://docs.we360.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.we360.ai/how-to-and-best-practices/improving-employee-wellness/driving-engagement.md).

# Driving Engagement

Boost employee engagement using We360.ai Wellness360 analytics to identify under-utilized staff and improve remote team management.

Disengagement is just as costly as burnout. This guide shows how to use We360.ai data to identify and re-engage under-utilized employees.

## Identifying Under-Utilization

{% columns %}
{% column %}

#### Low Activity Scores

Employees with consistently very low activity scores (few keystrokes, minimal mouse movement) may be under-utilized, bored, or working through excessive meetings that aren't captured as "active" work.
{% endcolumn %}

{% column %}

#### Very Low Online Time

Employees logging significantly fewer hours than their assigned shift, without approved leave, may be disengaged or experiencing personal issues worth addressing proactively.
{% endcolumn %}
{% endcolumns %}

## Action Steps

{% stepper %}
{% step %}

#### Generate a Team Utilization Report

Go to **Universal Tools → Reports** and run a **Group Insights** or **Productivity Summary** report for your team over the past 30 days. Sort by activity score to surface the bottom performers.
{% endstep %}

{% step %}

#### Review Individual Timelines

Click into any employee's **User Details** page to review their day-by-day activity timeline. This gives a qualitative sense of their working patterns beyond aggregate stats.
{% endstep %}

{% step %}

#### Engage with Data-Backed Conversations

Use the Wellness360 data as a starting point for a constructive manager conversation about workload, role fit, and team culture — not as a disciplinary measure.
{% endstep %}
{% endstepper %}

{% hint style="info" %}
We360.ai recommends using engagement data for HR conversations, not automated disciplinary actions. Transparency builds trust.
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.we360.ai/how-to-and-best-practices/improving-employee-wellness/driving-engagement.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.