> For the complete documentation index, see [llms.txt](https://docs.healthsherpa.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.healthsherpa.com/on-exchange-api-documentation/integration-guide/use-cases-and-features.md).

# Use Cases and Features

* [One-click quoting](/on-exchange-api-documentation/integration-guide/use-cases-and-features/one-click-quoting.md#overview)
  * Pass data from your CRM into HealthSherpa and agents can do a complete ACA quote with one click. 
* [Link CRM records to specific HealthSherpa transactions](/on-exchange-api-documentation/integration-guide/use-cases-and-features/link-your-crm-records-to-specific-healthsherpa-transactions.md#overview)
  * Use deeplinking to associate your client ID with that client's application in HealthSherpa, then see your ID in HealthSherpa enrollment exports. This means no more fuzzy matching. 
* [HealthSherpa Exports](/on-exchange-api-documentation/integration-guide/use-cases-and-features/operationalizing-healthsherpa-exports.md)
  * HealthSherpa’s export functions let agencies download CSV files of client, lead, enrollment, and follow-up data from across their organization, giving leadership a structured data feed for reporting, reconciliation, and operational oversight. 
  * By ingesting that data into their own systems, agencies can tie enrollments to commissions, support advance commissioning and payout forecasting, and trigger sales, service, and retention workflows that improve effectuation and producer accountability.

#### More features planned for 2026!


---

# 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.healthsherpa.com/on-exchange-api-documentation/integration-guide/use-cases-and-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.