Board or table
Cards while you are moving work along, a sortable table when you are scanning.
WizzHire CRM
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
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.
Boards and stages
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.
Contacts
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.
Client work
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.
Applications, stages and decisions run in the ATS.
Activity
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.
Client reporting
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.
Follow-ups
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.
Two thresholds per board, one for slow and one for too long, and the card changes with them.
A client that has not moved in the days you set gets flagged where the team is already looking.
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
Everything around the board that a team ends up needing in a busy week.
Cards while you are moving work along, a sortable table when you are scanning.
Select several clients and move them to another stage in a single drag.
Take the client directory out as CSV whenever you need it somewhere else.
By name, stage, owner or board, down to your own clients or the ones nobody owns.
A client can be a company or a private individual, and the record asks for what each one needs.
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
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.