> 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

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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

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

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.