> For the complete documentation index, see [llms.txt](https://docs.whiteswan.io/partner-knowledge-base/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.whiteswan.io/partner-knowledge-base/chat/upcoming-features.md).

# Upcoming Features

White Swan Chat is evolving into a unified communication layer across the insurance journey. A few upcoming enhancements include:

***

#### AI Agentic Capabilities

The current chat experience will also serve as the interface for future White Swan AI capabilities. This will enable an AI powered chat will have capabilities like:

* Producing quotes&#x20;
* Pre-filling applications
* Answering insurance questions intelligently with context from the users current insurance experience and industry data

...and much more.&#x20;

***

#### HubSpot Integration

Chat conversations will soon be a part of a broader HubSpot integration, allowing teams to:

* Manage chat through Hubspot inbox
* Sync client activity
* Trigger workflows
* Centralize communication history

***

More details will be added as each feature becomes available.

These features build on the existing white-labeled chat foundation, ensuring your support experience grows more powerful over time.


---

# 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.whiteswan.io/partner-knowledge-base/chat/upcoming-features.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.
