What this operation supports in Intercom
Retrieves a single conversation by its ID, including its message parts, participants, and current state (open, closed, or snoozed).
Implementation details
A conversation's parts include both customer-visible replies and internal notes from teammates, so distinguishing between the two matters when displaying or processing this data.
Operational considerations
Since conversations often contain customer-provided personal information, applying the same access controls used elsewhere in the integration keeps that data appropriately restricted.
Use cases
4–7 concrete use cases: context before replies, support QA, handoff to teams, and reporting by conversation type.