> 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/contact-center-211-pilot.md).

# 211 Crisis-Line Pilot

Summarises the public record of a U.S. contact-center outsourcer's vCon pilot with 211 crisis lines, and maps what the sources describe to vCon fields.

A U.S. customer-care outsourcer announced a national vCon pilot with 211 operators in June 2025, and in August 2025 announced an alliance with a dealer-services company whose conserver platform runs the vCon pipeline. Everything below comes from the three public sources listed at the end; the organizations are named there.

## What was announced

**The pilot (2025-06-04).** The outsourcer announced a national pilot bringing vCons to 211 operators, the U.S. social-services help line. Per the release, each interaction is wrapped in metadata covering time, tone, participants and sentiment, and is "cryptographically sealed for integrity and compliance." The pilot "will begin in diverse regions spanning metro centers and rural communities," and participating organizations "will use vCON to revisit prior interactions, improve follow-up accuracy, and highlight systemic gaps."

**The alliance (2025-08-19).** A joint release described the outsourcer and the conserver provider working to embed vCons in the contact center. It notes that 32 people dial 211 every minute, and says the outsourcer is "already scaling vCon use cases internally, from reducing onboarding time to enhancing agent guidance and improving outcome reporting via SCITT-verified dashboards."

**The progress report (2025-08-20).** TADSummit's vCon Progress Report restates both: the pilot "is with 211 contact centers across the U.S., a social services help line, transforming crisis calls into real-time intelligence," and the conserver platform "provides the trusted infrastructure to scale that approach."

## vCon features involved

The sources describe outcomes, not schemas. In vCon terms, what they describe maps to these parts of the format:

| The sources say           | vCon feature                                                                                                                                   |
| ------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------- |
| Participants on each call | [`parties`](/vcons/field-reference.md#party-object)                                                                                            |
| The call itself           | [`dialog`](/vcons/field-reference.md#dialog-object)                                                                                            |
| Tone and sentiment        | [`analysis`](/vcons/field-reference.md#analysis-object) entries added by a conserver chain ([Standard Links](/conserver/standard-links.md))    |
| Cryptographically sealed  | [Signed form](/vcons/field-reference.md#signed-and-encrypted-forms) (JWS)                                                                      |
| SCITT-verified dashboards | SCITT registration of the vCon, see [Lifecycle](/extensions/lifecycle.md) and the conserver [`scitt` link](/conserver/standard-links.md#scitt) |

The sources do not say which transcription or analysis vendors are used, how consent is recorded, or how many calls the pilot has processed. Nothing here should be read as describing those.

## Sources

* "Frontline Group Launches vCON Pilot," PR Newswire, 2025-06-04, reproduced at [AI Journal](https://aijourn.com/?p=340143)
* "Strolid and Frontline Group Redefine the Contact Center Through Virtualized Conversations," [GlobeNewswire, 2025-08-19](https://www.globenewswire.com/news-release/2025/08/19/3135841/0/en/Strolid-and-Frontline-Group-Redefine-the-Contact-Center-Through-Virtualized-Conversations.html)
* Alan Quayle, [vCon Progress Report](https://blog.tadsummit.com/2025/08/20/vcon-progress-report/), TADSummit blog, 2025-08-20

## See also

* [Operational Benefits of Conservers](/conserver/operational-benefits-of-conservers.md)
* [SCITT and vCon](/deep-dives/scitt-supply-chain-integrity-transparency-and-trust.md)


---

# 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/contact-center-211-pilot.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.