You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 0ad79bb
Browse filesBrowse the repository at this point in the historyBrowse files
Clarify team handling segment start and end reasons (#704)
* Clarify team handling segment start and end reasons
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
* Say a team handling period never continues across a team change
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
* Allow for periods with no team in the team handling segments wording
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Copy file name to clipboardExpand all lines: descriptions/0/api.intercom.io.yaml
+13-9Lines changed: 13 additions & 9 deletions
Original file line number
Diff line number
Diff line change
@@ -15411,7 +15411,9 @@ paths:
15411
15411
- Conversations
15412
15412
operationId: listTeamHandlingSegments
15413
15413
description: |
15414
-
List the periods teammates actively handled a conversation, attributed to the team assigned to the conversation at the time. A period is split where the team changes. Teammate identity is not included; join with List handling events by time to recover it.
15414
+
Shows the time teammates spent actively working on a conversation, and which team the conversation was assigned to while they did. Each period covers a single team assignment, and never continues across a team change. `team` is `null` for time when no team was assigned. The response doesn't say which teammate did the work.
15415
+
15416
+
Moving a conversation to another team usually unassigns the teammate as well. Their period then ends with an `end_reason` of `assignment`, and the next period starts, with a `start_reason` of `null`, when a teammate picks the conversation up again. You'll only see `team_change` when the team changes and the same teammate keeps working without a break, for example when round robin assigns the conversation back to the teammate who already had it.
15415
15417
15416
15418
Periods with no team assigned are returned with `team` set to `null`. `ended_at` is `null` while a period is still open.
15417
15419
@@ -15434,15 +15436,15 @@ paths:
15434
15436
started_at: "2026-01-20T13:10:05Z"
15435
15437
ended_at: "2026-01-20T13:20:00Z"
15436
15438
start_reason:
15437
-
end_reason: team_change
15439
+
end_reason: assignment
15438
15440
- team:
15439
15441
type: team
15440
15442
id: '113'
15441
15443
name: Refunds
15442
-
started_at: "2026-01-20T13:20:00Z"
15444
+
started_at: "2026-01-20T13:24:30Z"
15443
15445
ended_at: "2026-01-20T13:31:44Z"
15444
-
start_reason: team_change
15445
-
end_reason: assignment
15446
+
start_reason:
15447
+
end_reason: close
15446
15448
'400':
15447
15449
description: Intercom-Version is not Preview
15448
15450
content:
@@ -42203,13 +42205,15 @@ components:
42203
42205
start_reason:
42204
42206
type: string
42205
42207
nullable: true
42206
-
description: team_change when the period starts at a team reassignment
42208
+
description: team_change when the team changed while the teammate kept
42209
+
handling without a break, otherwise null
42207
42210
example: team_change
42208
42211
end_reason:
42209
42212
type: string
42210
42213
nullable: true
42211
-
description: Why the period ended (assignment, snooze, close, away, auto_away,
42212
-
session_drop, team_change)
42214
+
description: Why the period ended (switch, assignment, reassign, snooze,
42215
+
close, away, auto_away, session_drop, team_change). Null while the period
0 commit comments