AI for recruitment agencies, from the brief to the placement
A placement passes through the applicant tracking system, a mailbox, a calendar, a CRM and a signed contract, and the consultant is the only thread between them. Memtro connects to the tools a recruitment business already runs on and answers questions across them, with every fact cited, so a consultant walks into a client call briefed and a candidate is never asked the same question twice.
7-day free trial · card on file, nothing charged until it ends · cancel any time
Candidates, roles, clients, conversations and placements answered from one memory, with every fact cited to its record.
The systems these questions draw on, connected to one memory. Every connector reads by default; the tools that change something are granted by name, per team.
What it looks like today
- 01The candidate's status is in the ATS, the last conversation is in email and the interview is in a calendar.
- 02Which clients have open roles and which have gone quiet is a report nobody runs.
- 03A consultant leaves and the history of their relationships leaves with them.
- 04Terms agreed on a call are in nobody's record until the invoice is disputed.
- 05The same candidate is approached twice by two consultants, because the first conversation lived in one inbox.
- 06A client brief is taken on a call and retold three times, slightly differently, to three colleagues.
What Memtro does about it
One memory in front of the systems you already pay for, reading by default and acting only where an administrator has granted the tool by name.
- Connect Greenhouse, Gmail, Google Calendar, Calendly, HubSpot, Typeform and DocuSign, reading by default and acting where you grant it.
- Ask about a candidate or a client and the answer draws on the ATS, the correspondence and the calendar together, each fact cited; Gmail can draft the follow-up when asked.
- Candidates, clients and roles are anchored into memory, so what was discussed and promised is remembered across consultants.
- The commitments register keeps what was agreed with a client on a call and checks whether it was done.
- Schedule jobs: roles with no candidate movement for a week, interviews tomorrow with the last correspondence, contracts awaiting signature.
System by system
What Memtro reads in each part of the stack, and what it may change there once the tool has been granted.
The applicant tracking system
Greenhouse: jobs, candidates, applications, stages, scorecards and scheduled interviews, read as the spine that the mail and the diary hang off.
Mail and attachments
Gmail or Outlook: the thread with a candidate or a client, and the CV or specification attached to it read as text. Mail can be drafted or sent once the action is granted.
Diary and booking
Google Calendar, Outlook Calendar and Calendly: interviews, availability and what has actually been booked. The calendar can create or move an event when you ask and the tool is granted.
The CRM
HubSpot, Salesforce or Pipedrive: clients, roles, fees and owners, with records created or changed only through a granted action.
Forms and terms
Typeform for briefs and candidate forms, DocuSign for terms of business and contracts: what was agreed, who has signed and who has been sitting on it for a week.
Sourcing and the public record
LinkedIn, web search and the web scraper for what a candidate or a client has published, read inside the conversation rather than in six tabs.
There are 144 connectors in all, each with its own tools, its own permissions and a page of its own. Browse every connector →
Who asks what
Consultant
Walks into a client call with the role, the candidates in process, the last thing said on each side and what was promised about fees.
Resourcer
Checks before approaching: whether the firm has spoken to this person before, who did, when, and how it was left.
Client lead
Watches the account: which roles are live, which have stalled, what feedback came back and which clients have gone quiet.
Director
Sees the desk without a report: roles by client, days since movement, terms unsigned and invoices unpaid.
From brief to placement
- 01
The brief
What the client actually asked for — in the call, the mail and the form — is kept against the role, so the fourth consultant to touch it works from the same brief as the first.
- 02
The search
Before an approach, one question says whether the firm has spoken to this person, who did and how it ended. Candidates and clients are anchored into memory as they appear.
- 03
In process
Interviews, feedback and next steps are read from the ATS, the diary and the mail together, and a daily job names the candidates stuck in a stage.
- 04
Offer and invoice
Terms out for signature are chased by a job rather than a memory, and what was agreed on fees is checked against the signed document when the invoice is queried.
Ask it like this
Plain English, from chat, your editor, a scheduled job or your own agent. In agent mode each question also checks the other systems that know about the same people, companies and references, and the answer ends with a line per system consulted.
- Greenhouse
- Gmail
- Google Calendar
- Calendly
- HubSpot
Every figure in the answer cites the record it came from, and the run ends with a line per system consulted.
- ›Which open roles have had no candidate activity in seven days?
- ›What did we agree with BigCo on fees, and is it in the signed terms?
- ›Who is interviewing tomorrow, and what did they tell us about notice periods?
- ›Have we spoken to this candidate before, and who at the firm did?
- ›Which candidates have we put forward to Acme this year, and what came of each?
- ›What feedback came back on the three candidates for the Riverside role?
- ›Which clients have we not spoken to in 60 days, and what did they last brief us on?
Work that runs itself
A job is a prompt the agent runs on a cron schedule as its owner, with their tools and connections. Say any of these in chat and the job exists; every run's report is kept in a chat you can question.
- schedule:Every day 08:00: interviews today and tomorrow, with the candidate's last correspondence and the client's notes
- schedule:Every Monday 08:00: open roles by client with days since the last candidate movement
- schedule:Every Friday 16:00: terms sent for signature and still unsigned after five days
- schedule:Every day 17:00: candidates in the same stage for more than ten days, with the consultant who owns them
- schedule:Every Monday 09:00: clients with no contact in 60 days, with the last role they briefed us on
Questions people ask
Can it email candidates?+
Only where you grant the action. Gmail can send or draft when asked, and the draft is yours to read first; Google Calendar can book the interview, and HubSpot can update the record. Each is granted by name per team, and a connector only reads until it is.
What about candidate privacy?+
Memory classifies personal versus shared facts per fact, connections are granted to named teams, and a request to be forgotten removes a person across every store, verified and receipted.
Does it support other applicant tracking systems?+
Greenhouse is the one with a connector today. Any system with a reporting database is reachable over Postgres, MySQL or SQL Server, and the mail, calendar and CRM around the process are covered either way.
Does it screen or rank candidates?+
No. It reads and answers: what a candidate told us, where they are in process, what the client said. It does not score people or decide who proceeds, and anything that looks like a shortlist in an answer is the consultant's own criteria applied to records that are cited and can be checked.
Where do CVs come from?+
From Greenhouse, and from the mailbox: a PDF or Word CV attached to an email is read as text, so a CV sent straight to a consultant is as findable as one in the system.
Can a consultant's contacts stay their own?+
Yes. A connection is personal to one person or shared with named teams, and memory is classified fact by fact, so a personal mailbox serves only its owner's requests while what the business needs to keep is kept.
The same work, by team
The same connectors and the same memory, described through the job somebody does rather than the business they do it in.
- SalesWalk into every call briefedAccount history, open tickets, invoices, the last email thread and what was decided internally, pulled together from the systems that hold them and remembered for next time.Memtro for sales
- People and onboardingThe answers a new hire would otherwise ask around forPolicies, who owns what, how things are done and why: Memtro learns them from documents, conversations and the systems you connect, and keeps personal matters personal.Memtro for people and onboarding
- OperationsMonitors and digests that run themselvesJobs are prompts the agent runs on a schedule with the same tools as their owner. Create them in plain language, get the report in a chat, pause or change them in a sentence.Memtro for operations
Ask it about your own business
Connect the first two systems, ask the question you opened this page with, and see where the answer comes from. About five minutes.
7-day free trial · card on file, nothing charged until it ends · cancel any time