> 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/tools/vcon-apps-and-stores/tadhack-vcon.md).

# TADHack vCon

## Conversation Set

For this year's TADHack vCon Hackathon, we've generated a set of synthetic vCons for your use:

* You can download the set at <https://github.com/vcon-dev/tadhack-2025>
* An S3 Bucket is here: arn:aws:s3:::tadhack-vcons

## Overview

This dataset contains customer service conversation data from Aquidneck Yacht Brokers in VCON (Virtual Call Object Notation) format. The conversations span from May 18-24, 2025, and represent typical customer interactions for a yacht brokerage company. The dataset includes 42 customer service calls between Aquidneck Yacht Brokers agents and customers, covering various marine industry-specific support scenarios.

### Conversation Types

#### 1. Returns & Refunds

* Customers requesting returns for yacht equipment
* Processing refund requests
* Emotional customers (often expressing sadness about returns)

#### 2. Shipping & Logistics

* Yacht transportation inquiries (e.g., Fort Lauderdale to Newport)
* Delivery status updates
* Shipping cost questions

#### 3. Order Issues

* Wrong items received (e.g., yacht anchor instead of navigation system)
* Missing order investigations
* Order verification and corrections

#### 4. Equipment Support

* GPS malfunction troubleshooting
* Navigation system issues
* Equipment compatibility questions

#### 5. Business Services

* Yacht listing inquiries
* Brokerage service questions
* Pricing and commission discussions

#### 6. Account Management

* Membership cancellations
* Billing inquiries
* Privacy and data concerns
* Contact information updates

#### 7. Appointments & Scheduling

* Yacht viewing appointments
* Service scheduling
* Consultation bookings

### Call Characteristics

* **Average Duration**: 50-60 seconds
* **Call Disposition**: All marked as "ANSWERED" with "VM Left" status
* **Language**: English
* **Transcription Confidence**: 99%
* **Professional Tone**: Agents maintain consistent, helpful demeanor
* **Resolution Rate**: Most issues resolved or appropriately escalated

### Data Format

Each conversation includes:

* Audio recording (MP3 format)
* Full transcript with speaker diarization
* AI-generated summary
* Participant metadata (names, roles, contact info)
* Call metadata (duration, timestamp, disposition)

### Typical Interaction Flow

1. Agent greeting with company name and agent introduction
2. Customer name verification
3. Issue description by customer
4. Information gathering (order numbers, email verification)
5. Resolution or escalation
6. Professional closing

### Notable Patterns

* Customers frequently express emotions related to their issues
* Agents consistently follow verification protocols
* Marine industry-specific terminology used throughout
* Focus on high-value transactions typical of yacht brokerage

This dataset provides realistic examples of customer service interactions in the luxury marine industry, useful for training, analysis, or demonstration purposes.


---

# 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://www.conserver.io/tools/vcon-apps-and-stores/tadhack-vcon.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.