← all playbooks

Know when someone you placed has left, before the client calls you

Your past placements checked against where each person works today: who has left, where they went, when they left where the work history shows it, which departures fall inside the guarantee period you supplied, and a drafted note to each client contact. Staged, not sent.

use when
you have placed people over the years and would not know if one of them walked out of a client last month
starts from
Your database

The prompt

Paste it into Claude Code or the Claude desktop app with Hyreflow connected. The first line tells your agent to use Hyreflow, so it reads the play, asks before it spends anything, and hands the work back to you.

paste this into Claude
Use hyreflow and check which of the people I placed have since left the
client I placed them with.

My placements: <CRM_OR_PATH_TO_EXPORT>. Take everyone placed in the last
<YEARS> years in <DISCIPLINE>. Leave out anyone marked do not contact.

- For each person, tell me whether they are still at the client. If not,
  where they went, their title there, and when they left if you can date
  it. If you cannot check someone, say so. Do not count them as still there.
- My guarantee period is <GUARANTEE_PERIOD> from the start date. List
  anyone who left inside it separately, at the top.
- For each departure, find the client contact who took the placement and
  their work email. This is a client conversation, so work email only.
- Draft a short note from me to that contact: I know the seat is open and
  I can help fill it. For the guarantee cases, I am raising it first.
  Do not write to the person who left.

Check five placements first and tell me what the full run costs before you
do the rest. Stage the notes, do not send anything.

Replace every <PLACEHOLDER> with your own detail. Everything else can stay as written.

What you need first

  • Your placements, from a connected CRM that keeps a placements list or from an export: the person, their LinkedIn URL, the client and the start date
  • The guarantee period you agreed with each client, which the agent does not know and will not assume
  • A Hyreflow workspace with credits
  • A connected sequencer, if you want the notes staged in a campaign and not handed back as a table

Tools it can reach for

The agent picks per step from what your workspace has. Nothing here is required by name.

What happens when you run it

Free steps are marked free. Anything that spends credits is marked, and the agent asks before the first paid run of any size.

  1. 1

    Pull your placements

    free

    Placements are read from your CRM where it keeps a placements list, or from an export: the person, their LinkedIn URL, the client and the start date. Reading your own records is free.

  2. 2

    Fill in the missing LinkedIn URLs

    credits

    The check needs a profile URL for each person. Where your record has none, a web search on the name plus the client company finds it, and an ambiguous hit is left blank, not guessed.

  3. 3

    Check each person against the client

    credits

    Each profile is checked against the employer you expect, which is the client you placed them with. The answer is still there or moved on, with the current company and title for anyone who moved.

  4. 4

    Date the departures

    credits

    The check says that someone moved, not when. For the leavers only, the dated work history is pulled from the profile, which shows when the client role ended and the next one began.

  5. 5

    Flag the guarantee cases

    free

    Each departure date is set against the start date on your record and the period you supplied. It is arithmetic on your own terms, so it is free. A departure with no date is flagged as undated, not cleared.

  6. 6

    Find the client contact and their work email

    credits

    The hiring manager on the placement comes from your own records. Where the work address is missing, the enrichment waterfall runs in a set order and stops at the first hit, and the address is deliverability-checked.

  7. 7

    Draft the note to the client

    credits

    One short note per departure, from you to the person who took the placement. It is about the open seat and what you know of the brief. The guarantee cases are written so that you raise the subject first.

  8. 8

    Stage, do not send

    free

    Approved notes are loaded into a paused campaign in your sequencer, each contact carrying their own text, or handed back as a table. Starting a send is a separate action that you take.

What a run costs

Credits are spent per record the play actually works, and a lookup that finds nothing usually costs nothing. The two figures are the run where the first provider answers and the run where every lookup walks its full chain.

recordsif the first provider answersif every lookup walks the chain
25$6.363 credits$16160 credits
100$25250 credits$65650 credits
500$1251250 credits$3253250 credits
1,000$2502500 credits$6506500 credits

