> 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/one-click-quoting.md).

# One-click quoting

## Overview <a href="#overview" id="overview"></a>

Deeplinking allows users (agents and consumers) to navigate directly from your system (e.g., an agency CRM) into HealthSherpa’s quoting and shopping flow. By constructing a deeplink URL, your system can pass consumer attributes you already have to prefill the HealthSherpa quoting tool, removing the need for agents to re-enter data.

**Note:** The only form of deeplinking available is into the quoting/shopping flow; deeplinking directly into the application while passing a pre-selected health plan, is not supported for new integrations.

{% hint style="info" %}
If you pass your client/household's identifier in the deeplink (our `external_id` parameter), that ID will be included in your agency exports and any webhooks you set up. This allows you to easily map data from HealthSherpa to your system of record.&#x20;

See the [Deeplinking Parameters](/on-exchange-api-documentation/api-reference/deeplinking-to-plan-quoting/parameters.md) page for more details about `external_id` and [here](/on-exchange-api-documentation/integration-guide/use-cases-and-features/link-your-crm-records-to-specific-healthsherpa-transactions.md) for more about linking your CRM records to specific HealthSherpa transactions.&#x20;
{% endhint %}

### Problems this solves <a href="#problems-this-solves" id="problems-this-solves"></a>

1. **Duplicate data entry**: Your system already has some, or all, of the consumer data needed to quote on HealthSherpa. Deeplinking removes the need for an agent to copy and paste when they quote.
2. **Data integrity**: The quote is built automatically with the information from your system, so there’s no risk of human error when inputting data into our quoter.
3. **Record matching**: By utilizing an `external_id` passed during the quoting process, future HealthSherpa exports then reference that ID, allowing you to automatically associate the HealthSherpa transaction with the specific lead record in your internal system.

### How It Works

1. An agent opens a consumer record in your system.
2. Your system builds a deeplink URL to HealthSherpa, embedding the known consumer data, and your system's unique identifier for the consumer (`external_id`).
3. The agent’s browser navigates to the deeplink.
4. HealthSherpa parses the parameters, pre-fills the quoter, and associates the session with the provided `external_id`.
5. The agent lands on the HealthSherpa plan list page, with everything pre-populated, to shop and select a plan. From there, they submit the application like usual.

### What it looks like

<figure><img src="/files/PSoT6aSr0MWKnOEZ0H8j" alt=""><figcaption></figcaption></figure>

### Compliance and CMS Approval

**Deeplinking without CMS approval is non-compliant.** Agencies must be approved by CMS before they can use deeplinking in production.

* **Requesting Approval:** HealthSherpa submits the request to CMS on your behalf.
* **Timeline:** The CMS review typically takes 2-4 weeks.
* **Development:** While waiting for CMS approval, you can build and test the deeplinks in HealthSherpa's staging environment.
* **Eligibility:** Access is granted on a case-by-case basis. Agencies must remain in good standing with CMS and HealthSherpa.

### Moving forward with deeplinking

If you haven’t done so already, please let us know you want to use deeplinking by submitting a request on [one.healthsherpa.com](https://one.healthsherpa.com).&#x20;

If you're interested in deeplinking, HealthSherpa will request that CMS approve your agency or platform to deeplink into HealthSherpa. We will also then reach out to you with information on how to access our staging and development environment.&#x20;


---

# 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/one-click-quoting.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.