100+ field-tested entries
Every entry used on a live recruitment call before it lands in the catalogue. Nothing theoretical.
Feature
Every answer has been used on a live call. Open questions, objection handling, scripts. Searchable by situation, organised by framework.
In the app
Knowledge base
Most recruitment 'knowledge bases' are unstructured wikis that decay the moment the consultant who wrote them leaves. The IPMERC knowledge base is different: every entry is an answer that worked on a real call before it entered the catalogue, and every entry is tied to a phase in a framework consultants already use.
The knowledge base sits inside the same platform as the training, so a consultant can search by situation without switching apps. 'Candidate says salary is the most important thing' returns the canonical reply and follow-up questions. 'Prospect says they already work with another agency' returns the WRIOC response and how to test whether the relationship is closed or just default.
Entries are versioned, owned, and reviewed. No conflicting copies scattered across slide decks. New consultants reach senior-level technique faster because the playbook is explicit, not tribal.
Every entry used on a live recruitment call before it lands in the catalogue. Nothing theoretical.
Each entry maps to a phase in IPMERC, WRIOC, or FAB. Search by 'probe', by 'objection', by 'close'.
Type 'kandidaat wil tegenaanbod accepteren' and get the canonical reply, not a list of 40 vaguely related articles.
Same situation, three audiences (prospect, client, candidate). Each gets its own variation of the answer.
Entries live inside the program structure so consultants learn them in sequence, not at random.
One canonical answer per question. Updates propagate. No outdated PDFs in shared drives.
Through the API or a plugin, your own CRM can surface the right knowledge entry next to each pipeline stage. No switching apps mid-call.