Help center Cases and collaboration Review spam and phishing assessments and manage sender exceptions Updated Wednesday, October 28, 2026 · Marcel Gravelle Message Security Review helps your support team investigate suspicious incoming email in the context of the customer case. It shows the available assessment, reasons and sender policy so an agent can make a deliberate decision. For B2B support, this is especially useful when an unfamiliar supplier, a new customer contact or a forwarded technical message looks unusual. A score helps prioritize investigation; your team still needs to confirm the sender, protect customer information and ensure legitimate requests receive attention. At a glanceFor: case-handling agents, support supervisors, email administrators and operations teams. Applies to: Supportbench Core.Start here: Open a Case → select an email activity → shield beside that message’s subject → Message Security Review Understand what the assessment does · Check access and the operating process · Open and interpret Message Security Review · Handle a suspicious message without losing a real customer request · Allow a verified sender deliberately · Block an exact sender with its full effect in mind · Use tags and workflows to create a monitored review process · Worked example: a new contact at an existing customer · Troubleshoot common assessment and policy questions Understand what the assessment does The current email-intake security check applies when a new Case is created from incoming email and Enable email security checks is enabled. It is not a promise that every reply on every existing Case has been assessed. An applicable sender or domain allow rule can bypass this assessment. Other email controls and processing rules still apply.An assessment is not a quarantine actionThe security assessment can label a message Blocked or Held for review, store its score and apply eligible tags while the new Case continues through normal processing and workflows. These labels describe the assessment. They do not, by themselves, prove that the Case was rejected, moved out of an agent queue, or held in a separate mailbox. Check the actual Case, routing and configured email rules.What you seeWhat you may concludeWhat you must not assumeA shield or warningAn assessment or saved security detail is available for review.The message has been physically quarantined.No shieldNo visible indicator is available in this context.The email passed every security check or is safe to open.AllowedThe assessment/policy describes an allowed outcome.All links, attachments or requests are trustworthy.Held for review or BlockedThe assessment warrants the corresponding level of investigation.No Case was created or no agent can see it.A spam or phishing tagThe Case can be found or handled by rules that use that tag.A review queue, Division or workflow has automatically been created.Keep your organization’s mailbox and security controls in place. Supportbench adds context to the support workflow; it does not replace your organization’s process for verifying suspicious requests. Check access and the operating process Confirm you can open the Case. The review and sender actions are authorized against the Case and the current agent’s access; they are not unrestricted tools for submitting arbitrary email addresses.Ask the account administrator to confirm Settings → Account → Policies → Enable email security checks. Do not assume it is enabled because another account or an older article said so.Identify who reviews suspicious messages, how often the review list is checked, and who can approve sender-policy exceptions. Make sure a backup person covers absences.Agree how to verify a sender through an already trusted contact method. A display name, familiar Company name or urgent request alone is insufficient evidence.Know where administrators manage Settings → Email configuration → Block/Allow list. An individual sender rule and a domain-wide rule have different scope.Case access and settings access are different. An agent may be authorized to use the Case’s sender actions without having administrative access to the full block/allow configuration. Your operational policy should still make responsibility clear. Open and interpret Message Security Review Open the Case and select the relevant email activity in the timeline so its message opens in the activity workbench. Locate the shield beside that email activity’s subject, rather than beside the overall Case title. Its accessible action is Open message security review.Open it to display Message Security Review. Read the sender address, not only the customer’s display name.Read the available score, category and verdict. A subtype or confidence value may be present; do not assume every assessment has every detail.Review Sender policy and, when shown, Domain policy. A policy affecting the entire domain can matter even when the specific sender has a different entry.Read Why this message was flagged. Use the actual reasons displayed for this message, rather than applying an assumed universal list of checks.Compare the request with the Case context and the known customer relationship. Use an approved independent contact route when verification is needed.Decide whether the Case needs ordinary support handling, a monitored review owner or escalation to your security process. Record the operational decision in an appropriate internal note.The shield is available when the selected activity has a saved security score or assessment details. It is suppressed for escalation drafts. If it is absent, first confirm that you selected the intended email activity; absence is not a clean assessment.A red indicator corresponds to a Block assessment or a high warning score of at least 80. A Hold assessment or another positive warning score below that level uses the warning treatment. Saved assessment detail can also make a review available when the recorded score is zero. Color is a shortcut to inspection, not a complete explanation of risk.When complete stored assessment details are unavailable or invalid, the review can reconstruct available information from the saved score, tags and policies. Treat missing reasons or confidence as missing evidence. Do not reinterpret an incomplete or zero-valued display as proof that a full clean assessment took place. Handle a suspicious message without losing a real customer request SituationRecommended operational responseVerificationUnexpected invoice or account-change requestFollow your organization’s verification process using an established contact method. Assign a responsible reviewer.Confirm the request with a trusted contact before acting on the requested change.Technical customer email flagged after forwardingInspect the actual sender and context; confirm whether the forwarded request is legitimate.Check the Case’s contact, Company and request details rather than relying on the display name.Repeated unsolicited mailReview the sender policy and discuss a narrowly scoped block rule with the responsible owner.Confirm it will not block legitimate inbound or outbound support mail.A genuine customer request routed to reviewRestore the appropriate operational owner, queue and follow-up after verification.Check deadlines and notifications; a policy change does not undo previous routing.The assessment is inconclusiveKeep the Case assigned to a monitored review process and gather evidence.Record the next action and review time so it is not silently forgotten.Do not open unexpected links or download suspicious attachments to see whether the assessment was correct. Use your organization’s approved security investigation route. Avoid copying potentially sensitive or malicious content into broadly visible notes or public knowledge articles. Allow a verified sender deliberately Verify the exact sender and the legitimate business context through an approved method. Confirm that an ongoing exception is appropriate, rather than merely resolving one unusual message.Open Message Security Review and inspect the current sender and domain policies.Choose Allow sender only when the displayed exact sender is the one you intend to allow. Complete the displayed confirmation or result flow.Reopen or refresh the review and verify the resulting sender policy. If the result is unclear, inspect the current policy before repeating the action.Have an administrator check the full Block/Allow list if a domain or direction-specific rule may still conflict.Return to the current Case and complete any separate routing, ownership or customer-follow-up work. Verify future behavior with an approved, harmless test message when appropriate.Allow sender establishes an allow rule for that exact email address and removes the opposing exact-address all-direction block entry. It does not necessarily remove domain-wide or other direction-specific rules. An applicable allow rule can bypass the new-case security assessment; it is therefore a meaningful policy decision, not a cosmetic way to remove a warning.Allowing does not repair the current CaseThe action does not erase the saved assessment or tags, reverse workflow actions, release an external mail quarantine, or guarantee delivery. Handle the existing Case explicitly and investigate remaining email rules if mail still fails. Block an exact sender with its full effect in mind Confirm the displayed exact email address and the reason for an ongoing block. Check whether it is a shared mailbox used by legitimate customer contacts.Open Message Security Review and choose Block sender when authorized by your operating process.Read the outcome and verify the policy shown after the change. This action creates an all-direction exact-address block, affecting both inbound and outbound email handling.Review any opposing domain or direction-specific rules with the email administrator. The exact sender action does not rewrite the entire rule set.Assign or close out the current Case according to the verified request and your policy. A future sender block does not remove the Case, recall earlier email, or undo already completed activity.Blocking a shared customer mailbox can also prevent your team from sending legitimate responses to that address. Prefer the narrowest supported rule that matches the operational need, and document why it exists. If you need a different direction or domain scope, use the administrative rule configuration rather than assuming this Case action supplies it. Use tags and workflows to create a monitored review process Eligible Hold or Block assessments categorized as Spam or Phishing can apply the lowercase tags spam or phishing, with a subtype where available. Not every nonzero score creates one of these tags. Tags make the Case available to your views and workflow conditions; they are not a built-in spam folder.Create a view for the actual tags used in your account and confirm it finds known examples. Also define how agents report suspicious cases that have no matching tag.Choose a review queue and responsible team, with a backup reviewer and a regular review schedule. This is an operational recommendation, not an automatically provisioned default.In the workflow configuration, define a narrowly scoped rule for the intended creation event and matching tags. Use the supported queue, owner or Division actions only where they fit your access and service model.Test the rule on approved examples: an eligible tagged message, a legitimate untagged request, and a verified false positive. Check the final Division, queue, owner, deadlines and customer notifications.Review rule ordering and other rules that can also match. A later rule can change the routing, and Stop When Hit has the event-pass scope described in the workflow guide.Monitor the review list and resolve false positives promptly. Measure the number of legitimate requests delayed as well as unwanted mail identified.Do not assume routing a Case to another queue or Division removes it from SLA calculations or all reports. Access, service commitments, notifications and reporting eligibility have their own configuration. Validate those effects before changing a live routing policy. Worked example: a new contact at an existing customer A customer’s new procurement contact sends a request from an unfamiliar shared mailbox. The message is flagged and enters your monitored review queue. The reviewer checks the exact sender, reads the available reasons, and confirms the request through the customer’s established account contact. After confirmation, the team routes the Case to the appropriate support owner and checks its service deadline. If future requests from that address are expected, the authorized owner evaluates an exact sender allow rule and checks for conflicting domain rules.The useful result is a documented, verified customer handoff. The team does not assume the message was unsafe solely because of its score, or safe solely because of its Company name. It also does not leave the real request unattended after changing the sender policy. Troubleshoot common assessment and policy questions ProblemLikely explanation and next stepA suspicious email has no shieldFirst select the relevant email activity in the timeline and check beside its message subject. It may be unassessed, bypassed by an allow rule, outside the new-case intake path, missing saved detail, or an escalation draft whose indicator is suppressed. Investigate the message and configuration; absence is not a clean result.The review says Blocked but a Case existsThat is an assessment label. Case creation can continue; inspect actual email exclusions and workflows separately.A legitimate sender is still blocked after Allow senderCheck domain-wide and direction-specific exclusions and upstream mail controls. The exact-address action does not remove every conflicting rule.A reply stopped sending after Block senderThe Case action creates an inbound-and-outbound block for that exact address. Review the intended direction and authorized correction with the email administrator.The old warning remains after allowingSaved assessment details and tags are not retroactively erased by the future sender policy. Verify policy and current Case handling separately.Reasons or confidence are missingThe review may be using limited saved evidence or a fallback representation. Do not invent missing checks; provide the Case ID and observed details to the responsible administrator.Tagged cases are still in normal queuesA tag alone does not route work. Check the configured event, conditions, actions, rule order and other matching workflows.A customer request disappeared from a team’s viewCheck filters, Division visibility, queue assignment and ownership. A security workflow may have changed access or routing.The review list is growingConfirm staffing, review frequency and false-positive resolution. Automation does not eliminate the need for an accountable reviewer. Continue learning Configure account policies and email-security checksManage email block and allow rulesDesign and test workflow routingConfigure workflow events and actionsBuild a monitored case viewConfigure queues and assignmentUnderstand Division configuration and access Was this article helpful? Yes No Thank you for your feedback.