Free before anything is charged

  • Pull your placements
  • Flag the guarantee cases
  • Stage, do not send

What moves the number

  • The channel. This play buys work email, because these are people you are approaching about work you want to win. A work address is the cheaper of the two to find.
  • Coverage on work history and work email. The chain stops at the first provider that answers, and only that provider bills.
  • How many records survive the free filters. Everything dropped before the paid steps costs nothing.
  • The scoring and drafting steps run on the metered agent, charged on what they read and write rather than per record, so they sit outside this table.
  • Providers you connect with your own key. Those calls bill your account, not your credits.

An estimate, not a quote, priced at the volume credit rate. Your agent sizes the run against your own workspace and tells you what it will cost before it spends anything.

A placement that leaves is a client event

When someone you placed walks out, three things are true at once. The client has an empty seat they did not plan for. You are the recruiter who filled it last time, so you know the brief, the manager and what the job is really like. And if it happened early, a guarantee conversation is coming whether you start it or not.

Most agencies find out late. The client mentions it in an awkward email, or a profile update turns up months afterwards. By then the backfill has gone to whoever rang first, and the guarantee conversation began on the client's terms.

The check is narrow, which is why it works across a whole placement history. You already hold the two facts it needs: who the person is and where they should be working. It asks one question per placement, and only the leavers need a second lookup.

What you get back

A table of your placements: person, client, start date, and whether they are still there. For the leavers, the company they joined, their title, and a departure date where the work history shows one. Departures inside the period you supplied sit at the top. Beside each departure is the client contact, a verified work email and a drafted note, staged and unsent. Placements that could not be checked are listed as not checked, never as still in the seat.

Variations worth knowing

The guarantee watch. Run only the placements still inside their period, and run it often. It is a short list, and it is the one where finding out first matters most.

The candidate side. The person who left is still someone you placed. Reconnecting with them is a different message on a different channel: get back in touch with candidates who were promoted or changed job.

When the contact has gone too. If the manager who took the placement has also moved, the note has no reader. Follow your client contacts when they move company finds them.

Where this goes wrong

A profile nobody updated. The check reads what the person has published. Recent leavers often have not touched their profile yet.

The employer name does not match. You placed them at a subsidiary and the profile names the parent, or a trading name. The check compares against the employer you give it, and a mismatch can come back as never having worked there. Give the client's website domain where you have it, and read those rows by eye.

Internal moves look like nothing. The check reports a change of employer only. Someone promoted out of the role still shows as employed at the client, though the seat you filled may be open.

Sounding like surveillance. A note from the recruiter who made the placement is normal. A list of what you found out about the person who left is not. Keep it to the seat.

Questions

How does it know someone has left?

Each person's professional profile is checked against one employer, the client you placed them with. The answer is that they are still there, or that they have moved, with the company and title they hold today. It is a check on a public profile, so someone who left last week and has not updated theirs still reads as employed. No departure found is not proof that nobody left.

Does it know what my guarantee terms are?

No, and it does not guess. You give the period, and the agent compares the start date on your record with the departure date it could find. Whether a departure triggers a replacement, a rebate or nothing at all is in the terms you signed with that client. Read them before the note goes out.

Why would I tell a client that my own placement has left?

Because they already know. The only open question is whether they hear from you or have to chase you. A recruiter who raises it first, with a plan for the seat, looks like a supplier who is paying attention. One who waits for the email about the guarantee looks like the opposite.

Will it contact the person who left?

No. This play writes to the client, by work email. The person who left is a candidate, and candidates are approached by personal email and LinkedIn, never through a work inbox at the company they have just joined. That conversation is a different play with a different message.

Can I run this every month?

Yes, once you have run it by hand and trust the output. It converts into a scheduled workflow that re-checks the placements list and leaves the leavers and the drafts waiting in your workspace. It never sends. Prove it by hand first, because each check is charged per person, and a loose list spends credits on placements so old that nobody would act on the answer.