> For the complete documentation index, see [llms.txt](https://help.rechat.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.rechat.com/appendix/brokerage-set-up/pages.md).

# Pages

Pages allows brokerage admins to provide valuable information to their agents.

{% embed url="<https://rechatq.wistia.com/medias/j2eeyd1xap>" %}
Pages
{% endembed %}

Pages allow brokerage administrators to create a centralized hub of helpful resources, announcements, and training materials for their agents.

Use **Pages** to share things like:

* Office policies
* Training guides
* Marketing resources
* Important links
* Embedded videos and tutorials

Once published, Pages are instantly available to agents directly inside Rechat, making it easy to keep everyone informed without sending separate emails or files.

#### Accessing Pages

1. Navigate to **Support** (upper-right corner)
2. Select **Pages**
3. From here, you can:
   * Create new pages
   * Edit existing pages
   * Delete outdated pages
   * Reorder or update content anytime

Changes publish immediately for your agents.

#### Creating or Editing a Page

1. Click **Create Page** (or select an existing page to edit)
2. Add your:
   * Title
   * Text content
   * Links
   * Formatting
   * Media

The editor works like a simple document builder, allowing you to quickly design clean, easy-to-read content.

You can enhance your Pages by embedding videos directly into the content. This is perfect for:

* Training walkthroughs
* Announcements
* Recorded webinars
* Onboarding guides

No uploads are required. Simply paste a video link and Rechat handles the rest.

**Supported video sources**

* YouTube
* Vimeo
* Direct video files (MP4)

**Steps to add a video**

1. Open your page in edit mode
2. Place your cursor where the video should appear
3. Click **Insert Video** in the editor toolbar
4. Paste your video URL
5. Click **Save**

That’s it. The video will automatically embed and play inline for agents directly on the page.

#### Best Practices

To keep Pages clean and easy to navigate:

* Keep sections short and scannable
* Use headings and bullet points
* Embed videos instead of linking out when possible
* Separate large topics into multiple pages
* Update content regularly

Tip: For training content, embedding short videos directly on the page often leads to higher engagement than linking to external sites.

<details>

<summary>💡 IDEAS FOR PAGES</summary>

🛜 Wifi Information

💻 IT Information

🔧 Preferred Vendors

📱 Leadership Contact Information

📖 Policies & Procedures

🔁 Information Regarding Incoming & Outgoing Referrals

🖥️Social Media Links for Brokerage

🏢 Office Location Information

🗓️ Upcoming Company Events

</details>


---

# 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://help.rechat.com/appendix/brokerage-set-up/pages.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.