> For the complete documentation index, see [llms.txt](https://docs.enate.net/enate-help/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.enate.net/enate-help/francais/master.md).

# Work Manager

Dans cette section, vous trouverez de nombreuses explications et vidéos pour apprendre à utiliser le logiciel Work Manager d'Enate pour gérer vos processus commerciaux au quotidien.

### Présentation de Work Manager

Work Manager est une application web multipages utilisée par les membres de l'équipe de prestation de services pour gérer les Tickets, les Cas et les Actions en cours dans le cadre des processus métier gérés.

Les utilisateurs de Work Manager sont les agents de service, les chefs d'équipe, les responsables des opérations et les cadres dirigeants. Work Manager propose un ensemble standard de vues permettant à ces utilisateurs d'effectuer leur travail.

Regardez cette vidéo pour un aperçu rapide de Work Manager :

{% embed url="<https://enate.cdn.spotlightr.com/watch/MTM2MTYzMA==>" %}

### Prise en charge des navigateurs

Work Manager est conçu pour prendre en charge les navigateurs suivants :

* Dernière version de Chrome (au moment de sa sortie)
* Dernière version de Firefox (au moment de la publication)
* Dernière version du navigateur Microsoft Edge, basée sur Chromium (au moment de sa sortie).


---

# 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.enate.net/enate-help/francais/master.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.
