Skip to main content
Hyper· revenue engineTalk to usFind my ideal customers
A recruitment consultant's desk, phone in hand, mid a placement call

Campaign management for recruitment desks

Your consultants keep every relationship. Jude keeps everything around it.

A hiring deadline is public for weeks before the shortlists close. Jude finds the employers who have to hire now, names the candidates worth putting forward, and gets the message and the page out at scale.

Below is one hiring decision from the contract win to the reply. Both sides shown, so you can see exactly which parts stay with your desk.

Illustrative example
  1. Hyper's own segment view. A filter for engineering contract wins with adverts live and a start date inside 90 days has settled on 38 businesses found, with Rennick Power Services highlighted in the list.

    Hyper finds the agencies' buyers before the adverts are cold.

  2. The Rennick Power Services record, headed six engineers by 6 October. Three research lines list the contract win, the seven adverts and the 6 October start date, with a shortlist of three named candidates below.

    Hyper has read the adverts and dated the deadline.

  3. An email and its landing page, generated side by side. The email closes on the worded link the three engineers, traced through to a page headed three engineers for your 6 October start. A count reads 38 sent, and the Rennick row is flagged held for Nadia Whyte.

    Every email gets its own page, and every page gets sent.

  4. A Teams chat with Jude. She reports that Rennick Power Services has won the Fife substation contract, and that seven engineer adverts have gone live with a 6 October start date.

    Three named candidates, in the client's own inbox.

  5. Jude's draft, open in Outlook and labelled Drafted by Jude, addressed to Claire Nesbitt with the subject six engineers for the Fife contract.

    The draft is already waiting for Nadia.

  6. The same draft, with a generic line replaced by Nadia's own words: I placed Owen on the Torness upgrade last year, and he can start on two weeks notice.

    Nadia adds the one thing Hyper could not know.

  7. Outlook's inbox. A new reply from Claire Nesbitt has arrived, saying the agency is the first to come back to them and asking whether Owen and Priya can talk to the site lead on Thursday.

    The agency arrived first, in the same week.

  8. The CRM record for Rennick Power Services. The stage has moved to In conversation, a new activity line reads reply sent by Nadia Whyte and logged by Jude, and the next action is to book Thursday interviews for Owen Faulkner and Priya Raval.

    The record keeps itself.

Read the transcript

A contract win, seven adverts, a start date. Every hiring deadline is public weeks before the shortlists close.

Hyper finds the employers who have to hire now, knows the candidates worth naming, and puts them in the client's inbox first.

Your consultants keep every relationship and add what no system knows. The agency that arrives first, in the same week, usually wins.

Jude found the deadline. Nadia decided who to put forward.

ACT 1 / FIND

The deadline was public. Jude found it first.

A contract win and a run of job adverts are both public record, but nobody reads the whole market by hand. Jude does, and turns the pattern into a dated hiring deadline with named candidates against it.

Your desk never writes the first email from a blank page. Jude drafts it, builds the page it points to, and gets both out to every business the pattern matched.

What Jude prepared

The segment, the record and the send

  • 38 businesses matched on contract wins, live adverts and a start date inside 90 days.
  • Rennick Power Services researched: the contract win, the adverts and the 6 October start date, dated.
  • A shortlist of three candidates, one line of relevance each.
  • An email and its own landing page, generated together and sent at scale.

What Nadia's desk decided

The one record held back

  • Every business but one went out automatically.
  • Rennick Power Services stayed with Nadia, flagged for her own review rather than an automatic send.
  • The judgement of which record was worth a person's attention stayed hers.

ACT 2 / DECIDE

The reply that wins is the one that adds a person.

Jude's draft carried everything the public record could show. It could not carry the one detail that comes from actually knowing a candidate, so it did not try to.

Nadia added that detail, sent the email under her own name, and the reply came back inside the week.

What Jude prepared

The draft, waiting in Outlook

  • A drafted reply to Claire Nesbitt, in Nadia's own drafts folder.
  • Three named candidates and the deadline they are being weighed against.
  • The record updated the moment the reply landed: stage moved, activity logged, next action set.

What Nadia decided

The edit and the send

  • Replaced a generic line with the one placement history only she knew: Owen's Torness upgrade and his two-week notice.
  • Sent the email under her own name.
  • Booked the Thursday interviews the reply asked for.

How the work splits

The work Jude takes off your desk.

  • The market reading. Jude watches contract wins, job adverts and start dates across your whole patch, so your consultants hear about a hiring deadline while there's still time to win it.
  • The first email and the page behind it. By the time a consultant looks up, the draft's written, the shortlist's attached, and everything waits on their word before it goes anywhere.
  • The record. Every reply, stage and next step files itself, so consultants spend the afternoon on calls instead of the CRM.

Your consultants bring the placement history and the judgement no record can hold. Jude brings everything else, on time.

