Why recruiters hate their CRM
Consultants do not dislike software in general. They dislike a system that takes time out of their day and gives it to somebody else's report. Here is where that feeling actually comes from, and which parts of it a change of vendor would fix.
Ask AI about this
Every agency owner has had the conversation. Someone says the CRM is rubbish, you ask what specifically, and you get four complaints that do not obviously belong together: it is slow, it never finds anyone, it takes twenty minutes to log a morning of calls, and the last update moved a button. It sounds like grumbling, so it usually gets answered with more training.
Underneath those four complaints there is one cause, and it is structural rather than emotional. The system was designed around the record, and the recruiter's day is not made of records. Once you can see that, the complaints stop being a morale problem and become a list of things to test on your next vendor.
Why do recruiters hate their CRM?
Because most of the work the system asks of them is work that benefits somebody else. A consultant makes a call, and the call is the valuable thing. Then the system asks for an outcome, a note, a next action, a stage change and a follow-up date, none of which help them place that person, and all of which help the weekly report.
That trade is worth making when the system gives something back. It gives nothing back when the information it collects is never returned in a useful shape, and consultants notice that fast. If the notes they wrote last quarter are not what surfaces the next time that candidate is relevant, they learn that writing notes is a tax and they start paying the minimum.
Why does logging a day of activity take so long?
Because the information is spread across tools that do not tell each other anything, so the consultant becomes the connection between them. The call happened in a phone system, the email is in a mail client, the interview is in a calendar, the CV arrived as an attachment and the contract was signed somewhere else entirely. The CRM knows about none of it until a person retypes it.
Vendors answer this with integrations, and integrations are better than nothing. They are also a promise between two companies that will agree about a mobile number until one of them changes something, after which they will disagree quietly. That is how a candidate ends up with a correct number in the phone system and an old one on the record, and it is why consultants check both.
The practical test on a demo is not to watch the integration screen. Ask them to place a call to your own mobile from inside the system, then show you the call, its recording, the note and the next action on the candidate's record without anybody typing. Then ask the same for a signed document and an interview booking.
Why does CRM search never find the candidate you know you have?
Because most CRM search matches the text somebody happened to type, not the person. A consultant searches for a skill, gets eleven results, knows for certain the database holds forty people who can do it, and concludes the system is broken. The system is doing what it was built to do, which is find the word.
The consequence is expensive and almost never measured. Every time search fails, someone goes back to a job board or a sourcing tool and pays to find a candidate the agency already owns, already has a relationship with, and has already paid for once. Owners see the sourcing bill and the consultant's hours, and rarely connect either to a search box.
To measure it in your own agency, pick three skills your team places regularly. Have a consultant search the CRM for each, then search their own memory, then check the number you would have said. The distance between those numbers is the size of the problem, and it will tell you more than any feature comparison.
Why does everyone blame training when the system is unpopular
Because training is the only explanation that does not require anybody to have made an expensive mistake. When adoption is poor, the comfortable conclusion is that people need another session, and sometimes that is true. When the same complaints survive three rounds of training, the system is the problem and the sessions are a way of not saying so.
There is a fair test for this. Sit with your best consultant, the one who is not resistant to anything and hits their number every quarter, and watch them work for an hour without helping. Count the times they retype something the system already knew, open a second tool for something the CRM should have done, or abandon a screen and do it a different way. Whatever you count, that is what the whole floor is doing, minus the goodwill.
What recruiters actually complain about, and what causes it
| The complaint | What is actually happening | What to ask a vendor |
|---|---|---|
| It takes forever to log my day | The system is not connected to where the work happens | Show me a call logged end to end, timed |
| Search never finds anyone | Text matching rather than finding people | Search my own data for a skill during the trial |
| It is slow | Often true, and often really a count of clicks | Count the clicks to add a candidate to a shortlist |
| It is useless on my phone | A cut-down view rather than a real app | Log a call and send a CV from a phone, on the demo |
| I have to retype everything | Forms that do not carry details across | Add a contact as a candidate and watch what transfers |
| The AI writes nonsense on records | Software that is never allowed to be unsure | Hand it a genuinely ambiguous case and watch |
What an owner can do about it without changing system
Start by cutting the fields nobody reads. Most agencies collect a set of mandatory entries that were added years ago for a report that no longer runs, and each one is charged to every consultant on every record forever. Go through the required fields with the person who produces your numbers and remove anything that has not been looked at in six months.
Then find out what your team keeps outside the system and why, one consultant at a time. Those spreadsheets are a precise list of what the software fails to do, written by the people who know. Some of them are a configuration problem you can fix in an afternoon. Some of them are a vendor problem, and knowing which is which is the whole of the decision about whether to move.
The thing I would most want an owner to take from this is that the complaint is usually accurate and usually badly worded. Consultants say the CRM is rubbish because they are busy, not because they cannot tell you what is wrong. Ask the narrow version of the question, about one task and one hour, and you will get a list specific enough to act on, whether that means fixing your configuration, going back to your vendor, or starting to look.
Anshika leads Customer Success at Recruitly.
