> For the complete documentation index, see [llms.txt](https://www.conserver.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.conserver.io/use-cases-studies.md).

# Use Cases / Studies

Lists real vCon deployments and public projects, each with a public source you can check, so you can see where vCon is used today.

Every case in this section is a real deployment or a public project, and each one links to a public source: a press release, a conference write-up, a hackathon record, or a public GitHub repository. If a claim has no public source, it is not here.

## Cases

| Case                                                                                                | What it is                                                                                                        | Date               | Source                                                                                                        |
| --------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------- | ------------------ | ------------------------------------------------------------------------------------------------------------- |
| [211 crisis-line pilot and contact-center alliance](/use-cases-studies/contact-center-211-pilot.md) | A U.S. customer-care outsourcer piloting vCons with 211 social-services contact centers, on a conserver platform  | 2025-06 to 2025-08 | Press releases, [TADSummit vCon Progress Report](https://blog.tadsummit.com/2025/08/20/vcon-progress-report/) |
| [Public corpora as vCons](/use-cases-studies/public-corpora.md)                                     | US Supreme Court oral arguments, IETF meeting sessions, and City of Newport, RI public meetings converted to vCon | 2026               | Public GitHub repositories                                                                                    |
| [TADHack builds](/use-cases-studies/tadhack-builds.md)                                              | Hackathon projects built on vCon in 2025 and 2026, and the synthetic dataset supplied to them                     | 2025-2026          | TADSummit and TADHack blogs, [hackathon review](/helps-and-hacks/vconic-tadhack-2026-hackathon-review.md)     |

## Patterns

[Patterns](/use-cases-studies/patterns.md) collects the problems vCon is designed for that do not yet have a public deployment to point to: moving conversation history between providers, privacy compliance, sharing with third parties. That page is labelled as patterns, and each pattern links to the hackathon build or spec section that shows it in practice.

## Add a case

Open a pull request against `use-cases-studies/` in [vcon-dev/vcon-docs](https://github.com/vcon-dev/vcon-docs) with a link to the public source. Say what was done, which vCon features it used, and when. Name an organization only if the public source names it.


---

# 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://www.conserver.io/use-cases-studies.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.