Redacting ticket content

<body>
<div class="article-banners">
<div id="docs-wmp-link">
<a href="https://support.zendesk.com/hc/en-us/articles/5411234991258-plan" rel="noopener" target="_blank">What's my plan?</a>
</div>

<div class="article-banner" id="suite_all">
<table>
<tbody>
<tr>
<td>
<strong>All Suites</strong>
</td>
<td>Team, Growth, Professional, Enterprise, or Enterprise Plus</td>
</tr>
</tbody>
</table>
</div>

<div class="article-banner" id="support_all">
<table>
<tbody>
<tr>
<td>
<strong>Support</strong>
</td>
<td>Team, Professional, or Enterprise</td>
</tr>
</tbody>
</table>
</div>

</div>
<div id="docs-ai-summary">
<p id="docs-ai-summary-toggle">Verified AI summary <span id="up-triangle">◀</span><span id="down-triangle">▼</span></p>
<p id="docs-ai-summary-content">
Redact sensitive information like credit card numbers and passwords from ticket comments and attachments to maintain security and compliance. Use the Agent Workspace to mark and remove data from email, messaging, and side conversations. Note that redaction is irreversible and doesn't affect external channels. Limitations include active chats and SMS. The <code>redacted_content</code> tag helps track redacted tickets.
</p>
</div>

<div class="body">

