Skip to main content
To give Kello feedback, mark each candidate Yes, Maybe or No on your list page and add a short note on why, or reply to Kello by email in plain words. Kello studies the people you said Yes and No to, reads your notes, and sends the next list of up to 20 new people, usually within a few hours. Each role includes up to 5 lists across 3 months from your first list.

How do I mark candidates?

Open the link to your Kello list page. Each candidate has three options: Next to each mark you can add a note on why. A few words are enough: too senior, love this one, wrong kind of sales. Anyone you share the list link with can review and mark candidates, so your hiring manager can give feedback directly.

How should I review a list?

Kello delivers fast. Searches most often stall because nobody reviews the list. Four habits keep a search moving:
  • Mark every candidate. Yes, Maybe or No on all of them, not just the ones that stand out. Kello notices a partial review and asks for the rest. Outreach starts once you mark people Yes (or Maybe) and answer Kello’s outreach questions.
  • Add a one-line reason to every No. In the Kello team’s words: “The No’s teach the agent your taste; a one-liner on why goes a long way.”
  • Review early. The best people on your list are often in demand elsewhere. A same-day pass of ten minutes beats a thorough one next week.
  • Mark even when you’re short on time. Marks alone still teach Kello. See do I need to add a note?
Real example: why a reason on each No matters. On a VP Engineering search, the client marked several people from the same well-known company as No. The company clearly wasn’t the problem, so Kello asked: “Could you tell us in a line why the ‘No’ candidates were not a fit? For example, level, company background, or the kind of work they lead…”The answer was one line: “Platform, System engineering and AI exposure was missing in almost all profiles.” The next list was sharply recalibrated around it.

Do I need to add a note?

No, but notes help a lot. Kello studies the Yes and No profiles in depth to learn your team’s taste. A mark tells Kello what you decided. A note tells Kello why, which makes the reason explicit instead of something Kello has to infer. For example, two people marked No for different reasons look the same without a note. With “too senior” on one and “no pharma” on the other, Kello knows exactly what to change. Marks alone still carry signal. Kello works out the pattern from your Yes and No marks and builds the next list around it. See the feedback playbook for what to write in common situations.

Can I give feedback by email?

Yes. Reply to Kello’s email in plain words. Some examples:
Example feedback replies
Email works well for feedback about the whole list rather than one person. You can mark candidates on the list page and send an email; Kello reads both.
Files emailed back, such as a spreadsheet of your marks, aren’t read. Mark on the list page or reply in words.

Should I send all my feedback at once?

Yes. Collect your thoughts and send them in one message.
Feedback sent while Kello is already building the next list can miss that .
If your hiring manager is reviewing too, agree on the feedback first, then send it together. The feedback-after-a-round template keeps it to a few lines.

What about feedback after interviews?

Send it. Interview outcomes are the strongest signal Kello gets. A profile shows what someone has done; a conversation shows how they’d do in your team. Short lines are enough: Passed round 1, no-show, pay expectations too high, strong on systems design, weak on customer calls. If your is connected, Kello can pull interview feedback back from it. See Your team and ATS.
Real example: learning from marks and interviews. A voice-AI startup hiring for DevSecOps wrote little on the list itself. Kello read the pattern from its marks. Kello replied: “pure SecOps is insufficient. Derived from rejections of pure security profiles.” It also noted a high Yes rate for people from B2B SaaS and fintech companies.The client then sent interview outcomes per candidate, such as “too expensive” and “bad comms”. The next list targeted mid-level seniority, to avoid people who were too senior or above the pay range.

What does Kello do with my feedback?

Kello uses your marks, notes and emails to understand what your team values, then searches again for your next list. Feedback also decides who Kello reaches out to. Everyone you mark Yes is contacted first, then everyone you mark Maybe. Nobody you mark No is contacted. See outreach.
Already know someone on the list, or they’re in your ? Mark them No, or tell Kello, and they won’t be contacted.

How do I get the next list?

Give feedback on the current one, on the list page, by email, or both. Kello uses it to search again and sends the next list, usually within a few hours.

How is the next list different?

It reflects what you told Kello. If you wrote “too senior” on three people and “love this one” on another, the next list leans toward what you liked. If your feedback isn’t moving the list the way you want, the feedback playbook has what to write for common cases.

How do rounds work?

Each list is a round. Every new round:
  • Opens with what changed since the last list. Kello says what it added, tightened or dropped, and cites the feedback that caused each change. Read this first to check Kello understood you.
  • Has only new people. Nobody you’ve already seen comes back.
  • Gets more precise. Each round builds on every mark, note and interview outcome so far.
Real example: tightening a niche over three rounds. An energy-data company hiring an Applied AI Engineer asked for “3-5 years… AI in an energy or data company”. In round 2, Kello added hands-on work with complex energy data as a requirement.The client then named five favourites, each with a reason, such as one who had built a text-to-SQL chat engine at an energy tech company. Round 3 moved from general “text-to-query” to text-to-SQL specifically. The lists went from 20 to 19 to 12 people, each tighter than the last.

Will I see the same people again?

No. Every new list contains only new people. You never see the same person twice for a role.

How many lists do I get?

A list can have fewer than 20 people if not enough meet the bar. Kello tells you which requirement is narrowing the search so you can decide if it can bend. See why a list has fewer than 20 people.

What if Kello misread the role?

Reply with the correction: It's a Director role. Pune, not Bangalore. Kello restarts on the corrected brief, even mid-search. A correction is part of the same role, not a new one.

Can I start the search from scratch?

Yes. Reply with this line, along with the sharper or corrected brief:
Kello drops its earlier reading of the role and searches again. Check you’ve attached the right before you send. A restart works from whatever you give it.

What happens after the last list?

Kello tells you when a list is the final one for the role. If you still need people, start fresh with a sharper brief. Put in what the lists and interviews taught you: the kinds of people who worked, what to avoid, and which requirements turned out to be firm.

What happens after 3 months?

If the role is still open after 3 months, you can renew it and Kello keeps going. See kello.ai/pricing for renewal terms.

Is my feedback shared with anyone?

No. Your feedback is used only for your own role: to get your lists right and to decide who Kello contacts. It’s never used to train Kello’s algorithms or shared with other customers. See data, privacy and fairness.

Feedback playbook

What to write when the list is off.

Your list

What’s on the list page, and short lists.

Outreach

How Kello reaches out to your Yes and Maybe picks.
Send your next role to [email protected].
Last modified on October 17, 2026