Articles in this section

Slack and Teams Nudging

Updated

Overview

Nudging messages let you contact targets through Slack or Microsoft Teams before a phishing email is delivered and after the target's phishing result is known. A phishing template can contain a pre-nudge message, a post-nudge message, or both. Post-nudge content can differ depending on whether the target failed the phishing test.

Nudging is available for phishing campaigns that use groups synchronized through the Slack or Microsoft Teams integration. The selected group's integration determines the delivery channel: a Slack-synchronized group receives Slack nudges, and a Teams-synchronized group receives Microsoft Teams nudges.

Use the links below to jump to a section:

Before you begin

  • Connect and activate the Slack or Microsoft Teams integration.
  • Synchronize the Slack workspaces or Microsoft teams that you want to use. The synchronized members become targets in integrated groups.
  • Create or edit the phishing email templates that will be included in the campaign. See Phishing Email Template Editor for general template-editing instructions.
  • Complete the channel-specific read-tracking setup in this article if you want Portal to record nudge read actions.

Note: Nudging messages are configured on phishing email templates. Training email nudging is not part of this workflow.

Back to top

Create a phishing template with nudging

  1. Navigate to Templates > Manage Templates.
  2. Leave Phishing Email Templates selected.
  3. Create a phishing email template, or select Edit beside an existing phishing email template.
  4. In the Phishing Email Details & Settings panel, expand Nudge Settings.
  5. Turn on Send a Pre-Nudge Message, Send a Post-Nudge Message, or both. The corresponding Pre-Nudge and Post-Nudge tabs appear along the top of the Template Editor.

Template Editor showing the Nudge Settings switches and the Pre-Nudge and Post-Nudge tabs

Localization: Nudge messages support the same template-localization workflow as other template content. Configure the default locale first, and then add localized versions as needed.

Back to top

Configure the pre-nudge message

  1. Open the Pre-Nudge tab.
  2. In Nudge Settings > General, set Message Channel to Slack or Teams.
  3. If no message is tied to this stage and channel, select the create-message button shown in the editor.
  4. Compose the message. You can use supported variables, headings, lists, links, formatting, code, and images.
  5. Use Message, Preview, or Split to change how the editor is displayed.

Pre-Nudge Message editor with Slack selected as the message channel

The editor views work as follows:

  • Message: Displays the full message editor.
  • Preview: Displays an approximation of how the message will appear to the target.
  • Split: Displays the editor and preview side by side.

Preview view of a Slack pre-nudge message

Split view showing the message editor and rendered preview

Channel notes: Teams images are delivered through Adaptive Cards. Slack must be able to retrieve an image from the public internet when the message is sent, so use an image URL that Slack can access.

Back to top

Configure the post-nudge messages

  1. Open the Post-Nudge tab.
  2. Set Message Channel to Slack or Teams.
  3. Use Post-Nudge Trigger to choose the outcome you want to edit:
    • Failed Phishing Test: The target failed the phishing test.
    • Did Not Fail Phishing Test: The target did not fail before the applicable post-nudge event.
  4. Create and edit the message for the selected trigger.
  5. Turn on Use the same message for both triggers if both outcomes should receive identical content. Leave it off to maintain a different message for each outcome.

Post-Nudge editor showing the message channel, post-nudge trigger, and same-message switch

Back to top

Configure read tracking

Slack

If you use the PhishingBox Slack app, no additional read-tracking configuration is required.

If you are a reseller using a white-labeled Slack app, Portal uses the Slack app's Signing Secret to verify read events. Find the Signing Secret in Slack app settings > Settings > Basic Information. Then navigate to Administration > Integration Store, select Edit on the Slack card, enter the Signing Secret, and select Test > Save. See Whitelabel Slack App for the full reseller setup.

For the standard Slack integration workflow, see Slack.

Microsoft Teams

A Microsoft Teams administrator must allow read receipts before the PhishingBox or reseller bot can record read actions:

  1. Open the Microsoft Teams admin center.
  2. Navigate to Messaging > Message policies.
  3. Select Global (Org-wide default), or select the policy assigned to the affected users.
  4. Set Read receipts to Turned on for everyone.
  5. Select Save.
  6. Allow time for Microsoft Teams to apply the policy change.

Back to top

Create a phishing campaign with nudging

For complete campaign-creation instructions, see Create Campaign.

  1. Navigate to Tests / Campaigns > Create Campaign.
  2. Create a phishing campaign and select the phishing templates that contain your nudge messages.
  3. Select one or more groups synchronized through Slack or Microsoft Teams.
  4. Open the Schedule step.
  5. Set Nudging to YES.
  6. Set the Pre-Nudge Lead Time and Post-Nudge Delay Time. Each duration can be configured for up to one week.
  7. Review the remaining campaign settings and launch the campaign when ready.

Campaign Schedule step showing Nudging enabled with pre-nudge lead time and post-nudge delay time

The lead and delay values are campaign-wide settings and apply to every configured nudge in the campaign. A template that does not contain a message for a stage can still be used, but Portal skips that missing stage. No nudge is sent unless the campaign's Nudging setting is YES.

Back to top

Understand nudge delivery

  • A pre-nudge is scheduled before the corresponding phishing email by the configured Pre-Nudge Lead Time.
  • If the full lead interval is not available when a phishing message is scheduled, Portal sends the pre-nudge first and delays the phishing email by the configured lead time.
  • A post-nudge is scheduled after the target fails the phishing test or after the campaign reaches the applicable non-failure event. Portal selects the post-nudge content that matches the target's result.
  • The Post-Nudge Delay Time controls how long Portal waits after the triggering event before sending the scheduled post-nudge.
  • The synchronized group's integration determines whether Portal sends the message through Slack or Microsoft Teams.
  • Portal logs a successful nudge delivery as a nudge action. Read actions depend on the channel-specific configuration described above.

Back to top

Monitor and send nudges from Campaign Details

See Campaign Details for general information about the campaign-management page.

  1. Navigate to Tests / Campaigns > Manage Campaigns.
  2. Open the applicable campaign.
  3. In the new Campaign Details experience, open the Nudging tab.

The Nudging table shows each target's nudge stage, message type, delivery status, scheduled time, and triggering event. Use these values to confirm which message Portal plans to send and why.

To send a pending nudge immediately, select Send in that target's Action column. Portal evaluates the target's current campaign context at send time. A target who failed receives the Failed Phishing Test post-nudge; a target who did not fail receives the Did Not Fail Phishing Test post-nudge.

Campaign Details Nudging tab showing Teams pre- and post-nudge message statuses and Send actions

Back to top

Troubleshooting

The Pre-Nudge or Post-Nudge tab is not visible

Expand Nudge Settings in the phishing template and enable the applicable message. The tab appears only when its corresponding nudge setting is enabled.

The Nudging option is not available in the campaign

Confirm that you are creating a phishing campaign and that the campaign contains at least one group synchronized through Slack or Microsoft Teams.

A scheduled nudge was not sent

  • Confirm that the campaign's Nudging setting is YES.
  • Confirm that the selected phishing template has a message configured for the missing stage and delivery channel.
  • Confirm that the integration remains active and that the target belongs to the synchronized group.
  • Review the target's status and schedule in Campaign Details > Nudging.

Nudge read actions are missing

For a white-labeled Slack app, confirm that its current Signing Secret is saved in the Slack integration. For Teams, confirm that read receipts are enabled in the Microsoft Teams message policy assigned to the users. Allow time for Microsoft policy changes to take effect.

Back to top

Back to top

Was this article helpful?
0 out of 0 found this helpful