> ## Documentation Index
> Fetch the complete documentation index at: https://guide.kello.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Feedback playbook: what to tell Kello when a list is off

> If your Kello list is off, tell Kello why in one specific line. Copy-ready feedback for 10 common cases, vague vs specific examples and a round template.

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.

> [accordion] Candidates are too senior
>
> Usually means: the experience range or title level in the brief is wider than you meant.
>
> ```text wrap theme={null}
> Too senior. We need someone who still writes code daily, 5–8 years, not people managing managers.
> ```

> [accordion] Candidates are too junior
>
> Usually means: the brief undersold the scope, or the title reads lower than the real role.
>
> ```text wrap theme={null}
> Too junior. This person will own the function and report to the CEO. Look for people who have already led a team of 5+.
> ```

> [accordion] Wrong industry
>
> Usually means: the brief didn't say which industries matter or which to avoid.
>
> ```text wrap theme={null}
> No pharma or healthcare. Prefer B2B SaaS, ideally companies selling to mid-market.
> ```

> [accordion] Too few people in my city
>
> Usually means: location was loose, or the city has a small pool and remote wasn't mentioned.
>
> ```text wrap theme={null}
> Bangalore is a must. Open to people willing to relocate from Pune or Hyderabad.
> ```

> [accordion] Good profiles, but they won't move
>
> Usually means: you want people more likely to say yes right now.
>
> ```text wrap theme={null}
> Several of these just joined new roles. Prioritise people who have been in their current role a while.
> ```

> [accordion] Great profiles, wrong function
>
> Usually means: the title is used differently across companies.
>
> ```text wrap theme={null}
> These are solutions engineers. We need people who build and ship product, then sit with customers. Engineering first.
> ```

> [accordion] I liked one person, I want more like them
>
> Usually means: one Yes is the clearest signal of your taste.
>
> ```text wrap theme={null}
> Love [name]. Their move from an early-stage startup into a larger company is exactly what we want. More like this.
> ```

> [accordion] Wrong kind of company
>
> Usually means: company size or stage matters more than the brief said.
>
> ```text wrap theme={null}
> Too many large enterprises. We want people who have worked at startups between 20 and 200 people.
> ```

> [accordion] Strong on paper, but my hiring manager said no
>
> Usually means: the real must-haves aren't written down yet.
>
> ```text wrap theme={null}
> Hiring manager wants hands-on experience with enterprise customers. That's a must-have, not a nice-to-have.
> ```

> [accordion] The whole list feels wrong
>
> Usually means: Kello may have misread the role.
>
> ```text wrap theme={null}
> This is a Director role, not a Manager role. Please restart on that basis.
> ```

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:

| Vague (leads to a blind re-run) | Specific (leads to a sharp pivot) |
| - | - |
| "Didn't find anyone exciting." | "Proof of people who have made long-format videos with AI, more than 3–4 minutes, and multilingual." |
| "These profiles don't fit the requirement." | "No marketplaces. Look for FMCG, ecommerce and D2C brands." |
| "None of the profiles worked so far." | "Too data-heavy. Focus on pure product experience: user journeys, A/B testing. Avoid banking." |
| "More senior." | "10+ years, ideally on revenue cycle work for dental offices. Customer onboarding experience is a huge plus." |

> [!TIP]
>
> 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.

```text More of this wrap theme={null}
More of this: [paste the description from your list page].
More like [name], because [one line on what makes them right].
```

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 round (Each list is a round: one list, plus your marks and feedback on it.).

* 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.

```text Feedback after a round {1} wrap theme={null}
Marked all 20 on the list page (8 Yes, 3 Maybe, 9 No), with a reason on each No.

What's working: [the pattern in the Yes's]
What's off: [the pattern in the No's: level, company type, missing skill]
Change for the next list: [one requirement to add, drop or bend]
More like: [name from the list], because [one line]
Interview update: [name: passed round 1 / no-show / pay mismatch]
```

> [!TIP]
>
> Leave out any line you have nothing for. The "change for the next list" line does the most work.

## Related

> [card] [Feedback and next lists](https://guide.kello.ai/kello/feedback.md)
>
> How Yes, Maybe, No and rounds work.

> [card] [Your list](https://guide.kello.ai/kello/your-list.md)
>
> Why a list has fewer than 20.

> [card] [Write a great brief](https://guide.kello.ai/kello/write-a-great-brief.md)
>
> Get it right from the first list.

Send your next role to [source@kello.ai](mailto:source@kello.ai).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.