Problem:
When a conversation is converted to a ticket, attribute values on the conversation are not automatically populated into matching ticket fields, even when identically named fields exist on both objects. The two remain linked but maintain fully independent attribute sets.
This gap is not surfaced to users at the point of conversion, making it non-obvious until a workflow fails or an SLA is missed.
Impact
The most immediate consequence is SLA policy behavior. Because SLA policies in Intercom evaluate at the conversation level, a ticket with Urgency set on the ticket attribute, but not on the corresponding conversation attribute may not trigger or breach correctly. Teams populating ticket fields in good faith could be inadvertently creating invisible SLA gaps.
Additionally, any workflow conditioned on a ticket attribute will not fire as expected if that attribute was not populated at conversion time. This affects routing logic, automation triggers, and any Fin-based attribute detection, which does not carry over to tickets automatically.
Requested Feature
A native attribute mapping configuration allowing workspace admins to define field-level mappings between conversation attributes and ticket attributes. When a conversion occurs, values from mapped source fields would be written into their designated target fields automatically before any workflows evaluate the new ticket.