The whole point
Notes are worthless in another app
Every notetaker produces a document. The document is not the job — filing it is. Recruitly writes the meeting onto the client, the candidate and the job as a note on the calendar event that was already there, so nobody copies, pastes or reconciles anything.
The event that was already on the record, upgraded in place.
The problem
The notes exist. They are just not where the work is.
Your best client's last four conversations are in four places, and none of them are on the client.
One is in a notetaker's workspace. One is a Slack message someone pasted. One is in a recruiter's notebook. One never happened at all because they were driving. So when a colleague opens that account before a call, the record shows an email from March. The information was captured and it still did not exist, because capture is not the job — the job is having it on the record when somebody else needs it.
Where it ends up
- A separate app with its own login and its own search
- Pasted into a note by whoever remembered
- Nowhere, because the summary email got buried
What it costs
- Colleagues covering an account with no history
- The same question asked twice by two consultants
- A leaver takes the client relationship with them
Why syncing doesn't fix it
- An integration pushes a blob into a notes field
- It cannot decide the notes belong on the job too
- It cannot make an action item a task somebody owns
How we solve it
1
Written onto the record, not into an inbox
The meeting becomes a note on the client, the candidate and the job it concerns — structured by what kind of meeting it was, and visible to anyone on the team who opens that record afterwards.
- Summary, key points and next steps, in recruitment language
- On the company, the contact, the candidate and the job as appropriate
- Same timeline as your calls, emails and WhatsApp messages
- Anyone covering the desk sees it without being told it exists
- Searchable with everything else, not in a second search box
- Bell and toast when it arrives, so you know it is done
2
One meeting, one entry — the event grows the notes
The calendar event that was created when Simi was invited is the same row that carries the notes afterwards. It is upgraded in place rather than joined by a second entry, so the timeline reads like a history instead of a reconciliation exercise.
- The card appears at invite time and fills in after the meeting
- Never a duplicate row, even if you connect a calendar later
- The platform is shown, so an attended meeting is obvious at a glance
- Ordinary calendar events look exactly as they always did
- Attendees resolve to real records, not email strings
3
Shaped by what the meeting actually was
A client briefing and a candidate screen produce different output, because they are different jobs. The meeting type decides the shape of the notes and the one action worth offering at the bottom of them.
- Client briefing: requirements captured as they were said, and a drafted job
- BD call: next steps and a note on the deal
- Screening: notes and a scorecard prefill on the candidate
- Interview and debrief: feedback structured per candidate
- Reference: the standard structure, on file, where compliance expects it
- Always overridable — you pick the type, we suggest it
What lands on the record
Ninety seconds after everyone hangs up.
The rest of the meeting
Notes on the record is one moment of it. They only work like this because they are all the same product as your CRM.
Questions recruiters ask
Which record do the notes go on?
The ones the meeting was actually about. Attendee emails are matched against your contacts and candidates, so a client briefing lands on the company and the contact, a screen lands on the candidate, and where there is an obvious job in play it lands there too. If nothing matches, the notes still arrive and ask you where they belong, with the likely records one click away. They are never lost and never quietly filed in the wrong place.
Can my team see meetings they were not in?
Yes, and that is the point of putting them on the record rather than in a personal workspace. Anyone with access to that client or candidate sees the history, so covering a colleague's desk does not mean starting from nothing.
What if the AI gets something wrong?
It is a note on a record, so you edit it like any other note, and the transcript is right there to check it against. Every summary sits next to the thing it was summarised from — that is the difference between a note you trust and a note you inherit.
Do I get an email too?
You get a notification, and the notes are on the record. We deliberately do not build the workflow around an email you have to act on, because that is the habit that leaves half the meetings unfiled.
Capture is not the job. Being on the record is the job.