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

# Troubleshooting Kello: common problems and fixes

> Fixes for common Kello problems: a bounced request, an unreadable JD link, budget questions, the wrong role, a short list, or no reply yet.

Most Kello problems are fixed with one short email reply: tell Kello what's wrong in plain words and it adjusts, even mid-search. Below are the common ones, in the order you'd hit them, each with the likely cause and the fix. For anything else, email [support@kello.ai](mailto:support@kello.ai).

**Sending your role:** [My request bounced](#my-request-bounced) · [Kello couldn't read my JD link](#kello-couldnt-read-my-jd-link) · [Kello says it can't start the role](#kello-says-it-cant-start-the-role) · [Kello keeps asking about budget](#kello-keeps-asking-about-budget) · [I haven't received my first list yet](#i-havent-received-my-first-list-yet) · [Kello identified the wrong company](#kello-identified-the-wrong-company) · [Kello misread the role](#kello-misread-the-role) · [Kello sourced the wrong role](#kello-sourced-the-wrong-role)

**Your list:** [I can't open the list link](#i-cant-open-the-list-link) · [My colleague can't see the list](#my-colleague-cant-see-the-list) · [I got fewer than 20 people](#i-got-fewer-than-20-people) · [I got no list at all](#i-got-no-list-at-all) · [The new list looks similar to the last one](#the-new-list-looks-similar-to-the-last-one) · [My feedback didn't make it into the next list](#my-feedback-didnt-make-it-into-the-next-list) · [I emailed back a spreadsheet of marks](#i-emailed-back-a-spreadsheet-of-marks)

**Outreach:** [Kello hasn't started outreach](#kello-hasnt-started-outreach) · [No candidate has replied yet](#no-candidate-has-replied-yet) · [Someone on my list is already in my pipeline](#someone-on-my-list-is-already-in-my-pipeline)

## My request bounced

**Cause:** Kello accepts roles only from work email addresses.

> [!WARNING]
>
> Use your work email. Roles sent from personal addresses, such as Gmail, aren't accepted.

> [!TIP]
>
> **Fix:** Send the role again from your work email.

## Kello couldn't read my JD link

**Cause:** Kello can't open every link. Notion pages and some job-board links fail most often. Kello replied to one team: *"I wasn't able to access the JD through that Notion link. Could you please paste the full text here or attach it as a PDF or Word document?"*

> [!TIP]
>
> **Fix:** Paste the JD (Job description: the document that describes the role.) text into your reply. That's the most reliable format. A PDF or Word file usually works too, and LinkedIn, ATS (Applicant tracking system: the software your team uses to track candidates.) and careers-page links usually work. If you send a link, paste the key details as well. See [which JD formats work best](https://guide.kello.ai/kello/write-a-great-brief.md#which-jd-formats-work-best).

## Kello says it can't start the role

**Cause:** Kello couldn't find enough to search on. Three things cause this:

* **The JD lists only requirements.** Kello needs to know what the person will do, so a brief with no responsibilities can't start.
* **A forwarded hiring post doesn't name the role or company.** Kello replied to one: *"since it doesn't specify a role or company, I'm not able to start a search from it just yet."*
* **A blank template.** `I am hiring for: ___` with nothing filled in gives Kello no role to read.

> [!TIP]
>
> **Fix:** Reply with a few lines on what the person will do, plus the role title and company. When you forward a social post, add one line with role, company, location and pay, for example:
>
> ```text wrap theme={null}
> Budget: market. Location: remote US.
> ```

## Kello keeps asking about budget

**Cause:** Kello treats "Flexible" as unanswered, because it doesn't tell Kello what seniority to search for. A missing budget is the most common reason a search waits.

> [!TIP]
>
> **Fix:** Give a range, or say there isn't one: `No fixed budget, use market rates` is a complete answer. Check the number with the hiring manager first. In one search, a guessed budget turned out far below the real one, and the first list was built on the wrong level. See [location and budget](https://guide.kello.ai/kello/write-a-great-brief.md#do-i-need-to-give-a-location-and-budget).

## I haven't received my first list yet

**Cause:** The first list usually takes about two hours. If something important was missing from your brief, such as location, budget or work setup, Kello asks one short question before searching.

> [!TIP]
>
> **Fix:** Check your inbox for a question from Kello and reply. A one-line answer is enough, for example `No fixed budget, use market rates`. If there's no question and it's been more than a few hours, email [support@kello.ai](mailto:support@kello.ai).

## Kello identified the wrong company

**Cause:** Your company name is shared with other companies, so Kello read the wrong one.

> [!TIP]
>
> **Fix:** Reply with your company website. Include your website in future briefs too. Kello starts with your company, so getting it right matters.

## Kello misread the role

**Cause:** The JD left something open, or it was read in a way you didn't mean.

> [!TIP]
>
> **Fix:** Reply with the correction: `it's a Director role`, `Pune, not Bangalore`. Kello restarts on the corrected brief, even mid-search. It's the same role, not a new one. Kello confirms how it read the role within minutes of your brief, so check that confirmation early.

## Kello sourced the wrong role

**Cause:** Usually one of two things. The wrong file was attached: in one case, an email about an ML role carried a product marketing JD, and Kello searched for product marketing. Or the email didn't name the role and company, so Kello matched it to an older role from your company.

> [!TIP]
>
> **Fix:** Reply with the right JD and say `start from scratch`. Kello restarts the search on it. Before sending, check the attachment, and put the role and company in the subject line, for example `Backend Architect – [Company]`.

## I can't open the list link

**Cause:** Long links can break when they are copied, pasted or forwarded.

> [!TIP]
>
> **Fix:** Click the link straight from Kello's email rather than copying it. If it still won't open, reply to that email or write to [support@kello.ai](mailto:support@kello.ai) and Kello will help.

## My colleague can't see the list

**Cause:** Your colleague doesn't have the list link and isn't on the role's email thread. Only people you share the link with can see your results.

> [!TIP]
>
> **Fix:** Add them to the thread with Kello on CC, or forward them the link to your Kello list page. Anyone with the link can review and mark candidates. See [Your team and ATS](https://guide.kello.ai/kello/team.md#how-do-i-share-a-list-with-my-team).

## I got fewer than 20 people

**Cause:** Not enough people met the bar. Kello would rather send 14 strong people than pad the list.

> [!TIP]
>
> **Fix:** Kello tells you which requirement is narrowing the search. Decide whether it can bend, and reply. See [why the list is short](https://guide.kello.ai/kello/your-list.md#why-are-there-fewer-than-20-people).

## I got no list at all

**Cause:** You never get an empty list. If nobody fits, Kello adjusts an assumption it made and searches again, or asks you one clear question about one of your requirements, such as "is the 8-year minimum firm?"

> [!TIP]
>
> **Fix:** Answer the question with a one-line reply. If it's still stuck, someone from the Kello team steps in. See [what happens if nobody fits](https://guide.kello.ai/kello/your-list.md#what-happens-if-nobody-fits).

## The new list looks similar to the last one

**Cause:** Every new list contains only new people, so you won't see the same person twice for a role. If the profiles feel alike, Kello is still working from the same reading of your brief and feedback.

> [!TIP]
>
> **Fix:** Tell Kello what to change, in plain words: `more B2B SaaS`, `no pharma`, `must have managed 5+`. Add a note on why when you mark No. Notes like `too senior` make the reason explicit. See the [Feedback playbook](https://guide.kello.ai/kello/feedback-playbook.md).

## My feedback didn't make it into the next list

**Cause:** You sent it while a round (Each list is a round: one list, plus your marks and feedback on it.) was already running. Kello may reply that the round is already underway.

> [!WARNING]
>
> Feedback sent while Kello is already building the next list can miss that round.

> [!TIP]
>
> **Fix:** Send it again on the thread, and it shapes the next list. Next time, review the whole list first, then send all your feedback in one message. See [sending all your feedback at once](https://guide.kello.ai/kello/feedback.md#should-i-send-all-my-feedback-at-once).

## I emailed back a spreadsheet of marks

**Cause:** Kello doesn't read files emailed back, such as a spreadsheet of marks or a marked-up download of your list.

> [!TIP]
>
> **Fix:** Mark Yes, Maybe or No on your list page, or reply in words, for example:
>
> ```text wrap theme={null}
> Yes to the three from fintech, No to anyone without team management.
> ```
>
> See [how to mark candidates](https://guide.kello.ai/kello/feedback.md#how-do-i-mark-candidates).

## Kello hasn't started outreach

**Cause:** Outreach starts when you reply to Kello's offer to reach out, or when you email Kello asking it to start. Before contacting anyone, Kello asks you a few quick questions, such as what should happen when a candidate is interested and which requirements every candidate must meet. Nobody is contacted until you mark Yes or Maybe.

> [!TIP]
>
> **Fix:** Mark the candidates you want contacted Yes or Maybe on your list page. Then reply to Kello's questions, or email Kello asking it to start outreach for the role. One short reply is enough. See [what Kello asks](https://guide.kello.ai/kello/outreach.md#what-does-kello-ask).

## No candidate has replied yet

**Cause:** Kello is reaching out, and replies take time. Most candidates aren't actively looking.

> [!TIP]
>
> **Fix:** Ask Kello for an update anytime. You'll hear who has been introduced or booked time, who's still in conversation, and who isn't moving forward, with the reason. Marking more people Yes or Maybe widens who Kello contacts. See [outreach updates](https://guide.kello.ai/kello/outreach.md#how-do-i-get-an-update).

## Someone on my list is already in my pipeline

**Cause:** Kello doesn't know who you've already spoken to.

> [!TIP]
>
> **Fix:** Tell Kello and they won't be contacted, or mark them No. Send your pipeline (People you're already talking to or interviewing for this role.) on day 1 to avoid this: see [sending your pipeline](https://guide.kello.ai/kello/outreach.md#when-should-i-send-my-pipeline).

> [card] [Still stuck? Email support@kello.ai](mailto:support@kello.ai)

## Related

> [card] [Write a great brief](https://guide.kello.ai/kello/write-a-great-brief.md)
>
> What the first email needs.

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

> [card] [Feedback playbook](https://guide.kello.ai/kello/feedback-playbook.md)
>
> What to write for each problem.

> [card] [Outreach](https://guide.kello.ai/kello/outreach.md)
>
> Get an update on candidates.


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