Consultants in conversations. Not on the CRM.
Match candidates to live roles, re-engage the database, keep applicant communications moving and clean up the CRM in the background — so consultants spend their day doing what pays: talking to candidates and clients.
One desk · Scoped around your ATS/CRM · No sales deck
The CRM is where consultants' billable time goes to die.
Every live role needs a longlist, every candidate interaction needs a note, every applicant needs an update. Consultants know what the right next action is on 200 candidates — they just don't have time to execute it. The database becomes a liability instead of an asset.
Live roles don't surface relevant candidates
Longlists get built from recent memory, not from the database. Consultants know they've placed similar people before, but finding them means searches, filters and scrolling — so they call the easy ones instead.
Dormant candidates stay dormant
Years of candidate data sits in the ATS. Status is stale, contact details drift, availability is unknown. Re-engaging at scale is a project no-one has time to run.
Note-taking and status updates eat billable hours
After every call, the right CRM update doesn't happen — or it happens hours later, imperfectly. The database rots. Reporting is unreliable. Consultants resent it. Managers chase it.
Candidates surfaced. Conversations drafted. CRM kept clean.
Tola handles the surrounding mechanics — matching, chasing, drafting, logging — so consultants spend their time where the margin is. Every outbound communication is drafted, not sent, until a consultant approves.
-
Live roles and candidate data are retrieved from your ATS/CRM
Open roles, job specs, candidate records and recent activity are pulled from your recruitment platform via supported API or webhook.
-
Candidate signals are collected from email, LinkedIn responses and uploads
Applications, replies, CV uploads and update emails are monitored and matched back to candidate records automatically.
-
Candidates are matched against live roles
Candidate experience, skills, location and availability are matched against live job specs, surfacing a shortlist with a reasoning summary — not a mystery score.
-
Dormant candidates and stale records are flagged
Candidates who match a live role but haven't been contacted in months, records with outdated contact details, and inconsistent status entries are surfaced for consultant action.
-
Outreach and applicant updates are drafted for approval
Role-specific outreach, re-engagement messages and applicant status updates are drafted in the consultant's voice and held in a review queue for approval before sending.
-
Interactions and status changes are logged in the ATS/CRM
Approved outcomes — notes, status changes, candidate-role associations — are written back to your recruitment platform through supported integrations.
Fits around your ATS/CRM — not around you.
Tola connects to your email, calendar, document store and recruitment platform. We're explicit during scoping about what integrates via API today and what sits behind file exchange.
If your firm runs on a specific ATS and it's load-bearing, bring it to the scoping call. We'll tell you what's already built, what we can build and what sits in file exchange.
Consultants own the relationship. Tola handles the admin.
Every candidate-facing and client-facing message is drafted but not sent until a consultant approves. Tola accelerates the mechanics around conversations, not the conversations themselves.
What stays with the consultant
Shortlist judgement, candidate representation, client advice and the actual conversations stay with your consultants.
- Shortlist decisions and candidate representation remain with the consultant.
- Candidate-facing and client-facing messages are drafted but held in a review queue until approved.
- Low-confidence matches are routed for consultant review rather than auto-shortlisted.
- CRM write-back is gated on approval rules you define per workflow.
- A full audit log records every match, draft, approval and write-back.
Things recruitment firms usually ask first.
Will Tola message candidates on our behalf without a consultant seeing it?
No. Every candidate-facing message is drafted and held in a review queue. A consultant approves or edits before anything is sent. This is a deliberate design choice — the relationship stays with your consultants, not with the automation.
How does Tola handle candidate data under GDPR?
Documents and candidate data are processed in EU regions, scoped per workflow, with no model training on your data. Retention windows match your firm's existing policy. Candidates' rights (access, deletion) are respected via your existing ATS workflows. See the security page for the full posture.
Does Tola replace a recruitment resourcer?
No. It removes the mechanical parts of resourcing — initial longlist generation, re-engagement sweeps, applicant status updates, CRM hygiene. Resourcers typically shift to higher-value sourcing and candidate care; consultants get back billable hours.
How does pricing work?
Monthly, based on the number of desks or consultants covered by the automated workflow. Fixed scope, fixed price — no per-seat sprawl and no "contact us for pricing" after signing. Commercials are agreed up front and reviewed as scope expands.
Can we see the match view before deciding?
Yes. The discovery call walks through the match view with reasoning, the re-engagement queue, the draft messages and the audit log — on a desk relevant to your firm. Illustrative screens are labelled as such.
Pick one desk. See what comes off the CRM.
Bring one desk and a sample set of live roles. In 30 minutes we'll walk through how it would run on Tola against your ATS, and what would come off your consultants' CRM time and go into billable conversations.