Update README.md
Browse files
README.md
CHANGED
|
@@ -0,0 +1,137 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 1 |
+
# Multi-Domain Support Conversations Dataset
|
| 2 |
+
|
| 3 |
+
This dataset combines **600 realistic customer support conversations** from six different domains:
|
| 4 |
+
|
| 5 |
+
- **Customer Service** (100 conversations)
|
| 6 |
+
- **E-commerce** (100 conversations)
|
| 7 |
+
- **Financial Support** (100 conversations)
|
| 8 |
+
- **HR / Onboarding** (100 conversations)
|
| 9 |
+
- **Medical Helpdesk** (100 conversations)
|
| 10 |
+
- **Technical Support** (100 conversations)
|
| 11 |
+
|
| 12 |
+
Each dialogue is exactly 11 turns long and covers a wide variety of issues, making it ideal for training general-purpose AI assistants, chatbots, and customer support models.
|
| 13 |
+
|
| 14 |
+
## Dataset Structure
|
| 15 |
+
|
| 16 |
+
Each conversation is stored as a JSON object with the following fields:
|
| 17 |
+
|
| 18 |
+
| Field | Type | Description |
|
| 19 |
+
|-------|------|-------------|
|
| 20 |
+
| `id` | integer | Unique identifier (1–600, grouped by domain) |
|
| 21 |
+
| `domain` | string | Original domain (e.g., `"customer service"`, `"e-commerce"`) |
|
| 22 |
+
| `problem` | string | Short description of the customer's issue |
|
| 23 |
+
| `customer_type` | string | Customer persona (see full list below) |
|
| 24 |
+
| `dialogue` | array | List of alternating customer/agent messages |
|
| 25 |
+
| `dialogue[].role` | string | `"customer"` or `"agent"` |
|
| 26 |
+
| `dialogue[].text` | string | The message content |
|
| 27 |
+
| `resolution` | string | One-sentence summary of how the issue was resolved |
|
| 28 |
+
|
| 29 |
+
## Customer Personas (with descriptions)
|
| 30 |
+
|
| 31 |
+
The dataset includes six distinct customer types, evenly distributed across each domain in a fixed cycle (conversations 1–6 contain one of each type, and the pattern repeats every 6 conversations up to 100):
|
| 32 |
+
|
| 33 |
+
- **frustrated user** – Emotionally charged, expects fast resolution, may be abrupt.
|
| 34 |
+
- **confused beginner** – Low technical literacy, needs step-by-step guidance, asks basic questions.
|
| 35 |
+
- **impatient executive** – Busy professional, direct, demands efficiency and authoritative responses.
|
| 36 |
+
- **elderly user** – Older, patient, requires clear explanations and warm treatment.
|
| 37 |
+
- **tech-savvy user** – High technical knowledge, uses precise terminology, wants exact details.
|
| 38 |
+
- **calm and patient user** – Collaborative, easy-going, follows instructions without friction.
|
| 39 |
+
|
| 40 |
+
This balanced distribution ensures your model learns to handle a wide range of communication styles and needs.
|
| 41 |
+
|
| 42 |
+
## Example Conversation
|
| 43 |
+
|
| 44 |
+
Below is a sample conversation from the **customer service** domain (customer type: impatient executive):
|
| 45 |
+
|
| 46 |
+
```json
|
| 47 |
+
{
|
| 48 |
+
"id": 1,
|
| 49 |
+
"domain": "customer service",
|
| 50 |
+
"problem": "order never arrived",
|
| 51 |
+
"customer_type": "impatient executive",
|
| 52 |
+
"dialogue": [
|
| 53 |
+
{
|
| 54 |
+
"role": "customer",
|
| 55 |
+
"text": "I placed an order 10 days ago and it still hasn't arrived. This is completely unacceptable."
|
| 56 |
+
},
|
| 57 |
+
{
|
| 58 |
+
"role": "agent",
|
| 59 |
+
"text": "I sincerely apologize for this delay. I'll look into this immediately. Could you provide your order number?"
|
| 60 |
+
},
|
| 61 |
+
{
|
| 62 |
+
"role": "customer",
|
| 63 |
+
"text": "Order number is #ORD-88421. I need this resolved today."
|
| 64 |
+
},
|
| 65 |
+
{
|
| 66 |
+
"role": "agent",
|
| 67 |
+
"text": "Thank you. I've pulled up your order. I can see it was delayed at the courier depot. I'm escalating this as high priority right now."
|
| 68 |
+
},
|
| 69 |
+
{
|
| 70 |
+
"role": "customer",
|
| 71 |
+
"text": "How long will an escalation actually take? I've heard that before."
|
| 72 |
+
},
|
| 73 |
+
{
|
| 74 |
+
"role": "agent",
|
| 75 |
+
"text": "I completely understand your frustration. I'm contacting the courier directly and will have a confirmed delivery window within 2 hours. I'll also apply a full shipping refund."
|
| 76 |
+
},
|
| 77 |
+
{
|
| 78 |
+
"role": "customer",
|
| 79 |
+
"text": "Alright. A 2-hour update is acceptable. What's the reference for this case?"
|
| 80 |
+
},
|
| 81 |
+
{
|
| 82 |
+
"role": "agent",
|
| 83 |
+
"text": "Your case reference is TKT-20394. I've also sent you an email confirmation with the courier's direct contact and your shipping refund confirmation."
|
| 84 |
+
},
|
| 85 |
+
{
|
| 86 |
+
"role": "customer",
|
| 87 |
+
"text": "I received the email. The refund is noted. I expect the delivery window shortly."
|
| 88 |
+
},
|
| 89 |
+
{
|
| 90 |
+
"role": "agent",
|
| 91 |
+
"text": "Absolutely. You'll receive an SMS from the courier within 90 minutes. Is there anything else I can assist with?"
|
| 92 |
+
},
|
| 93 |
+
{
|
| 94 |
+
"role": "customer",
|
| 95 |
+
"text": "No. Just make sure it's delivered. Thank you."
|
| 96 |
+
}
|
| 97 |
+
],
|
| 98 |
+
"resolution": "Order traced to courier depot delay. Case escalated with priority, shipping refund applied, and delivery window confirmed within 2 hours."
|
| 99 |
+
}
|
| 100 |
+
|
| 101 |
+
How to Use
|
| 102 |
+
Load with Python (local JSON)
|
| 103 |
+
python
|
| 104 |
+
|
| 105 |
+
import json
|
| 106 |
+
|
| 107 |
+
with open("multi_domain_support.json", "r", encoding="utf-8") as f:
|
| 108 |
+
data = json.load(f)
|
| 109 |
+
conversations = data["conversations"]
|
| 110 |
+
|
| 111 |
+
# Example: print all problem descriptions
|
| 112 |
+
for conv in conversations:
|
| 113 |
+
print(conv["domain"], conv["problem"])
|
| 114 |
+
|
| 115 |
+
Load with Hugging Face Datasets
|
| 116 |
+
python
|
| 117 |
+
|
| 118 |
+
from datasets import load_dataset
|
| 119 |
+
|
| 120 |
+
dataset = load_dataset("ai-training-datasets/multi-domain-support", split="train")
|
| 121 |
+
print(dataset[0])
|
| 122 |
+
|
| 123 |
+
License
|
| 124 |
+
|
| 125 |
+
This dataset is released under the MIT License. You are free to use, modify, and distribute it for both research and commercial purposes.
|
| 126 |
+
Citation
|
| 127 |
+
|
| 128 |
+
If you use this dataset in your work, please cite it as:
|
| 129 |
+
text
|
| 130 |
+
|
| 131 |
+
@dataset{ai_training_datasets_2026,
|
| 132 |
+
title = {AI Training Datasets: Multi-Domain Support Conversations},
|
| 133 |
+
author = {AI Training Datasets},
|
| 134 |
+
year = {2026},
|
| 135 |
+
version = {1.0},
|
| 136 |
+
publisher = {Hugging Face}
|
| 137 |
+
}
|