Back to documentation

Recruiter Workflow

This is the end-to-end workflow for a recruiting agency using Lynx with a client: create a role, invite the client, submit candidates, collect feedback, and keep everything organized in one place.

How Lynx organizes work

  • Workspace: your company account (members, settings)
  • Client: a company you recruit for (managed in Clients)
  • Job Role: a search you’re running (pipeline, chat, team, candidates)
  • Candidate: a submission in a role (resume, summary, notes, feedback, stage)

Step 0: Set up your workspace members

Before you start a role, make sure your internal recruiting team members are in the workspace.

  • Go to Settings → Allowed Users
  • Invite teammates by email and assign roles (Owner/Admin/User)

Step 1: Add the client

Create the client company record so it’s easy to attach clients to roles and keep your book organized.

  • Go to Clients
  • Add the client name and a short description

Step 2: Create a job role

Roles are where recruiter ↔ client collaboration happens. A role includes a pipeline (stages), a general chat, and a roster of team members (recruiters + clients).

  • Go to Job Roles
  • Click Add Job Role
  • Fill in the role details (title, client, location, compensation, link/description)

Upload a job description and extract info (optional)

In role settings, you can upload a job description file. Lynx can extract structured fields from that file and populate the role details.

  • Open the role → Settings
  • Upload the job description file
  • Click Extract to overwrite fields with extracted data

Step 3: Invite the role team (recruiters + clients)

Role membership is configured per role so you can keep access scoped to the right search.

  • Open the role → Settings → Hiring Team
  • Under Recruiting Team Members, invite internal recruiters by email
  • Under Client Team Members, invite client stakeholders by email
  • Click Save to persist changes

Step 4: Add candidates

Candidates are added inside a role. You can upload a resume file, or paste resume content, then fill in the candidate details. Lynx will store the resume and can format the resume text for readability.

  • Open the role
  • Click Add Candidate
  • Enter the candidate’s basic info and add their resume

Use AI to accelerate candidate preparation (optional)

  • Resume extraction: extract structured fields (like name/contact) from resume content
  • Resume formatting: generate a clean, readable resume text view
  • Summary: generate an AI-powered candidate summary from the job description + resume + notes
  • Recruiter Notes: generate internal-only notes (recruiter-visible only)

Step 5: Collaborate before submission

Use Lynx chat to keep context connected to the role and the candidate:

  • General Chat inside the role for search-level discussion
  • Candidate Chat for candidate-specific discussion and feedback

Step 6: Submit candidates to the client

Candidates typically start in Pending Submission. When you’re ready to submit, move the candidate to Submitted by using Move Forward.

  • Open the candidate profile
  • In the decision/actions area, choose Move Forward
  • Customize the notification message and select who should be notified
  • Confirm to move the candidate stage and send the notification

Reminders and follow-up

If a stage sits inactive beyond the role's follow-up reminder threshold, Lynx flags the candidate as needing attention. Recruiters can resend the most recent notification from the candidate profile to prompt a decision.

Step 7: Track decisions and stage changes

As the client reviews, the candidate can move through stages such as Submitted, multiple Interview stages, Offer, and Hired. You can also:

  • Reject a candidate
  • Put a candidate On Hold, then resume later
  • Move to a Previous Stage when the process needs to step back

Each stage transition supports an optional notification message and recipient selection.

Step 8: Close out the role

When the role is complete, keep the full decision trail in Lynx: submissions, feedback, stage history, and chat context. This becomes the durable record of what happened and why.

Related guides