Client Hunter can connect a confirmed result to the next action

One explicit link keeps research and candidate scoring honest

A completed Client Hunter result marked Confirmed can now be linked to an existing active CRM job for the same organization and company. The recruiter must confirm that the selected CRM job represents the public source role before any candidate score is shown.

The green shortlist contains only current, active candidates scoring 80% or higher for that selected CRM job. RecruitIQ shows the scorer and evidence versions plus the score time, pauses the action while scoring is refreshing or its provenance is not current, and checks again immediately before any delivery.

Outreach starts as a reviewable draft

RecruitIQ prepares a concise draft for a contact whose email and public source were captured in the investigation. The recruiter can edit and save the subject and message before anything is sent.

At send time, RecruitIQ checks that the public source still contains the exact email address. A Confirmed company result alone is not treated as proof that every contact field is safe to use.

The generic contact source on existing investigations is content-supported today because the guarded email path re-fetches it and requires the exact email token. Field-specific email and phone source URLs make each claim easier to review when a result supplies them; retaining the direct verification URL and a content hash with each audit would make that proof more durable over time.

Contact cards keep identity and role evidence separate from email and phone evidence when those links are available. A phone is called a Direct line only when the result explicitly says it is direct; a company switchboard is labeled Company main line, and an older untyped phone remains a Publicly listed number.

An unfinished job URL stays with this tab

When you start a new Client Hunter investigation and type or clear a job URL, RecruitIQ keeps that exact unsubmitted draft while you navigate elsewhere in the same browser tab. Returning to Client Hunter restores the Start New form instead of replacing it with the most recent investigation.

The draft is local to the current browser-tab session and is scoped to the exact signed-in user and organization. It is not synced to another tab, device, user, or organization, and it expires after 12 hours. An explicit run link always opens that saved investigation instead of being replaced by a local draft.

You can review an earlier investigation without deleting the unsubmitted URL. Choose Start New to return to it. Once Client Hunter successfully saves the new investigation, the local draft record is removed as one unit.

If you stage a different normalized URL while an earlier investigation is open, RecruitIQ hides that earlier result and every CRM or outreach action. The page shows the staged URL beside the previous investigation source and lets you restore the previous URL; only then does the saved result become current again.

Company identity links use verified official websites only

In the local product-review build, Client Hunter shows a company logo or company link only when the current chosen client has an official company-website source and the saved material-evidence audit marks that source as supported. This behavior is not live or deployed.

A contact email domain is not company-identity evidence. Domains from an ATS, job board, generic aggregator, directory, or social profile do not qualify either. If the current investigation has no supported official website, the company name remains neutral and non-clickable instead of guessing a destination.

The verified website is bound to the current signed-in user, investigation, company name, and normalized domain. Opening an older result for the same company cannot supply the current result’s logo or link.

The same posting keeps its investigation history

When the exact same normalized job URL has an earlier terminal investigation, RecruitIQ compares the named client, confirmation level, confidence, and research context before preparing or sending outreach. Different named client identities pause outbound action instead of letting the newest result silently replace the earlier conclusion.

A different-identity conflict does not declare either investigation correct. Recruiters can open the earlier evidence directly, and an organization owner or administrator must explicitly choose the current investigation identity before work continues. That acknowledgment is bound to the exact selected identity, normalized identity, ordered prior-run IDs, and the fingerprint of the reviewed history, so a newer or changed blocking conclusion requires another review.

When both investigations name the same normalized client, any confirmation-band change or confidence change of 10 percentage points or more appears as a non-blocking stability notice. It shows prior and current calibration without suggesting the current result is wrong or requiring the blocking identity acknowledgment.

• Any confirmation-band change or a confidence change of 10 percentage points or more is shown as a warning when the normalized identity is the same.
• Prompt, model, schema, and evidence-set changes provide context but do not choose a winner or create a conflict by themselves.
• The check inspects at most 12 earlier terminal results, uses a 13th record only as a lookahead, and pauses outbound action if the bounded history is incomplete or unavailable.

Automatic sending is closed by default

The guarded beta send path requires three separate approvals: a global service kill switch, a versioned organization opt-in saved by an owner, and an explicit confirmation bound to the exact saved draft and that opt-in version. Editing the draft or changing the opt-in resets confirmation. The message is sent through the acting recruiter’s connected Gmail account.

Only the explicitly designated production deployment may address the public contact. Before confirmation, RecruitIQ says whether that contact will receive the message or shows the exact dedicated allowlisted test sink used by preview, staging, and local environments. Each investigation has one initial-outreach identity and every replay reports its stored state without creating a duplicate. A suppressed address is saved as a locked result without contacting Gmail, while an ambiguous provider result is marked for human reconciliation and is not retried automatically.

• Probable, Strong lead, and Unknown results cannot use these actions.
• The selected job and company must be active, organization-owned records that match the Confirmed hidden client.
• Sent and ambiguous history remains readable if the linked job or company later closes, but new mutations remain blocked.
• A suppressed initial action is saved and locked; a different sourced contact requires a new reviewed action, and preparing again cannot overwrite a claimed or terminal action.
• This guarded beta action does not yet replace the planned client-pursuit, response, job-order, and placement chain.