> For the complete documentation index, see [llms.txt](https://help.steeple.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.steeple.com/en/centre-d-accompagnement/bienvenue.md).

# Welcome to your Support Center

### A journey to go further with Steeple

The Support Center guides each organization, independently, through every stage of adopting Steeple. Whether usage is just beginning or already established, this journey makes it possible to:

* take stock of the actual use of Steeple in the company
* engage the right internal stakeholders
* centralize communications
* embed new practices sustainably

The center is designed to **adapt to each person’s pace**, depending on current priorities. It can be followed step by step or explored as needed. And if necessary, **Steeple consultants can step in occasionally**.

### The 8 key steps of the journey

#### 1. Understand your adoption level

Where to start? Take stock.

* Identify the signs of good usage… or warning signs
* Assess the level of maturity on Steeple
* Define the next priorities for action

#### 2. (Re)engage leadership

A strong project needs a strong sponsor.

* (Re)engage leadership around the project
* Align the company’s strategic challenges with internal communication objectives
* Give meaning and weight to the approach

#### 3. Ensure accessibility for everyone

Steeple is only useful if everyone can access it.

* Check that every employee can connect easily
* Activate the right access points: screens, mobile, PC, QR codes…
* Think about frontline, disconnected or isolated employees

#### 4. Centralize communication

One tool, one reference: Steeple.

**4.1. Identify internal competing tools**

* Sort through: emails, WhatsApp, paper, posters, intranet…
* Spot duplicates and noisy channels

**4.2. Create a platform that reflects the company**

* Customize the interface: logo, sections, useful modules
* Highlight the right content: news, schedule, directory…

**4.3. Support managers and communication relays**

* Organize workshops or internal training sessions
* Provide concrete ideas and simple tools for posting

**4.4. Permanently eliminate competing tools**

* Put an end to duplicates: email, paper postings, WhatsApp, etc.
* Set up a clear and engaging transition plan

#### 5. Ensure quality and consistency

What matters is not publishing a lot… but publishing well.

* Set up a simple and realistic editorial calendar
* Vary the formats, authors, and topics
* Take care with the tone: clear, human, authentic

#### 6. Measure and improve

Managing means progressing.

* Track the indicators
* Ask employees for feedback
* Adjust the content and priorities over time

#### 7. Exchange with peers

Other companies face the same challenges.

* Get inspired by other Steeple customers
* Take part in workshops, meetups, or webinars
* Share successes and questions

#### 8. Get support (if needed)

No one is alone.

* Call on a Steeple consultant for a helping hand
* Request an audit, a workshop, or personalized support
* Access the support services catalog


---

# 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:

```
GET https://help.steeple.com/en/centre-d-accompagnement/bienvenue.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
