Skip to content

Document that /fin/escalate rejects user on Fin for Platforms - #617

Merged
rahulgdsouza merged 1 commit into
mainfrom
rgd/fin-escalate-standalone-user-rejected
Aug 6, 2026
Merged

Document that /fin/escalate rejects user on Fin for Platforms#617
rahulgdsouza merged 1 commit into
mainfrom
rgd/fin-escalate-standalone-user-rejected

Conversation

@rahulgdsouza

Copy link
Copy Markdown
Contributor

Why?

On Fin for Platforms there is no Intercom Helpdesk, so escalating by user — which would create a new conversation for a teammate — is rejected. The spec said the opposite, that escalating by user still creates a conversation and returns its ID, so anyone following it would build against a call that fails.

How?

Documents conversation_id as required on Fin for Platforms, with user marked unsupported on both the endpoint description and the request body.

Pairs with intercom/developer-docs#1087, which carries the same spec change plus the guide updates.

Generated with Claude Code

Escalating by `user` is not supported on Fin for Platforms — there is no
Intercom Helpdesk, so there is no Helpdesk conversation to create. The spec
previously said the opposite: that escalating by `user` "still creates the Fin
conversation, returned as intercom_conversation_id".

`conversation_id` is required on Fin for Platforms.

Co-Authored-By: Claude <noreply@anthropic.com>
@rahulgdsouza
rahulgdsouza marked this pull request as ready for review August 6, 2026 14:54
@rahulgdsouza
rahulgdsouza merged commit 1a59802 into main Aug 6, 2026
3 checks passed
@rahulgdsouza
rahulgdsouza deleted the rgd/fin-escalate-standalone-user-rejected branch August 6, 2026 15:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants