Get a demo

Paid Alumni Job Changer Enrollment

Get notified when a champion joins a target account

Builds a Clay workflow that checks every job-change signal against your CRM, drafts honest, persona-aware outreach, and enrolls qualifying people into the account rep's sequence the same day, then logs it to a CRM campaign.

About this Skill

When to use it

Use this Skill when a champion at a paying customer takes a new job at a company you want to win, and you need same-day outreach routed to the right rep. It builds a Clay workflow that checks each move against your CRM gate by gate, drafts honest persona- and usage-aware copy, and enrolls qualifying people into the right sequence with the enrollment logged to a CRM campaign. Avoid using it for generic title-based congrats emails, detecting or scoring job changes in the first place, creating or cleaning CRM contacts, or reporting on who moved.

What it delivers

You get a live, built Clay workflow plus a dry-run outcome table showing which test records would enroll, skip, or error before anything goes live. Enrollment only happens after every CRM check passes and you approve going live; the workflow never creates CRM contacts or invents a sender.

SKILL.md preview

Sign in to install and view the complete SKILL.md

Illustrative preview. Sign in for the actual file.

How someone would prompt this

Build a workflow that watches for champions leaving our paying customers, checks each move against our Salesforce CRM, drafts honest persona-aware outreach, and enrolls qualifying people into our rep's Gong Engage sequence the same day.

Inputs & outputs

What someone provides before the Skill runs, and the reviewable artifacts it returns.

Inputs

  • 01Product and targeting rules
    • Describe what you sell and what counts as prior product use
    • connect the feed that detects job changes
    • choose audience filters for which old accounts paid, which titles qualify, and which new-account tiers and personas to allow.
  • 02CRM and contact setup
    • Name your CRM and confirm its lookup action is set up
    • list the contact fields someone must fill in before you enroll them
    • identify the account and rep fields that name the sender.
  • 03Routing and sequencer setup
    • Provide your own qualification and routing step that decides who qualifies and which sequence to use
    • name your sequencer and confirm its actions exist
    • define the automatic and manual sequences and their steps.
  • 04Outreach and logging setup
    • Supply your copy generator or copy rules for drafting outreach
    • choose the CRM campaign each sequence logs enrollments against
    • optionally name a task queue to notify the rep.
  • 05Safety and control settings
    • Decide whether to skip accounts already touched by this play, and for how long
    • choose where alerts go when something fails
    • name the off switch and the wait time before checking an enrollment.

Outputs

  • 01Dry-run outcomesA table showing each test record's result, the specific check that stopped it, and the detail behind it, so you can review before going live.
  • 02Sample drafted emailA sample outreach email showing the honest, persona-matched copy style used for a sales-persona lead who was not a direct product user.

Representative output

Dry-run outcomes

RecordOutcomeReasonDetail
Ada Moreno, VP Sales → Northwindwould_enroll—sales persona · product user · automatic sequence · rep active · booking link usable
Ben Okafor, Head of Ops → Contososkippedaccount_suppressedContoso is suppressed in the CRM: "marked do-not-contact"
Cara Lin, CMO → Fabrikamskippedwould_create_contactno CRM contact for this email at Fabrikam; this play never creates contacts
Dev Shah, Director RevOps → Tailspinskippedin_flightalready in an active sequence
Eli Park, CEO → Litwareerrorlookup_errorthe account lookup returned no record set; alert posted, not treated as not found

Five records, one would enroll. The verdicts are would_enroll, skipped and error; enrolled appears only on live runs.

First email, drafted for a regular-subtype sales leader

How the Skill runs

Follow the steps in order. Each row includes the full instruction.

01
Check platform and connections

Confirms your Clay workspace, CLI access, and that a CRM lookup, sequencer actions, and an alert action all exist, stopping immediately if any piece is missing.

Step
02
Interview to define audience

Asks you, one at a time, for audience rules, persona filter, cooldown settings, and copy rules, and maps your CRM fields before building continues.

Step
03
Build the workflow

Asks for your approval to create roughly sixty-five nodes and a webhook trigger in your workspace, then stops and waits for your yes before building anything.

Step
04
Run the qualification checks

Passes each record through a fixed sequence of free checks for sanity, tier, persona, contact match, routing, and cooldown, skipping or alerting on any failure instead of guessing.

Step
05
Dry-run on test records

Runs ten built test records through the workflow with enrollment switched off, shows an outcome table, and stops and waits for you to review it.

Step
06
Draft copy and pick sequence

Generates usage-honest, persona-matched outreach copy, then routes the contact to the automatic or manual sequence based on your routing step's answer.

Step
07
Review cost and approve going live

Shows the dry-run results, the real cost per enrollment, and exactly what will be sent and written, then stops and waits for your yes before publishing.

Step
08
Report results and offer to save answers

Summarizes the workflow id, webhook URL, outcome table, and off switch, then offers to save your setup answers to a private file for future reuse.

Step

Connections required

No connections listed.

Install Clay and run it

Sign in once, install the Skill, then run the prompt.

  1. 1Install ClayUse the connector or official plugin in your coding-agent environment.
  2. 2Sign up or log inAuthorize Clay access and return when the connection is ready.
  3. 3Install the SkillRun the one-line install command from the Add this Skill card.
  4. 4Run the SkillPaste the example prompt and review the result.

Version history

Version 1From submitted SKILL.mdCurrent

Related Skills

Related searches