DEX / Automations

DEX Automations

Stop manually chasing completions and forwarding low scores, let WorkVerge notify managers, send reminders, and trigger follow-ups when survey events happen.

Real-world scenario

Priya Mehta · People Ops Lead at Bluewave Labs

During Q2 engagement, Priya automates three things: remind non-respondents at 50% window elapsed, alert her when Engineering completion drops below 55%, and ping a hiring manager when a week-1 pulse scores ≤ 3 on manager support.

Before you begin

  • DEX admin access
  • Background workers running in your environment

Overview

DEX automations react to survey and lifecycle events without Priya living in Slack. When someone submits a week-1 pulse with a low tooling score, WorkVerge can notify IT. When Q2 engagement stalls mid-campaign, non-respondents get a nudge automatically.

Priya's Q2 automation set

Trigger: Deployment response rate < 55% · Folder: Engineering → Action: Email Priya + Engineering VP
Trigger: Week-1 pulse submitted · Score ≤ 3 on manager support → Action: Notify hiring manager
Trigger: Exit interview submitted → Action: Notify People Ops + add to monthly themes review

Create an automation

  1. 1

    Open DEX → Automations

    Browse existing rules or create one for your next campaign or lifecycle event.

  2. 2

    Choose a trigger

    Survey submitted, deployment started, onboarding status changed, low response rate, etc.

  3. 3

    Define conditions

    Optional filters, e.g. only when NPS ≤ 6, or only for Engineering folder deployments.

  4. 4

    Add actions

    Send email, in-app notification, notify manager, start a follow-up deployment, or hand off to org workflows.

  5. 5

    Activate and test

    Run a test response or small pilot deployment before company-wide Q2 launch.

Common triggers

  • Survey response submitted. Branch on scores or question IDs
  • Deployment started or ended. Kick off reminders or leadership summaries
  • Onboarding or offboarding status changed. Schedule exit interviews or week-1 pulses
  • Low response rate threshold. Mid-campaign rescue for quarterly engagement

Workers must be running

Automations queue as background jobs. If workers aren't active, rules save but nothing executes, confirm your deployment runs workers.

Cross-product workflows

DEX-only rules live here. When Priya needs ITSM tickets created from survey answers or ITAM tasks on offboarding, use cross-product Automation Workflows under My Organization.

Related articles