Skip to content

Document API email-reply bot-comment behavior on replyConversation #551

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
markdennis22 merged 5 commits into from
Jun 17, 2026
Merged

Document API email-reply bot-comment behavior on replyConversation #551

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
5 commits
Select commit Hold shift + click to select a range
6a3f35f
Document API email-reply bot-comment behavior on replyConversation
markdennis22 Jun 16, 2026
9518d43
Tighten replyConversation admonition copy
markdennis22 Jun 17, 2026
cde688b
Rewrite replyConversation admonition in Intercom voice
markdennis22 Jun 17, 2026
c12e924
Align replyConversation admonition with Intercom style guide
markdennis22 Jun 17, 2026
90997a0
Backport replyConversation email-reply admonition to v2.7-v2.14
markdennis22 Jun 17, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 8 additions & 2 deletions descriptions/0/api.intercom.io.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -11044,8 +11044,14 @@ paths:
tags:
- Conversations
operationId: replyConversation
description: You can reply to a conversation with a message from an admin or
on behalf of a contact, or with a note for admins.
description: |-
You can reply to a conversation with a message from an admin or on behalf of a contact, or with a note for admins.

{% admonition type="warning" name="Bot replies to inbound email" %}
By default, bot or Operator replies to an inbound email conversation aren't sent to your customer. The reply is stored as an unnotifiable bot comment, and no `seen` receipt is generated until an email is actually delivered.

To send these replies as outbound emails, reach out to your accounts team to enable the email-reply feature flag for your workspace.
{% /admonition %}
responses:
'200':
description: User last conversation reply
Expand Down
10 changes: 8 additions & 2 deletions descriptions/2.10/api.intercom.io.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -5016,8 +5016,14 @@ paths:
tags:
- Conversations
operationId: replyConversation
description: You can reply to a conversation with a message from an admin or
on behalf of a contact, or with a note for admins.
description: |-
You can reply to a conversation with a message from an admin or on behalf of a contact, or with a note for admins.

{% admonition type="warning" name="Bot replies to inbound email" %}
By default, bot or Operator replies to an inbound email conversation aren't sent to your customer. The reply is stored as an unnotifiable bot comment, and no `seen` receipt is generated until an email is actually delivered.

To send these replies as outbound emails, reach out to your accounts team to enable the email-reply feature flag for your workspace.
{% /admonition %}
responses:
'200':
description: User last conversation reply
Expand Down
10 changes: 8 additions & 2 deletions descriptions/2.11/api.intercom.io.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -5134,8 +5134,14 @@ paths:
tags:
- Conversations
operationId: replyConversation
description: You can reply to a conversation with a message from an admin or
on behalf of a contact, or with a note for admins.
description: |-
You can reply to a conversation with a message from an admin or on behalf of a contact, or with a note for admins.

{% admonition type="warning" name="Bot replies to inbound email" %}
By default, bot or Operator replies to an inbound email conversation aren't sent to your customer. The reply is stored as an unnotifiable bot comment, and no `seen` receipt is generated until an email is actually delivered.

To send these replies as outbound emails, reach out to your accounts team to enable the email-reply feature flag for your workspace.
{% /admonition %}
responses:
'200':
description: User last conversation reply
Expand Down
10 changes: 8 additions & 2 deletions descriptions/2.12/api.intercom.io.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -5702,8 +5702,14 @@ paths:
tags:
- Conversations
operationId: replyConversation
description: You can reply to a conversation with a message from an admin or
on behalf of a contact, or with a note for admins.
description: |-
You can reply to a conversation with a message from an admin or on behalf of a contact, or with a note for admins.

{% admonition type="warning" name="Bot replies to inbound email" %}
By default, bot or Operator replies to an inbound email conversation aren't sent to your customer. The reply is stored as an unnotifiable bot comment, and no `seen` receipt is generated until an email is actually delivered.

To send these replies as outbound emails, reach out to your accounts team to enable the email-reply feature flag for your workspace.
{% /admonition %}
responses:
'200':
description: User last conversation reply
Expand Down
10 changes: 8 additions & 2 deletions descriptions/2.13/api.intercom.io.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -6585,8 +6585,14 @@ paths:
tags:
- Conversations
operationId: replyConversation
description: You can reply to a conversation with a message from an admin or
on behalf of a contact, or with a note for admins.
description: |-
You can reply to a conversation with a message from an admin or on behalf of a contact, or with a note for admins.

