DM protection watches the direct messages arriving at your connected accounts and flags the dangerous ones - phishing lures, scam offers, spam blasts, and abuse - so a risky message is caught before anyone on your team acts on it.

The most important thing to understand: DM protection flags, it does not act. Spikerz will not delete a message, block a sender, or reply on your behalf. It raises an alert, and you decide what to do - handling the message in the platform's own inbox, then marking the alert resolved in Spikerz. Nothing happens to your conversations without you.

The feature is organized into two tabs:

Make sure that:

Open the Settings tab. Under Predefined triggers you will find the four categories Spikerz can scan your direct messages for. Each one has its own dropdown with two states: Active scan or Off.

Note: a category set to Off is not scanned, so messages of that kind arrive with no alert at all. Because DM protection only ever flags, leaving a category on Active scan costs you nothing but an alert to review - there is no risk of a legitimate message being deleted or a real customer being blocked.

Recommendation: keep all four categories on Active scan. Phishing is the one to never switch off - it is the category that leads to a stolen account.

Open the Alerts tab. This is your working queue of flagged messages.

The row of counters across the top splits the queue by state:

Use Search to find a specific sender or phrase, Filter to narrow the queue, and Display to change how the list is laid out.

Each card carries everything you need to make a judgment call without leaving Spikerz:

You can also Add tag, Add assignee, and Add sentiment to an alert. Assignees are what turn the queue into a shared workflow instead of one person's job - assign the alert to whoever owns that account or that market.

This is the part that is easy to miss. Spikerz flags the message; closing it out is yours to do, in two separate places.

Working through a backlog: use the checkbox on each card, or Select all at the top of the list, to resolve several alerts in one pass. This is the fast way to clear a pile of low-risk spam without opening each one.

Needs review is a queue, not a log. Because Spikerz never acts on a message by itself, an unresolved alert means nobody has decided anything yet. Let the count run away and the one phishing attempt that mattered ends up buried under a hundred spam messages nobody bothered to close.

Treat Needs review the way you would treat an inbox: work it down to zero, and the number becomes a signal you can trust.

Direct message scanning depends on the platform exposing messages through its API. Today that means Facebook and Instagram.

For the full feature matrix across every Spikerz protection, see the Spikerz Platform Security Features & Availability Guide.

Reclassify the message using the category badge on the card, and use Feedback to tell Spikerz the call was wrong. If one category is consistently noisy for your account, you can set it to Off - but remember that switching off Phishing or Scam removes your warning on the two categories that cause real damage.

Alerts stay in Needs review until someone resolves them - it does not clear on its own, and reading an alert is not the same as resolving it. Use the check icon on each card, or Select all to resolve a batch at once.

That is by design. DM protection is a detection layer - it never touches your conversations. Select Manage DMs in inbox on the alert to open the conversation on the platform, take the action there, then come back and resolve the alert.