<p class="p" dir="ltr">Customers sometimes enter sensitive information such as credit card numbers, social
security numbers, passwords, attachments, or other sensitive information in tickets when they
shouldn't. In addition to being visible to anybody with access to the ticket, the sensitive
information automatically gets stored in a database with the rest of the ticket. </p>
<p class="p" dir="ltr">In the <a class="xref" href="https://support.zendesk.com/hc/en-us/articles/4408821259930" target="_blank">Zendesk Agent Workspace</a>, you can use ticket redaction
to redact personal data. You don’t need to install a separate app. You must have the Agent
Workspace <a class="xref" href="https://support.zendesk.com/hc/en-us/articles/4581758611866" target="_blank">activated</a> to use ticket redaction.
</p>
<div class="note tip" id="topic-1__note_alz_nyr_hfc">
<span class="tiptitle">Tip:</span> Customers with the <a class="xref" href="https://support.zendesk.com/hc/en-us/articles/6561144266906" target="_blank">Advanced Data Privacy and Protection add-on</a> can use <a class="xref" href="https://support.zendesk.com/hc/en-us/articles/6669399593882" target="_blank">redaction suggestions</a> to highlight sensitive data within ticket
comments. The add-on also allows you to create ticket triggers to <a class="xref" href="https://support.zendesk.com/hc/en-us/articles/9248330321050" target="_blank">redact sensitive data automatically</a>.</div>
<p class="p">This article contains the following sections: </p>
<ul class="ul" id="topic-1__ul_mct_b21_bhb">
<li class="li"><a class="xref" href="#topic_eyp_5rl_znb">About ticket redaction</a></li>
<li class="li"><a class="xref" href="#topic_hrl_lm4_ysb">Ticket redaction limitations</a></li>
<li class="li"><a class="xref" href="#topic_wrc_nsl_znb">Redacting ticket content</a></li>
<li class="li"><a class="xref" href="#id_m12_ngy_kwb">Redacting ticket content in side
conversations</a></li>
</ul>
<p class="p">Related articles:</p>
<ul class="ul" id="topic-1__ul_njm_mvt_ncc">
<li class="li"><a class="xref" href="https://support.zendesk.com/hc/en-us/articles/6669399593882" target="_blank">Automatically detecting sensitive information for redaction</a></li>
<li class="li"><a class="xref" href="https://support.zendesk.com/hc/en-us/articles/4408822124314" target="_blank">Automatically redacting credit card numbers from tickets</a></li>
</ul>
</div>
<div aria-labelledby="ariaid-title2" class="topic nested1" id="topic_eyp_5rl_znb">
<h2 class="title topictitle2" id="ariaid-title2">About ticket redaction</h2>
<div class="body">
<p class="p">Admins and <a class="xref" href="https://support.zendesk.com/hc/en-us/articles/4408882153882" target="_blank">agents in custom roles with permission</a> can redact,
or remove, sensitive information found in ticket comments and attachments so that your
account stays secure and compliant. This helps keep confidential information out of Zendesk.
On plans without custom roles, agents with permission to delete tickets can also redact.</p>
<p class="p" dir="ltr">Ticket redaction works on: </p>
<ul class="ul" id="topic_eyp_5rl_znb__ul_qgt_fsl_znb">
<li class="li" dir="ltr">Email</li>
<li class="li">Side conversation emails, child tickets, and Microsoft Teams messages</li>
<li class="li">Social messaging channels enabled through Sunshine Conversations</li>
<li class="li">Web and mobile messaging</li>
<li class="li" dir="ltr">Ended chat conversations from the Agent Workspace</li>
<li class="li" dir="ltr">Public comments</li>
<li class="li" dir="ltr">Internal notes</li>
<li class="li" dir="ltr">Images (attached and inline)</li>
<li class="li" dir="ltr">Attachments (with some <a class="xref" href="#topic_hrl_lm4_ysb">limitations</a>)</li>
<li class="li" dir="ltr">Content in archived or closed tickets for messaging, email, API, and webform
channels</li>
<li class="li">Tickets created through the Sunshine Conversations SDK. </li>
</ul>
<p class="p" dir="ltr">Ticket redaction does not currently support redaction of entire tickets. Also,
make sure you redact all sensitive content before merging tickets:</p>
<ul class="ul" id="topic_eyp_5rl_znb__ul_ld1_jbv_s1c">
<li class="li">If you redact content in the original ticket after it has been merged with another
ticket, the redacted content will be removed from the original ticket, but not from the
merged ticket.
</li>
<li class="li">It is not possible to redact information, including attachments, from the internal note
that is created when you merge a ticket. </li>
</ul>
<p class="p">Any redaction on a ticket breaks the ability to view original emails on all comments,
including those that came in before the redacted comment. The original email is also not
viewable for additional inbound email comments on that ticket. See <a class="xref" href="https://support.zendesk.com/hc/en-us/articles/4408832876442#topic_ewx_yss_y1c" target="_blank">Understanding when the original email is not viewable in
Zendesk</a>.</p>
<p class="p">If you redact a Zendesk message or a message created via the Sunshine Conversations SDK,
the Support ticket interface shows the redacted areas of the messaging conversation, all
within the context of the unredacted content. From the customer side, the entire message is
deleted. </p>
<p class="p" dir="ltr">Redaction events are noted in a ticket’s event log so customers can be aware data
has been deleted. In addition, when you redact ticket content, a <strong class="ph b">redacted_content</strong> tag
is automatically added to the ticket. When you redact ticket content, this causes an update
to be made on the ticket using the same channel associated with the content that was
redacted. For example, redacting a WhatsApp comment from a ticket. This behavior can cause
triggers to fire if your trigger conditions are set to look for updates on a specific
channel. </p>
<p class="p">If you redact content on a <a class="xref" href="https://support.zendesk.com/hc/en-us/articles/8037649972634" target="_blank">ticket with an AI-generated summary</a>, the summary can be removed
from the ticket by refreshing the summary or closing and reopening the Agent Workspace tab.
The summary is immediately removed from Zendesk's systems when a redaction is performed on a
ticket, but the summary continues to appear in the browser until the page is reloaded.</p>
</div>
<div aria-labelledby="ariaid-title3" class="topic nested2" id="topic_hrl_lm4_ysb">
<h3 class="title topictitle3" id="ariaid-title3">Ticket redaction limitations</h3>
<div class="body">
<div class="p">Ticket redaction does not work on:<ul class="ul" id="topic_hrl_lm4_ysb__ul_iyf_yfy_kwb">
<li class="li">Messages in an active chat
</li>
<li class="li">Ticket comments created from SMS
</li>
<li class="li">Translated messages. This limitation applies to all web, mobile, and social
messaging channels.
</li>
<li class="li">Messages stored in the Zendesk bot service and in third-party bot services
</li>
<li class="li">Channel framework-enabled tickets</li>
<li class="li">Ticket comments created from Mobile SDK, including those submitted through Zendesk's
support apps </li>
<li class="li">Tickets created from Slack Business Connect</li>
<li class="li">Slack side conversations</li>
<li class="li" dir="ltr">Content in archived or closed tickets for live chat channels
</li>
<li class="li">
<a class="xref" href="https://support.zendesk.com/hc/en-us/articles/4408836323738-Understanding-answer-step-types#topic_mnf_gwc_k4b" target="_blank">Quick reply</a> and <a class="xref" href="https://support.zendesk.com/hc/en-us/articles/4408836323738-Understanding-answer-step-types#topic_il3_pmj_tvb" target="_blank">carousel</a> steps displayed in the Agent
Workspace ticket interface</li>
<li class="li">Call summaries and transcriptions in Contact Center
</li>
</ul>
</div>
<p class="p">Additional limitations include:
</p>
<ul class="ul" id="topic_hrl_lm4_ysb__ul_vcf_qm4_ysb">
<li class="li">You must have a <a class="xref" href="https://support.zendesk.com/hc/en-us/articles/4408832171034#topic_zys_xht_qmb" target="_blank">chat role</a> to redact ticket content in chat or
messaging conversations. </li>
<li class="li">When you redact a ticket comment sent from an email channel, Zendesk does not redact
the content of the original email in the email provider's channel (such as Gmail or
Yahoo). Only the text hosted in Zendesk is redacted. </li>
<li class="li">When redacting a ticket, the underlying conversation is not edited on the social
messaging platform and third-party integrations. It is redacted only within
Zendesk-controlled systems. This also means that an end user, depending on how they
communicate with your agent, may still see unredacted content themselves when accessing
a message through different channels. For example, in Facebook Messenger or a 3rd-party
Chat bot. </li>
<li class="li">Redaction of messages exchanged between Zendesk bots, third-party bots, and end users
is not supported.</li>
<li class="li">If triggers are configured prior to redaction taking place, redacted content may
persist in the channels launched by these triggers. For example, email
conversations.</li>
<li class="li">Ticket redaction for the live chat history may not be instantaneous and may be delayed
by up to 10 minutes due to database replication.</li>
<li class="li">Bulk redaction is not supported.</li>
<li class="li">A maximum of 75 attachments can be redacted at once.</li>
</ul>
</div>
</div>
</div>
<div aria-labelledby="ariaid-title4" class="topic nested1" id="topic_wrc_nsl_znb">
<h2 class="title topictitle2" id="ariaid-title4">Redacting ticket content</h2>
<div class="body">
<div class="note important">
<span class="importanttitle">Important:</span> Ticket redaction cannot be reversed. Use caution when marking content
for redaction. Also, rich text formatting in a message may be lost when redacting.</div>
<p class="p"><strong class="ph b">To redact ticket content</strong></p>
<ol class="ol" id="topic_wrc_nsl_znb__ol_ugx_2tl_znb">
<li class="li">Open a ticket and scroll to the conversation thread that contains the content you want
to redact. <p class="p">You can only redact content in one thread at a time. Not all tickets can be
redacted. See <a class="xref" href="#topic_hrl_lm4_ysb">Ticket redaction limitations</a>.</p>
</li>
<li class="li">Hover your mouse over the thread to display the options menu icon (<img class="image" id="topic_wrc_nsl_znb__image_scv_zqc_dx" src="https://zen-marketing-documentation.s3.amazonaws.com/docs/en/options-menu-icon-small.png">).</li>
<li class="li">Click the options menu icon (<img class="image" id="topic_wrc_nsl_znb__image_ovn_ntl_znb" src="https://zen-marketing-documentation.s3.amazonaws.com/docs/en/options-menu-icon-small.png">) and select <strong class="ph b">Mark text for redaction</strong>.<p class="p"><img class="image img-screenshot" id="topic_wrc_nsl_znb__image_wvs_ztl_znb" src="https://zen-marketing-documentation.s3.amazonaws.com/docs/en/uc_ticket_redact_option2.png" width="500"></p>
<p class="p">A redaction
pane appears. </p>
</li>
<li class="li">Select the content you want to redact, then click <strong class="ph b">Mark for redaction</strong>. <p class="p">The
content you want to redact is highlighted.</p>
<p class="p"><img class="image" id="topic_wrc_nsl_znb__image_tvc_h5l_znb" src="https://zen-marketing-documentation.s3.amazonaws.com/docs/en/uc_ticket_redact_mark.png" width="500"></p>
</li>
<li class="li">Continue to select content to redact and <strong class="ph b">Mark it for redaction</strong>.<p class="p">You can include
multiple text strings, attachments, and images as part of the same redaction.
</p>
<p class="p"><img class="image" id="topic_wrc_nsl_znb__image_qr3_x5l_znb" src="https://zen-marketing-documentation.s3.amazonaws.com/docs/en/uc_ticket_redact_attachment.png" width="500"></p>
<p class="p">If you mark something for redaction by
mistake, click the content and select <strong class="ph b">Unmark for redaction</strong>.</p>
<p class="p"><img class="image" id="topic_wrc_nsl_znb__image_dxn_fvl_znb" src="https://zen-marketing-documentation.s3.amazonaws.com/docs/en/uc_ticket_redact_unmark.png" width="250"></p>
</li>
<li class="li">When you’ve finished selecting the content you want to redact, click <strong class="ph b">Redact</strong>.
<p class="p"><img class="image" id="topic_wrc_nsl_znb__image_ll1_nvl_znb" src="https://zen-marketing-documentation.s3.amazonaws.com/docs/en/uc_ticket_redact_both.png" width="500"></p>
<p class="p">The ticket is updated with the redacted
content. Ticket redaction is not reversible. </p>
<p class="p"><img class="image" id="topic_wrc_nsl_znb__image_nbt_qvl_znb" src="https://zen-marketing-documentation.s3.amazonaws.com/docs/en/uc_ticket_redact_done.png" width="500"></p>
<p class="p">When you redact ticket content, a
<strong class="ph b">redacted_content</strong> tag is automatically added to the ticket. You can <a class="xref" href="https://support.zendesk.com/hc/en-us/articles/4408882086298" target="_blank">search</a> for this tag to get a list of redacted
tickets.</p>
</li>
</ol>
<div class="note" id="topic_wrc_nsl_znb__note_lrf_hdf_z1c">
<span class="notetitle">Note:</span> If you have a ticket and you redact only one instance of a phrase
that appears multiple times in ticket comments, only that instance will be redacted. To keep
the phrase from being visible across multiple ticket comments, you must redact all
instances.</div>
</div>
</div>
<div aria-labelledby="ariaid-title5" class="topic nested1" id="id_m12_ngy_kwb">
<h2 class="title topictitle2" id="ariaid-title5">Redacting ticket content in side conversations</h2>
<div class="body">
<div class="note">
<span class="notetitle">Note:</span> You must be on a Suite Professional plan or above to use side conversations. Side
conversations are not available on Support only plans. See <a class="xref" href="https://support.zendesk.com/hc/en-us/articles/4408844206746" target="_blank">About side conversations</a>.</div>
<div class="p">You can also redact content in side conversations in both the Agent Workspace and the
standard agent interface. Content can be redacted on the following side conversations
channels:<ul class="ul" id="id_m12_ngy_kwb__ul_xdk_s1f_zwb">
<li class="li">Email</li>
<li class="li">Microsoft Teams</li>
<li class="li">Child tickets</li>
</ul>
</div>
<div class="p">When you redact content in a side conversation, keep in mind:<ul class="ul" id="id_m12_ngy_kwb__ul_bqx_t1f_zwb">
<li class="li">The redaction is only applied to the content in the side conversation. The content
isn't redacted on the external channels on which it was delivered, such as an email or
Microsoft Teams message.</li>
<li class="li">When you redact content on a side conversation child ticket, the redaction only takes
place on the side conversation. You must separately redact the content in the child
ticket.</li>
<li class="li">The <strong class="ph b">redacted_content</strong> ticket tag isn't automatically added to the ticket.</li>
</ul>
</div>
<p class="p">Side conversation redaction in the Agent Workspace:</p>
<p class="p"><img class="image img-screenshot" id="id_m12_ngy_kwb__image_uqs_d3y_kwb" src="https://zen-marketing-documentation.s3.amazonaws.com/docs/en/redact_sideconvo_cnxtpanel2.png" width="300"></p>
<p class="p">Side conversation redaction in the standard agent interface:</p>
<p class="p"><img class="image img-screenshot" id="id_m12_ngy_kwb__image_lcy_d3y_kwb" src="https://zen-marketing-documentation.s3.amazonaws.com/docs/en/redact_sideconvo_standard.png" width="300"></p>
</div>
</div>
<script id="ai-summary-script">
//<![CDATA[
const ai_summary_style = document.createElement('style');
ai_summary_style.innerHTML = `#styled-article-body{padding:0 0 0}#article-body #docs-ai-summary{background-color:#f3f3f3;border:1px solid #d3d3d3;padding:10px 10px 6px;margin-bottom:16px}#article-body #docs-ai-summary #docs-ai-summary-toggle{font-size:.9em;font-weight:700;margin-bottom:4px;cursor:pointer;display:flex;justify-content:space-between;align-items:center}#article-body #docs-ai-summary #docs-ai-summary-toggle #up-triangle{margin-left:auto;padding-right:10px;display:none}#article-body #docs-ai-summary #docs-ai-summary-toggle #down-triangle{margin-left:auto;padding-right:10px}#article-body #docs-ai-summary #docs-ai-summary-content{font-size:.9em;padding-left:25px;padding-right:25px;margin-bottom:12px}`;
document.head.appendChild(ai_summary_style);

const toggleAISummary = () => {
const summary = document.getElementById("docs-ai-summary-content");
const upTriangle = document.getElementById("up-triangle");
const downTriangle = document.getElementById("down-triangle");
if (summary.style.display === "none") {
summary.style.display = "block";
upTriangle.style.display = "none";
downTriangle.style.display = "inline";
} else {
summary.style.display = "none";
upTriangle.style.display = "inline";
downTriangle.style.display = "none";
}
};

document.getElementById("docs-ai-summary-toggle").addEventListener("click", toggleAISummary);
//]]>
</script>
</body>