WizzHire

WizzHire CRM

Inside WizzHire CRM, in detail.

One full section per capability, for the work that happens before a position is even open: the clients you work for, where each one stands, and what the conversation turns into. The hiring itself lives on the WizzHire ATS page.

Client records

One record per client, not a row in a spreadsheet.

Everyone you do work for gets a record: who they are, who owns the relationship, and everything the team has said about them so far.

  • Industry, website, notes and an owner from your team, on every record.
  • A client is an organization or a private person, and the record asks for what fits.
  • The client list stands on its own, so a record is never trapped on one board.

Boards and stages

The stages are yours, on as many boards as you need.

Build the stages the work really goes through, name them, give each one a color, and say which ones mean won and which mean lost. Move a card across when something changes, or a dozen of them in one drag.

  • Rename, recolor and reorder stages, and remove one by moving its clients somewhere else first.
  • Work the board as cards, or switch to a table and sort by stage, owner or last activity.
  • More than one board, so two kinds of work never have to share a pipeline.

Contacts

The people behind the client.

Clients are organizations; the work happens with people. Keep as many contacts as the relationship needs, with one marked primary so everyone knows who to call first.

  • Name, role, email and phone on every contact.
  • Exactly one primary contact, and promoting a different one is a click.
  • An email address belongs to one contact, so two cards never quietly hold the same person.

Client work

The conversation turns into an open position.

Link a position to the client it belongs to, or open a new one straight from the client's record. From there the applications, the stages and the decisions run in the ATS, and the client record knows about every one of them.

  • Link positions you already have, or create one from the client record.
  • Add a candidate onto the client's position yourself, with a CV and your own notes.
  • Unlink a position without touching the applications behind it.

Activity

Every move on the record, and who made it.

The client's timeline holds what happened and in what order: stage moves, notes, owner changes, contacts, positions and exports. Each entry says whether it was a person, the system, or an assistant working over MCP.

  • Notes from the team sit in the same timeline as the changes.
  • A stage move carries where the client came from and where it went.
  • An export is an entry too, so you know when numbers left the system.

Client reporting

What the work on one client actually produced.

One report per client, built from the positions linked to it: how many candidates came in, how many are still in play, how many were hired, and where the funnel narrows.

  • Candidates, active in pipeline, hired, interviews completed, offers extended and accepted.
  • One funnel across every linked position, and a breakdown per position.
  • Filter by position and by period, then take it away as CSV or PDF.

Follow-ups

The board says what has gone quiet.

Set the rules per board: how many days of silence counts as slow, how long a client may sit in one stage, and how long a record may go without an owner. Cards flag themselves, and the board filters down to just those.

  • Nothing heard for a while

    Two thresholds per board, one for slow and one for too long, and the card changes with them.

  • Stuck in one stage

    A client that has not moved in the days you set gets flagged where the team is already looking.

  • Nobody's client

    A record left without an owner past your limit stops being everyone's problem and becomes visible.

Every rule is off until you turn it on, and each one carries its own day count.

Also included

The rest of it, in one list.

Everything around the board that a team ends up needing in a busy week.

Board or table

Cards while you are moving work along, a sortable table when you are scanning.

Move many at once

Select several clients and move them to another stage in a single drag.

Export the list

Take the client directory out as CSV whenever you need it somewhere else.

Search and filters

By name, stage, owner or board, down to your own clients or the ones nobody owns.

Organizations and people

A client can be a company or a private individual, and the record asks for what each one needs.

Your own assistant

Connect Claude or ChatGPT over MCP and ask it to move a client, add a note, or pull a client report.

In pricing this is the Clients module, switched on next to Hire and People.

After the agreement

Where the hiring happens: WizzHire ATS.

A client record is where the work gets agreed. The position it turns into runs on the other half of the system, and what happens there comes back to the client's report.

  • Every application on one board, in your stages
  • WizzAI scores every CV; your team decides
  • Questionnaires, interviews, and offers on one profile
See WizzHire ATS in detail