Skip to content
Hypamoon

For teams that run on RecruitNow

RecruitNow open matches on closed job requests

In Cockpit a match stays open until someone gives it a final status, also when the job request behind it has closed. RecruitNow asks recruiters to set each finished match to placed or rejected to keep the pipeline clean, and its dashboard counts the ones left behind as expired matches.

How it goes today

  1. Filter the matches in Cockpit per job request.
  2. Check for each job request whether it is still active.
  3. Open each match that is still running and choose a final status.
  4. Check afterwards that the candidate status still fits.

How it can go

Open matches on closed job requests, found every week and closed after your check.

Every Monday each recruiter gets a list of their matches that are still open while the job request has closed, been filled or been withdrawn, grouped by job request. You pick once which final status such a match gets. The matches you approve get that status in Cockpit with a short reason on the record, and the others stay as they are.

Say this in ChatGPT, Claude or Copilot

Your chat gets connected to Hypamoon first, with this request filled in. RecruitNow first switches on access for your company when you ask them, which can take a few business days. After that you get the key, or create it yourself, and paste it in the portal, never in the chat.

Your request

With Hypamoon, every Monday, find the matches in RecruitNow Cockpit that are still open while their job request is closed, filled or withdrawn. Send each recruiter the list of their own matches, grouped by job request. When I approve, give those matches the final status I picked and note the reason on each one. Leave the others as they are.

RecruitNow creates an API key for your company and your Cockpit environment when you ask your implementation manager or support, and tells you the address of your environment. The key stays valid until RecruitNow revokes it. It stays yours.