{% admonition type="warning" name="Bot replies to inbound email" %}
By default, bot or Operator replies to an inbound email conversation aren't sent to your customer. The reply is stored as an unnotifiable bot comment, and no `seen` receipt is generated until an email is actually delivered.

To send these replies as outbound emails, reach out to your accounts team to enable the email-reply feature flag for your workspace.
{% /admonition %}
responses:
'200':
description: User last conversation reply
Expand Down
10 changes: 8 additions & 2 deletions descriptions/2.14/api.intercom.io.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -7403,8 +7403,14 @@ paths:
tags:
- Conversations
operationId: replyConversation
description: You can reply to a conversation with a message from an admin or
on behalf of a contact, or with a note for admins.
description: |-
You can reply to a conversation with a message from an admin or on behalf of a contact, or with a note for admins.

{% admonition type="warning" name="Bot replies to inbound email" %}
By default, bot or Operator replies to an inbound email conversation aren't sent to your customer. The reply is stored as an unnotifiable bot comment, and no `seen` receipt is generated until an email is actually delivered.

To send these replies as outbound emails, reach out to your accounts team to enable the email-reply feature flag for your workspace.
{% /admonition %}
responses:
'200':
description: User last conversation reply
Expand Down
10 changes: 8 additions & 2 deletions descriptions/2.15/api.intercom.io.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -7474,8 +7474,14 @@ paths:
tags:
- Conversations
operationId: replyConversation
description: You can reply to a conversation with a message from an admin or
on behalf of a contact, or with a note for admins.
description: |-
You can reply to a conversation with a message from an admin or on behalf of a contact, or with a note for admins.

{% admonition type="warning" name="Bot replies to inbound email" %}
By default, bot or Operator replies to an inbound email conversation aren't sent to your customer. The reply is stored as an unnotifiable bot comment, and no `seen` receipt is generated until an email is actually delivered.

To send these replies as outbound emails, reach out to your accounts team to enable the email-reply feature flag for your workspace.
{% /admonition %}
responses:
'200':
description: User last conversation reply
Expand Down
10 changes: 8 additions & 2 deletions descriptions/2.7/api.intercom.io.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -5204,8 +5204,14 @@ paths:
tags:
- Conversations
operationId: replyConversation
description: You can reply to a conversation with a message from an admin or
on behalf of a contact, or with a note for admins.
description: |-
You can reply to a conversation with a message from an admin or on behalf of a contact, or with a note for admins.

{% admonition type="warning" name="Bot replies to inbound email" %}
By default, bot or Operator replies to an inbound email conversation aren't sent to your customer. The reply is stored as an unnotifiable bot comment, and no `seen` receipt is generated until an email is actually delivered.

To send these replies as outbound emails, reach out to your accounts team to enable the email-reply feature flag for your workspace.
{% /admonition %}
responses:
'200':
description: User last conversation reply
Expand Down
10 changes: 8 additions & 2 deletions descriptions/2.8/api.intercom.io.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -5204,8 +5204,14 @@ paths:
tags:
- Conversations
operationId: replyConversation
description: You can reply to a conversation with a message from an admin or
on behalf of a contact, or with a note for admins.
description: |-
You can reply to a conversation with a message from an admin or on behalf of a contact, or with a note for admins.

{% admonition type="warning" name="Bot replies to inbound email" %}
By default, bot or Operator replies to an inbound email conversation aren't sent to your customer. The reply is stored as an unnotifiable bot comment, and no `seen` receipt is generated until an email is actually delivered.

To send these replies as outbound emails, reach out to your accounts team to enable the email-reply feature flag for your workspace.
{% /admonition %}
responses:
'200':
description: User last conversation reply
Expand Down
10 changes: 8 additions & 2 deletions descriptions/2.9/api.intercom.io.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -5208,8 +5208,14 @@ paths:
tags:
- Conversations
operationId: replyConversation
description: You can reply to a conversation with a message from an admin or
on behalf of a contact, or with a note for admins.
description: |-
You can reply to a conversation with a message from an admin or on behalf of a contact, or with a note for admins.

{% admonition type="warning" name="Bot replies to inbound email" %}
By default, bot or Operator replies to an inbound email conversation aren't sent to your customer. The reply is stored as an unnotifiable bot comment, and no `seen` receipt is generated until an email is actually delivered.

To send these replies as outbound emails, reach out to your accounts team to enable the email-reply feature flag for your workspace.
{% /admonition %}
responses:
'200':
description: User last conversation reply
Expand Down