Skip to content

Commit 0ad79bb

Browse 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>
1 parent ad8d4a0 commit 0ad79bb

1 file changed

Lines changed: 13 additions & 9 deletions

File tree

‎descriptions/0/api.intercom.io.yaml‎

Lines changed: 13 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -15411,7 +15411,9 @@ paths:
1541115411
- Conversations
1541215412
operationId: listTeamHandlingSegments
1541315413
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.
1541515417

1541615418
Periods with no team assigned are returned with `team` set to `null`. `ended_at` is `null` while a period is still open.
1541715419

@@ -15434,15 +15436,15 @@ paths:
1543415436
started_at: "2026-01-20T13:10:05Z"
1543515437
ended_at: "2026-01-20T13:20:00Z"
1543615438
start_reason:
15437-
end_reason: team_change
15439+
end_reason: assignment
1543815440
- team:
1543915441
type: team
1544015442
id: '113'
1544115443
name: Refunds
15442-
started_at: "2026-01-20T13:20:00Z"
15444+
started_at: "2026-01-20T13:24:30Z"
1544315445
ended_at: "2026-01-20T13:31:44Z"
15444-
start_reason: team_change
15445-
end_reason: assignment
15446+
start_reason:
15447+
end_reason: close
1544615448
'400':
1544715449
description: Intercom-Version is not Preview
1544815450
content:
@@ -42203,13 +42205,15 @@ components:
4220342205
start_reason:
4220442206
type: string
4220542207
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
4220742210
example: team_change
4220842211
end_reason:
4220942212
type: string
4221042213
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
42216+
is still open.
4221342217
example: assignment
4221442218
team_handling_segment_list:
4221542219
title: Team Handling Segment List
@@ -42227,7 +42231,7 @@ components:
4222742231
started_at: "2026-09-28T10:10:00Z"
4222842232
ended_at: "2026-09-28T10:20:00Z"
4222942233
start_reason:
42230-
end_reason: team_change
42234+
end_reason: assignment
4223142235
team_list:
4223242236
title: Team List
4223342237
type: object

0 commit comments

Comments
 (0)