Tickets are flagged when submitted by users who are not signed in to prevent potential security risks. This is because it's easy for someone to submit a ticket using an email address they don't own.
Allowing ticket submissions without signing in can be convenient for users, but it also opens up opportunities for social engineering. Flagging these tickets helps identify and manage potential risks, ensuring that your support system remains secure.
A flagged ticket in Zendesk indicates a potential risk associated with the ticket. This happens when an unknown user adds a comment or when a ticket is submitted by a user who isn't signed in. When a ticket is flagged, a warning icon appears beside…
Handling a flagged ticket in Zendesk involves assessing the comment and deciding on the appropriate action. If you're comfortable with the comment, you can ignore the warning flag and proceed as usual. However, if the comment raises concerns, you…
When an unknown user updates a ticket, their comment is flagged and added to the comment stream as a private note. This typically occurs when an email is forwarded to an unverified account, and the recipient replies. The flagging of such comments…
Currently, you cannot remove the flag from a ticket in Zendesk. The flag serves as a warning and remains as part of the ticket's metadata. If you're comfortable with the flagged comment, you can proceed with handling the ticket as usual. If not,…
Tickets from Typeform might be flagged if they are submitted by users who are not signed in or if the email addresses used are not recognized by Zendesk. This flagging is a security measure to prevent potential risks associated with unverified…