> For the complete documentation index, see [llms.txt](https://docs.welkinhealth.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.welkinhealth.com/designer/terminology-and-help/configure-help-section.md).

# Configure Help Section

## Overview

The Help section in the Care Portal provides care team members with quick access to resources, documentation links, and support contacts. You can configure the content of the Help section in the Designer to reflect your organization's specific resources and support workflows.

***

## Accessing Help Section Configuration

1. In the Designer, navigate to **Help Section** or **Configure Help**.
2. Create a draft to begin editing.

***

## What You Can Configure

The Help section can include:

* **Custom links** – links to internal documentation, training materials, or external resources
* **Support contact information** – email addresses, phone numbers, or ticketing system links for your internal help desk or Welkin support
* **Descriptive text** – free-text descriptions to help users understand available resources

***

## Adding a Help Link

1. Click **+ Add Link** in the Help Section configuration.
2. Enter a **Label** – the text that appears in the Care Portal (e.g., "Submit a Support Ticket").
3. Enter the **URL** for the link.
4. Optionally add a description.
5. Set the display order if multiple links are configured.
6. Save and publish.

***

## Publishing

Create a draft and publish to make help section changes visible to care team members in the Care Portal.

For an overview of how the Help section appears in Care, see [Help Section](/designer/terminology-and-help/help-section.md).


---

# 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.welkinhealth.com/designer/terminology-and-help/configure-help-section.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.