The other side of the desk Illustrative example

9,400 dormant records. One that woke up.

Your desk has years of candidates in it already: people you placed once, whose CVs went stale the moment the placement closed. The relationship stayed. It only went quiet.

Watch 80 seconds of one record waking up, from a dormant card to a consultant's own phone call.

  1. Maya Adeyemi's dormant candidate record, placed by this agency in 2022 and last contacted three years ago, pulling back into a wall of grey cards with a counter reading 9,400 dormant records on this desk.

    Years of candidates you already know, asleep in your own system.

  2. A live Senior Backend Engineer role against Maya's own card, with three research lines: her public profile updated three weeks ago, scored against this desk's last year of placements, and a 93% match routed to the right consultant.

    Hyper refreshes the record, scores it against your own placements, and finds the ones worth a call.

  3. A short message and its own landing page, generated side by side. The message is drafted in Cara Malloch's own name; the page reads Hi Maya, three roles with your name on them, with three response buttons beneath it.

    One page instead of twenty-five attachments. One tap instead of a form.

  4. A pixel-exact LinkedIn message thread. Cara's message sits sent, with a read receipt showing under it and no reply yet, which is honest: people rarely answer the first touch.

    From a consultant she knows, where she actually reads messages.

  5. A pixel-exact WhatsApp thread two days later, then Maya's own page open on her phone: she has tapped I'm interested on the 93% role, and the page reads simply, Cara will call you.

    Two channels, one respectful thread. The candidate raises a hand in one tap.

  6. A Teams chat with Jude, the next morning. She reports that Maya Adeyemi tapped yes on the Senior Backend role, that her profile has moved on twice since the CV on file, and that she is expecting Cara's call, not a message.

    Jude has the story ready before Cara picks up the phone.

  7. Maya's refreshed record on screen beside Cara as she dials, with the line Morning Maya, it's Cara, it's been three years, held on screen as she waits.

    A consultant calls a candidate who already said yes.

  8. Maya's record, status moved from dormant to in conversation, a new activity line reading interested via her page and call logged by Jude, with the next action set to send her the Senior Backend Engineer briefing pack.

    The database ends up cleaner than the engine found it.

Read the transcript

Somewhere in your database is a candidate you placed once, who's moved on twice since anyone last called. Years of relationships, asleep.

Hyper wakes them properly: refreshes each record, scores every candidate against your live roles using your own past placements, and shows each person the roles that fit, in your name.

So the replies that come back are warm, scored and worth a consultant's time. Your people pick up the phone to someone who's already said yes to the conversation.

Hyper found the record. Cara made the call.

ACT 1 / WAKE

9,400 records were asleep. One woke up because it was worth calling.

A candidate you placed once hasn't gone away. Hyper reads the whole dormant desk, refreshes each record from the candidate's own public profile, and scores every one against the roles your desk has actually filled before.

One record cleared the bar: three years quiet, a public profile that had moved on twice, and a live role a consultant's own placement history says fits.

What Hyper prepared

The record, refreshed and scored

  • 9,400 dormant records read, each checked against this desk's own placement history rather than a generic score.
  • Maya Adeyemi's profile refreshed from her own public page; the CV on file was three years stale.
  • A 93% match against a live Senior Backend Engineer role, routed to Cara Malloch, the consultant who placed her.
  • A short message and Maya's own page generated together, in Cara's name.

What stayed with the desk

Whose name it went out under

  • The message drafted in Cara's own name: hers is the relationship, so hers is the name on it.
  • Which candidate was worth reaching stayed a scored suggestion, not an automatic send: Cara's desk decides who gets a message.
  • The three roles on the page, and their fit, came from the desk's own history, not a guess.

ACT 2 / REACH

One tap raised a hand. A person made the call.

The same message reached Maya twice, honestly, from a name she already knows: a LinkedIn DM first, read but not answered, then a shorter WhatsApp nudge two days later. No new channel, no disguised sender, just the ordinary patience a real follow-up takes.

She opened her own page, saw three roles with her name on them, and tapped once. No form, no CV upload. Jude had the whole story ready in Teams before Cara picked up the phone.

What Hyper prepared

The tap, and the brief before the call

  • The same worded link, sent from the same name, across LinkedIn and then WhatsApp two days later.
  • Her page recorded the tap the moment it happened: interested, on the 93% role, no form.
  • A Teams brief waiting for Cara: what Maya tapped, what had changed since her CV, and that she is expecting a call, not another message.

What Cara decided

The call, and what happens to the record

  • Cara made the call herself, from the record Hyper had already refreshed and scored.
  • Everything the call decides, judgement about fit, timing, the next step, stays hers.
  • The record updated itself the moment the call was logged: status moved, activity recorded, next action set, with nobody typing a thing.

Prepare your next hiring conversation

See what Hyper would build for an employer you would like to work with.

Find my ideal employers