> For the complete documentation index, see [llms.txt](https://docs.talkfurther.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.talkfurther.com/products/web-data/content-hub-knowledgebase.md).

# Content Hub & Knowledgebase

Senior-living prospects and families ask time-sensitive questions (pricing context, tours, care levels, amenities, services, etc.). If your data lives in scattered docs and emails, you get:

* Inconsistent answers across channels (web, SMS, phone, email)
* Slower responses and missed moments to book tours
* Wasted effort on setting up and maintaining seperate campaigns for communities in your Marketing Automation

Centralize your community facts once and power consistent answers everywhere using Further's Content Hub. Use the same underlying resources across all of Further prodcuts, including **Instant Answers**, **AI SMS**, **AI Phone**, **AI Email**, **Marketing Automation** and **Website Tools**.

**The Content Hub & Knowledgebase give you a single source of truth** that feeds every AI and web experience. Update it once, and the right, community-specific answer appears instantly across all channels — improving trust, speed, and move-in conversions.

![Content Hub](/files/vsGllLwqb6lSWsc2rx3y)

***

## What It Is & How It Works

Create and manage structured, community-specific information in two complementary views:

* **By Community** – curate everything for a single location (e.g., “Acme Senior Living”) in one place with all available tags raning from Community Name to Brochure links
* **By Tag** – manage a specific data element across many communities (e.g., `Event Phone Number`) and update it once using excel for all communities

Typical data Further will centralize:

* **Community Data Assets** from brochure links, to images, make it easy to share high quality resources with prospects — *add once; reuse everywhere*
* **Community Activities & Services** — all the details about the activities and services offered at your community to showcase resident quality of life.
* **Care & Funding Options** — costs, accepted payer sources (eg. Medicaid, Veterans Benefits), admission criteria, **age limits**, etc.
* **Floor Plans & Room Types** — names, availability descriptors, highlights
* **Pricing Context** — **entrance fee**, **second-person fee**, general price positioning

![Content Hub](/files/D1gjTS3is6irIdmauw3V)

Supported content types:

* **Text, links, and images**
* **Documents & media** (e.g., videos, brochures)
* **Community-specific attachments** tied to a tag

Bulk operations with guardrails:

* **Excel export/import** for fast, multi-community updates
* **Built-in validation** to prevent malformed data or breaking changes prior to publish

![Content Hub](/files/hIBwNZjaDvoS4SueYwdd)

### Knowledgebase (retrieval for AI)

The Knowledgebase transforms your Hub content into structured, retrieval-ready knowledge so AI can deliver precise, channel-appropriate answers:

* **Single source of truth for AI** used by Instant Answers, AI SMS, AI Phone, AI Email, and Website Tools
* **Community-aware personalization** so responses reflect each location's facts and preferred guardrails for communication
* **Merge tags** available across Further tooling (marketing/sales automations, conversational webforms, web tools, etc.)

![Email Editor](/files/VDwUFsrZGe6JadTXeh76)

## Guidelines For Managing Content Hub & Knowledgebase

**Scoping**

* Attach entries to the correct **community** so the right facts power that location’s channels
* Use **By Tag** when a single fact (e.g., a campaign phone number) is shared across communities to bulk upload tags using excel

**Naming conventions**

* Prefer clear, reusable names, for example:
  * `facebook_social_link`
  * `accepted_payers`
  * `room_types`
  * `dining_description`
  * `age_limit`
  * `entrance_fee` / `second_person_fee`

**Examples in templates**

* Email/SMS: “Call us at **{{event\_phone\_number}}** to RSVP.”
* Instant Answers/Phone: “We accept the following goverment programs: **{{accepted\_payers}}** and our age limit is **{{age\_limit}}**…”

***

## How to Set It Up

### Prerequisites

* **Admin access** to Further

### Access the Content Hub

1. Open **Content Hub** in Further
2. Choose a working mode:
   * **By Community** to curate a single location’s content end-to-end
   * **By Tag** to standardize a field across multiple communities

![Content Hub](/files/vsGllLwqb6lSWsc2rx3y)

### Add & Structure Content

1. Create or edit entries (e.g., **activities**, **outdoor areas**, **amenities**, **room types**, **dining areas**, **payer acceptance** like **Medicaid/Medicare**, **event phone numbers**, **age limits**, **fees**)
2. Apply **tags** and assign to **communities**
3. (Optional) **Excel download → update → upload** for bulk changes
4. Run **Validation** to catch formatting/mapping issues
5. **Publish** to sync updates to the Knowledgebase and all AI/web channels

***

## Summary

The **Content Hub & Knowledgebase** are the backbone of Further’s AI experiences. They centralize your community data, streamline maintenance (individually or in bulk), and guarantee that **the same, correct answer** flows to **Instant Answers, AI SMS, AI Phone, AI Email, and website tools** — resulting in faster, more consistent responses, richer personalization by community, and a smoother path from question → tour → move-in.


---

# 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.talkfurther.com/products/web-data/content-hub-knowledgebase.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.