File size: 10,402 Bytes
0dff23d
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
# Call opening annotation guide v0.2

You label the **opening of a customer-service call** from a speaker-labelled transcript. You report what the
institution side communicated, with exact quotes as evidence. You do not judge whether a policy is met.

Each call is given as numbered turns `t0, t1, …` with a speaker role (`Agent`, `Customer`, or `IVR` for an automated
recording) and a metadata line. The transcript is speech-recognised: expect fillers, repeats, misspellings and
names written as heard.

## 1. Who counts

- Only **Agent** and **IVR** turns can provide identification or a notice.
- A customer introducing themselves, naming the bank, or asking "Are you recording?" never counts.
- Trust the speaker labels. If a turn looks mislabelled, label as given and say so in `notes`.

## 2. The opening window

`opening_end_turn` = the index of the **Agent turn that answers the customer's first statement of their reason for
calling**. That turn is part of the opening (disclosures in it count).

- Greetings, identification, notices, asking the customer's name, "how can I help" all come before it.
- The reason counts as stated at the customer's first **explicit** request or problem ("I want to close my account",
  "my card was declined"), not a hint or small talk ("today is my last day as a customer", "I have a question").
  The answer is the first Agent turn that **responds to the request itself** ("Yeah, absolutely", "Sure, I can help
  with that", "Let me look into that"). A bare backchannel ("OK.", "Mhm", "Wow!") or an Agent turn about something
  else (spelling the customer's name, asking them to repeat) is not the answer; keep looking.
- If the customer states no reason in the turns shown, use the last Agent turn shown and add a note.
- Fields are labelled **only from turns up to and including `opening_end_turn`**. Identification or a notice that
  first appears later goes into `late_mentions`, not into the labels.

## 3. Fields

### agent_identification: `present` | `absent` | `unclear`
- `present`: the agent gives their own first name, full name, or agent / employee number. "This is Amanda",
  "my name is Jean", "I'm Agnes", "Hi, Dani Brooks, with Intellibank", "you're speaking to Carlie",
  "my agent number is eight two five seven one four".
- `unclear`: an attempt that cannot be made out ("this is, uh, with Intellibank", a name cut off).
- `absent`: none of the above. A department name ("this is customer service") is not identification.

### institution_identification: `present` | `absent` | `unclear`
- `present`: the institution is named, even misspelled by speech recognition ("Intellibank", "Intellabank",
  "Intel Bank", "Rivertown Insurance").
- `unclear`: only a generic noun ("thank you for calling bank", "the bank", "customer service") or an
  unintelligible name.
- `absent`: no institution mentioned by the agent or IVR.
- The institution named inside a product name ("Intellibank Business Total Checking") counts as `present`.
- If the metadata line says an automated notice naming the institution was played, that counts as `present`; quote
  nothing (evidence turn `-1`).

### recording_notice: `definite_recording` | `possible_recording` | `monitoring_only` | `none` | `unclear`
- `definite_recording`: the call **is** recorded. "This call is being recorded", "we are on a recorded line",
  "I will be assisting you on this recorded call", "recorded and monitored", "this call will be recorded".
- `possible_recording`: recording is only possible. "may be recorded", "may be monitored or recorded",
  "calls are sometimes recorded", "some calls are recorded".
- `monitoring_only`: monitored / listened to, no mention of recording. "This call may be monitored for quality".
  Monitoring never implies recording.
- `none`: no notice, or a negation ("this call is not recorded"; keep the negation as evidence with polarity
  `negated`).
- `unclear`: contradicting or garbled statements about recording.
- More than one notice: the strongest wins (`definite_recording` > `possible_recording` > `monitoring_only`).
- **Not recording notices** (label `none` unless there is a real notice too; quote them as polarity `distractor`
  only when they could confuse a reader): "I'm recording your address", "let me record your info", "I see a record
  of your call", "for the record, my name is", "your records", "on a secure line", a customer asking "do you record
  this?".

### recording_purpose: list of `quality`, `training`, `security`, `other`, `not_stated`, `unclear`
Only when `recording_notice` is `definite_recording`, `possible_recording` or `monitoring_only`; otherwise `[]`.
- `quality`: quality assurance, quality purposes, customer satisfaction, customer service purposes, to improve
  our service.
- `training`: training, coaching.
- `security`: security, for your protection, fraud prevention, verification.
- `other`: any other stated purpose: compliance, regulatory, legal, record keeping, dispute resolution.
- `not_stated`: a notice with no purpose. Never combine `not_stated` with another value.
- `unclear`: a purpose phrase that cannot be made out.
- **"secure line", "secured line", "secure call" are never a purpose** (they describe the line, not why the call is
  recorded): "this call is being recorded on a secure line" → `["not_stated"]`.
- "quality and training" → `["quality", "training"]`. "for your security and customer satisfaction" →
  `["security", "quality"]`. "on a secure line" is **not** a purpose.
- The purpose must be stated for the recording or monitoring within the opening window.

### opening_coverage: `complete` | `incomplete` | `unknown`
- `complete`: metadata says `starts at call start: yes`.
- `incomplete`: metadata says `no`, or (metadata not given) the text plainly starts in the middle of the call: the
  first turns continue a conversation already under way (an account being looked up, a reply to a question we never
  saw) with no greeting.
- `unknown`: metadata not given and the text could be the start of the call (for example it starts with a greeting).
- When coverage is `incomplete`, a field you would otherwise label `absent` / `none` is labelled `unclear`
  instead: not observed is not confirmed absence.

## 4. Evidence

For every field value other than `absent`, `none`, `not_stated` and coverage, give at least one evidence item:
`{"field", "value", "polarity", "turn", "quote"}`.
- `turn` is the turn index (`-1` for metadata); `quote` is copied **exactly** from that turn (same spelling, same
  case, no added or removed characters), as short as possible while still carrying the meaning: "This is Amanda",
  "Intellibank", "this call is being recorded", "for quality assurance purposes".
- `polarity`: `asserted` (normal), `negated` ("is not recorded"), `distractor` (looks like a notice but is not).
- For `recording_purpose`, one item per purpose value.
- For `unclear` values, quote the garbled part.

`late_mentions`: items `{"field", "value", "turn", "quote"}` for identification or notices after
`opening_end_turn`.

## 5. Output

Reply with one JSON object: `{"rows": [ … ]}`, one item per call, in the order given:

```json
{"id": "<call id>", "opening_end_turn": 2,
 "agent_identification": "present", "institution_identification": "present",
 "recording_notice": "definite_recording", "recording_purpose": ["security", "quality"],
 "opening_coverage": "complete",
 "evidence": [{"field": "agent_identification", "value": "present", "polarity": "asserted", "turn": 0, "quote": "My name is Sandra"}],
 "late_mentions": [], "notes": ""}
```

`notes`: empty, or one short sentence about anything doubtful.

## 6. Worked examples

1. `t0 Agent: Good morning, Intellibank. This is Amanda, how may I help you?` `t1 Customer: I need my balance.`
   `t2 Agent: Yeah, absolutely.` → end 2; agent present ("This is Amanda"); institution present ("Intellibank");
   notice none; purpose []; coverage complete.
2. `t0 Agent: Thank you for calling Intellibank. My name is Jean, and I will be assisting you on this recorded call.`
   → agent present; institution present; `definite_recording` ("this recorded call"); purpose `["not_stated"]`.
3. `t0 Agent: …My name is Sandra and I'll be assisting you on a recorded call for your security and customer
   satisfaction.` → `definite_recording`; purpose `["security", "quality"]` (quotes "for your security",
   "customer satisfaction").
4. `t0 Agent: Thank you for calling Intellibank. My name is Casey.` `t1 Customer: I want to open a savings account.`
   `t2 Agent: I can help with that. Just to let you know we are on a recorded line on a secure line, and my agent
   number is eight two five.` → end 2; `definite_recording` ("we are on a recorded line"); purpose
   `["not_stated"]` ("secure line" is not a purpose).
5. `t0 Customer: Ring, ring.` `t1 Agent: Good afternoon. Thank you for calling bank. This is Ron Smit.` → agent
   present ("This is Ron Smit"); institution `unclear` ("calling bank").
6. `t0 Agent: Hello, thanks for calling Rivertown insurance customer service. How may I help you?` → agent `absent`;
   institution present ("Rivertown insurance").
7. `… t3 Agent: yes I do see there's a record of a call here` → notice none; optional distractor evidence
   ("there's a record of a call").
8. `t2 Agent: Thanks for calling Northgate Bank, this is Ravi.` `t3 Customer: Are you recording this?`
   `t4 Agent: No, this call is not recorded.` (t4 answers the customer's first reason) → notice none, evidence
   polarity `negated` ("this call is not recorded").
9. `t0 Agent: This call may be monitored for quality purposes. Thank you for calling Westfield Bank.` →
   `monitoring_only`; purpose `["quality"]`.
10. `t0 Agent: Calls may be recorded or monitored for training. Thank you for calling Kaveri Credit Union, my name is
    Anil.` → `possible_recording`; purpose `["training"]`.
11. Metadata `starts at call start: no`; `t0 Agent: …so I'll go ahead and pull up that account for you.` → coverage
    `incomplete`; agent / institution / notice `unclear` (not observed is not absent).
12. `t0 Agent: Thank you for calling Intellibank. How can I help?` `t1 Customer: My card was declined.`
    `t2 Agent: I can look into that.` … `t10 Agent: just so you know this call is recorded, I'm Lavinia.` → end 2;
    agent absent; notice none; `late_mentions` for both.