Peloras Request an invitation

Invitation only

Peloras is the first AI RecOps Assistant built for recruiting agencies.

Fill more roles, faster, with the team you already have.

Your recruiters lose hours every day to scheduling, follow-ups, writing up calls and updating the ATS. Peloras does that work instead. They get the time back for candidates and clients, which is where placements actually come from.

Request an invitation See what it does

Works with the Google Workspace account your team already uses.

one agent

One agent, working across the whole recruiting workflow.

Not a set of separate tools your team switches between. The same assistant carries a role from the brief through to the offer, on the threads it already lives on, and everything it learns in one place stays available everywhere else.

FromArjun Mehra arjun@keystonetalent.in
ToPriya Raghavan priya.raghavan@fastmail.in
CcPeloras peloras@keystonetalent.in
SubjectSenior Backend Engineer at Adayan Systems
You copy it in

Add Peloras to the thread the way you would add a colleague. That is the whole setup.

It replies where the work is

Answers go on the same thread, to the same people, from your agency's own address.

It asks when it should

If something needs a person, it says so on the thread instead of guessing.

how you work with it

It works inside your email, like another person on the team.

There is no new tool for your recruiters to learn and no tab anybody has to keep open. Peloras is on the thread. You copy it in, it replies, it asks when it needs to, and everything it does sits in the same place your team already reads. That one idea is what the four capabilities below are built on.

what it does

Four jobs your recruiters do every day. Peloras does them instead.

Not one assistant that does a bit of everything. One agent that covers four specific pieces of the day, each one end to end, each one something your team would otherwise be doing at nine in the evening.

Interview scheduling Checks the calendar, offers times that are free, books the slot the candidate picks. Call follow-through Joins your client calls and candidate interviews, then does what comes out of them: the write-up, the ATS, the job spec, the submission. ATS Automation Moves candidates along the board, writes the record, and fetches what you ask for. The Talent Bench Keeps everyone you have already screened in play, and brings them back when a role fits.

interview scheduling

A candidate says yes once, and the interview is in the diary.

Peloras reads the request, checks the real calendars of everyone who has to be in the room, and only offers times that are genuinely free. When the candidate picks one, it writes the hold and sends the invites. Nobody goes back and forth.

Senior Backend Engineer at Adayan Systems one thread, start to confirmed

Arjun Mehra

Priya cleared the second round at Adayan and their VP Eng wants to meet her this week. She can only do evenings. Can you set it up?

Peloras

Sent Priya two evening options, Thursday at 6:30pm and Friday at 7:00pm. Both are open on your calendar and on the VP's.

  • read the thread
  • matched the open mandate
  • free and busy on 2 calendars
  • email sent

Priya Raghavan

Thursday works for me. Thanks for setting it up so quickly.

Peloras

Held Thursday at 6:30pm, sent the invite to Priya and the VP, and moved the mandate to Interview scheduled.

  • calendar hold written
  • invite sent to 2 guests
  • Arjun copied on everything
Interview confirmed, Thursday 6:30pm Arjun read about it at 9am

call follow-through

Everything a call creates gets done, not just written down.

Peloras joins your client calls and your candidate interviews, the same as anyone else on the invite. It takes the notes, and then it does the things the call created: the record updated, the job spec the client just described, the requisition sheet filled in, the submission that was promised. Your recruiter comes off the call and the follow-up is already moving.

00:00

What Peloras heard

What it did afterwards

Switch between the two calls, and click any highlighted line to see what it produced. It works the other way round too.

ats automation

Peloras works your ATS in both directions.

It moves candidates along the board as things actually happen, writes the details back to the record, and when your recruiter needs something out of the ATS it goes and gets it, then emails it to her. Nobody logs in to go looking.

Priya Raghavan, Senior Backend Engineer at Adayan Systems zoho recruit
NewScreenedInterviewOffer
Priya Raghavan7 yrs, payments

What happened this week

What it did

Pick an event. The card moves, the record changes, and the one where Arjun asks a question comes back as an email.

the talent bench

Every candidate you have already screened stays in play.

Most of the work your team puts into a candidate is thrown away the moment that role closes. Peloras keeps it. It remembers who you screened, what they wanted and when they come free, and it brings them back on its own when a new role fits. There is no bench for anybody to go and look at. It writes to you.

Overnight, with nobody working nobody asked for this

What Peloras did on its own

  1. 02:14

    Checked everybody your team has already screened against every role you have open.

  2. 02:14

    Rohit Nair's project at Adayan ends on 2 October. He is free from then.

  3. 02:15

    Vasant Retail's Platform Engineer role is still open, and he fits it on skills and on budget.

  4. 02:15

    You screened him in March, so there is nothing left to check.

  5. 06:00

    Wrote to Arjun.

What was waiting for Arjun at six

FromPeloras
ToArjun Mehra
SubjectRohit Nair comes free on 2 October

You screened Rohit in March for the Adayan role. He did not get that one. Vasant Retail's Platform Engineer role is still open and he fits it on skills and on budget.

Want me to write to him?

Nobody opened anything. Answering the email is the whole interaction.

the honest comparison

There are three ways this work gets done, and two of them already exist.

The first runs out of hours in the day. The second forgets everything the moment you stop watching it. We would rather show you where each one breaks than pretend they do not work.

How most agencies do it nowyour ATS, a spreadsheet, and whoever is still online A tool you build yourselfone developer, an API key, a few weekends Pelorasbuilt for a recruiting desk
A candidate replies at 11:40 at night Nobody sees it until the morning. By then two other agencies have already called her. It replies straight away, and nobody on your team sees what it said until a client forwards it back. It writes the reply, checks the calendar, and either sends it or holds it for your recruiter. You choose which, per client.
A candidate stops replying after the second interview Someone chases her if they remember. On a busy week nobody remembers. It chases the people someone wrote a rule for. Everybody else goes quiet with her. Every candidate has a next step and a date on it. Nothing sits untouched without someone being told.
Two clients want the same candidate Whoever asked loudest gets her CV first, and you hear about the clash afterwards. It has no idea the second role exists. Nothing told it. Both roles sit in one place, so you see the clash before the CV goes out.
It gets something wrong You hear about it from the client. You dig through logs, change the wording, and hope the next one comes out better. You can see what it sent and why, on the same thread, and move that step to approval only, in one click.
Your best recruiter resigns Six months of client history leaves with her, in her inbox and in her head. The same, and a tool only she knew how to restart. The history stays on the account. Whoever picks it up opens the thread and reads what happened.
Time to first result Weeks of new process that the team quietly stops following. A month building it, then a longer month fixing it against real email. One live role scheduled end to end in your first week.
Who keeps it running Your recruiters, on top of a full desk. You do. Every time the model changes or a mailbox behaves oddly, that is yours. We do.

control

You decide what it is allowed to send without asking.

Some clients are happy for candidate emails to go straight out. Others want to read every word first. That is a setting on the client, not a decision anyone has to remember.

  • Different rules for different clients

    Turn a step on for one client and leave it off for another. Nothing is set once for the whole agency.

  • Each recruiter connects her own calendar

    She can see her connection and remove it herself. No one else on the team can see it at all.

  • Disconnecting really disconnects

    Access is withdrawn at Google, not just forgotten on our side. You can check it in your own Google account and the entry is gone.

Peloras is invitation only.

Tell us how your desk runs today and which roles you are working on. If it is a fit, we will set you up on one live role and you can judge it from there.

Request an invitation See it across the whole desk

One agent, on the threads your team already works in.

© 2026 Peloras