<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>question Best practice for email correlation between ServiceNow CSM and customer's ticketing system in Community Central forum</title>
    <link>https://www.servicenow.com/community/community-central-forum/best-practice-for-email-correlation-between-servicenow-csm-and/m-p/3591513#M7778</link>
    <description>&lt;P class=""&gt;Hi all,&lt;/P&gt;&lt;P&gt;we have a CSM email integration scenario where both ServiceNow and the customer use their own ticketing systems.&lt;/P&gt;&lt;P&gt;The customer sends emails from their ticketing system to our ServiceNow CSM mailbox. Their external ticket number is part of the subject, for example:&lt;/P&gt;&lt;P&gt;Ticket: EXT-123456 - "open tickets"&lt;/P&gt;&lt;P&gt;ServiceNow creates a Case, e.g. CS0012345, and sends an automatic notification back to the customer's service desk.&lt;/P&gt;&lt;P&gt;The ServiceNow notification subject is currently something like:&lt;/P&gt;&lt;P&gt;CS0012345 - A new case has been opened&lt;/P&gt;&lt;P&gt;ServiceNow also adds its normal Ref:MSG... watermark to the email.&lt;/P&gt;&lt;P&gt;The problem is that the customer's ticketing system requires &lt;STRONG&gt;its own ticket number (EXT-123456) in the subject&lt;/STRONG&gt; to associate the incoming email with the existing ticket. If the external ticket number is no longer present, the customer system may create a new ticket, potentially resulting in an email/ticket ping-pong.&lt;/P&gt;&lt;P&gt;On the ServiceNow Case, correlation_id and correlation_display are currently empty.&lt;/P&gt;&lt;P&gt;What is the recommended ServiceNow approach for this kind of &lt;STRONG&gt;email-to-email ticket system communication&lt;/STRONG&gt;?&lt;/P&gt;&lt;P&gt;In particular:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;Is there an OOTB/recommended mechanism to retain an external ticket reference from an inbound email and reuse it in outbound notification subjects?&lt;/LI&gt;&lt;LI&gt;Should the external ticket number be stored in correlation_id, or is that field intended for a different correlation scenario?&lt;/LI&gt;&lt;LI&gt;Would you recommend storing the customer's ticket number in a dedicated Case field and using it in the notification subject?&lt;/LI&gt;&lt;LI&gt;How should this work together with ServiceNow's existing Ref:MSG... watermark?&lt;/LI&gt;&lt;LI&gt;Is there a standard approach to prevent autoresponse loops when both ServiceNow and the external ticketing system generate automatic notifications?&lt;/LI&gt;&lt;LI&gt;Ideally, this behavior should be configurable only for customers/service desk mailboxes that require external ticket correlation.&lt;/LI&gt;&lt;/UL&gt;</description>
    <pubDate>Wed, 26 Aug 2026 12:10:43 GMT</pubDate>
    <dc:creator>sn-ushi</dc:creator>
    <dc:date>2026-08-26T12:10:43Z</dc:date>
    <item>
      <title>Best practice for email correlation between ServiceNow CSM and customer's ticketing system</title>
      <link>https://www.servicenow.com/community/community-central-forum/best-practice-for-email-correlation-between-servicenow-csm-and/m-p/3591513#M7778</link>
      <description>&lt;P class=""&gt;Hi all,&lt;/P&gt;&lt;P&gt;we have a CSM email integration scenario where both ServiceNow and the customer use their own ticketing systems.&lt;/P&gt;&lt;P&gt;The customer sends emails from their ticketing system to our ServiceNow CSM mailbox. Their external ticket number is part of the subject, for example:&lt;/P&gt;&lt;P&gt;Ticket: EXT-123456 - "open tickets"&lt;/P&gt;&lt;P&gt;ServiceNow creates a Case, e.g. CS0012345, and sends an automatic notification back to the customer's service desk.&lt;/P&gt;&lt;P&gt;The ServiceNow notification subject is currently something like:&lt;/P&gt;&lt;P&gt;CS0012345 - A new case has been opened&lt;/P&gt;&lt;P&gt;ServiceNow also adds its normal Ref:MSG... watermark to the email.&lt;/P&gt;&lt;P&gt;The problem is that the customer's ticketing system requires &lt;STRONG&gt;its own ticket number (EXT-123456) in the subject&lt;/STRONG&gt; to associate the incoming email with the existing ticket. If the external ticket number is no longer present, the customer system may create a new ticket, potentially resulting in an email/ticket ping-pong.&lt;/P&gt;&lt;P&gt;On the ServiceNow Case, correlation_id and correlation_display are currently empty.&lt;/P&gt;&lt;P&gt;What is the recommended ServiceNow approach for this kind of &lt;STRONG&gt;email-to-email ticket system communication&lt;/STRONG&gt;?&lt;/P&gt;&lt;P&gt;In particular:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;Is there an OOTB/recommended mechanism to retain an external ticket reference from an inbound email and reuse it in outbound notification subjects?&lt;/LI&gt;&lt;LI&gt;Should the external ticket number be stored in correlation_id, or is that field intended for a different correlation scenario?&lt;/LI&gt;&lt;LI&gt;Would you recommend storing the customer's ticket number in a dedicated Case field and using it in the notification subject?&lt;/LI&gt;&lt;LI&gt;How should this work together with ServiceNow's existing Ref:MSG... watermark?&lt;/LI&gt;&lt;LI&gt;Is there a standard approach to prevent autoresponse loops when both ServiceNow and the external ticketing system generate automatic notifications?&lt;/LI&gt;&lt;LI&gt;Ideally, this behavior should be configurable only for customers/service desk mailboxes that require external ticket correlation.&lt;/LI&gt;&lt;/UL&gt;</description>
      <pubDate>Wed, 26 Aug 2026 12:10:43 GMT</pubDate>
      <guid>https://www.servicenow.com/community/community-central-forum/best-practice-for-email-correlation-between-servicenow-csm-and/m-p/3591513#M7778</guid>
      <dc:creator>sn-ushi</dc:creator>
      <dc:date>2026-08-26T12:10:43Z</dc:date>
    </item>
  </channel>
</rss>

