When we reply to an email conversation with POST /conversations/{id}/reply (message_type: comment, type: admin), the reply shows the email icon in the Inbox but no sender/recipient header. Replies written in the Inbox UI on the same conversation do show the header with from, to and cc.
The API response matches what the Inbox shows. A GET /conversations/{id} returns email_message_metadata.email_address_headers (from, to, cc, reply_to) for the UI reply. The API reply has no email_message_metadata at all. We checked with Intercom-Version 2.16 and 2.17 and got the same result. So we can’t confirm who an API reply went to, or whether it went out as an email at all. drop_reason doesn’t help either, because there are no headers to carry it.
What we’d like:
- API replies on email conversations record
email_message_metadatathe same way Inbox replies do, so the recipients and anydrop_reasoncan be read back. - Optionally,
to/ccfields on the reply endpoint, so an integration can set recipients explicitly, the way an agent can in the Inbox.
Context: we post support replies from an internal tool through the API, and we have to be able to show which customer contacts received each one.