Skip to main content
When a Kello list is off, the fastest fix is one plain, specific line that says what’s wrong and why, either as a note on the candidates you mark No or as an email reply. Kello reads that “why” alongside your Yes and No marks and adjusts the next list, which usually arrives within a few hours.

What should I write?

Find what you’re seeing in the list below. Open it, copy the line, edit it to fit, and send it as an email reply or add it as a note on the list page.
Usually means: the experience range or title level in the brief is wider than you meant.
Usually means: the brief undersold the scope, or the title reads lower than the real role.
Usually means: the brief didn’t say which industries matter or which to avoid.
Usually means: location was loose, or the city has a small pool and remote wasn’t mentioned.
Usually means: you want people more likely to say yes right now.
Usually means: the title is used differently across companies.
Usually means: one Yes is the clearest signal of your taste.
Usually means: company size or stage matters more than the brief said.
Usually means: the real must-haves aren’t written down yet.
Usually means: Kello may have misread the role.
If Kello misread something basic, like the level or the city, Kello restarts on the corrected brief, even mid-search.

What’s the difference between vague and specific feedback?

Vague feedback tells Kello the list missed, but not which way to move, so the next list is a guess. Specific feedback names what to add, drop or look for, so the next list pivots. These are real replies, anonymised:
The test: could someone who has never met you act on the line? If yes, Kello can too.

Why do named technical specifics work best?

Because they draw a hard line between people who look alike on paper. “Telephony experience” covers a lot of people. Naming the stack does not.
  • One team asked for “IP telephony stack, VoIP, SIP”, then narrowed further to “Asterisk, Kamailio, FreeSWITCH”.
  • Another separated “agentic AI” from “agentic SDLC”, two kinds of AI engineering that share most of their keywords.
For technical roles, name the tools, systems or problems the person must have worked on. Say what you mean by depth, too: core ML, not apps built on LLM APIs.

Can I ask for more of one kind of person?

Yes. The list page explains how Kello approached your search, including the kinds of people it looked for. If one of those descriptions is exactly right, paste it back with more of this. The same works with a person on your list.
More of this
The “because” matters. It tells Kello which part of the profile to look for again.

Tips for writing useful “why” notes

Kello studies your Yes and No profiles in depth to learn your team’s taste. A note makes the reason explicit, so Kello doesn’t have to guess which part of a profile you reacted to.

Name the reason, not the verdict

A No already says you don’t want them. The note should say why.
  • Weak “Not a fit.”
  • Good “Not a fit. Only agency experience, we need someone who has been in-house.”

Say whether it’s firm

Kello asks before relaxing your requirements. Telling it upfront which ones can bend saves a .
  • Weak “Should have 8+ years.”
  • Good “8+ years is flexible if they have led a team. Leading a team is firm.”

Tell Kello what you liked, too

Yes notes matter as much as No notes. They show Kello what to look for more of.
  • Weak “Yes.”
  • Good “Yes. Built the data team from scratch at a 50-person company. That’s the story we want.”

Pass on what you learned in interviews

After a first conversation, a line of interview feedback is often the clearest signal of all.
  • Weak “Didn’t work out.”
  • Good “Strong on systems design, but couldn’t explain trade-offs to a non-technical customer. Customer communication matters more than we said.”

Template: feedback after a round

1

Mark every candidate on your list page

2

Fill in the template

3

Reply to Kello's email as one message

Line 1 is an example, change the numbers.
Feedback after a round
Leave out any line you have nothing for. The “change for the next list” line does the most work.

Feedback and next lists

How Yes, Maybe, No and rounds work.

Your list

Why a list has fewer than 20.

Write a great brief

Get it right from the first list.
Send your next role to [email protected].
Last modified on October 17, 2026