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

# How Kello reaches out to candidates for you

> Kello's team contacts the candidates you mark Yes, then Maybe, from their own LinkedIn, email and WhatsApp, and brings interested people to you.

Kello reaches out on your behalf to the candidates you approve: everyone you mark **Yes**, then everyone you mark **Maybe**, never anyone you mark **No**. A named person on the Kello team contacts them from their own LinkedIn, email and WhatsApp, checks your must-haves in the conversation, and brings interested people who fit to a first conversation with you.

```mermaid theme={null}
flowchart TD
  A[You mark Yes or Maybe] --> B[You answer Kello's questions]
  B --> C[A named Kello person messages them]
  C --> D[Must-haves checked in the conversation]
  D --> E[Company name shared once they're open]
  E --> F[Private role page with your JD]
  F --> G[Calendar booking or email intro]
```

## What is the goal of outreach?

To get interested candidates to a first-round conversation with you. The people on your list didn't apply, and most aren't actively looking. Outreach turns a strong profile into a real conversation.

## Who does Kello contact?

| You mark | Kello contacts them? |
| - | - |
| Yes | Yes, first |
| Maybe | Yes, after your Yes picks |
| No | Never |

> [!TIP]
>
> Nobody is contacted until you mark them Yes or Maybe.

If you mark more people Yes later on your list page, Kello contacts them too, with no need to ask again.

Already know someone, or they're in your pipeline (People you're already talking to or interviewing for this role.)? Tell Kello or mark them No, and they won't be contacted. Best done on day 1: see [sending your pipeline](#when-should-i-send-my-pipeline).

## How do I start outreach?

There are two ways:

* **Kello asks you.** Once you've marked candidates, Kello replies on your email thread offering to reach out, with a few quick questions.
* **You ask Kello.** Email Kello any time, for example:

  ```text wrap theme={null}
  Please start outreach for the people I marked Yes and Maybe.
  ```

  Kello replies with the same questions.

Either way, nobody is contacted until you've answered the required questions below.

***

## What does Kello ask?

Before Kello contacts anyone, it asks you a few quick things. One short reply covers it.

### Required

Required

| # | Question | Why it matters |
| - | - | - |
| 1 | What should happen when a candidate is interested? | Share a calendar link, or name the person (or people) Kello should introduce candidates to by email. |
| 2 | What must every candidate meet? | Notice period (How long someone must keep working at their current job after resigning.), max salary, location, office days, visa. Kello checks these in the conversation and only brings you people who fit. |
| 3 | Anyone not to contact? | People you already know, people in your pipeline, or companies to keep out of it. |

If one required answer is missing, Kello asks for it before starting. `None` is a fine answer to the last one.

### Optional

Optional

| # | Question | Why it matters |
| - | - | - |
| 4 | Your pitch | The team, the manager, funding, the problems to solve. Kello builds these into each message. |
| 5 | Can the salary range be shared? | If yes, Kello shares it. If not, Kello asks each candidate's expectation and moves ahead if it fits your range. |
| 6 | Topics to avoid | Anything candidates shouldn't hear from Kello before they talk to you. |

## Is there a template for my answers?

Yes. Copy this, fill in the brackets, and reply on the thread. Numbered lines make it easy to match each answer to its question.

```text Outreach answers template wrap theme={null}
1. When a candidate is interested: calendar link [URL], or intro by email to [name, email]
2. Must-haves: max salary [amount], notice [N] days or less, based in or willing to move to [city], [office days], [visa]
3. Don't contact: [names, LinkedIn links or companies] (or "none")
4. Pitch: [2-3 lines: what the team does, stage and funding, who they'd work with]
5. Salary range: [OK to share X / don't share]
6. Topics to avoid: [topics, or "none"]
Also check: [anything to screen for, e.g. expected pay within budget]
```

## Example reply

```text Example reply wrap theme={null}
Calendar: https://cal.example.com/priya-30min - Priya (Engineering Manager) takes first calls.

Must-haves:
- Notice period 60 days or less
- Bangalore, 3 days a week in office
- Max 45 LPA fixed

Don't contact: anyone currently at our two main customers, and Rahul S. (already in our pipeline).

Pitch:
- Series A, raised last year, 30 people
- Small team, ships to enterprise customers every week
- Priya came from a large product company and runs a no-meetings-Wednesday team
- The hard problem: making our search fast at 10x today's data

Salary: OK to share 35-45 LPA fixed plus ESOPs.
Avoid: don't discuss the upcoming product launch.
```

A shorter reply works too. This is enough to start:

```text Shorter reply wrap theme={null}
Calendar link is X, notice under 60 days, Bangalore only, don't contact anyone at Y
```

## How have other teams answered?

Short, plain answers work. Three real replies, anonymised:

* **Founder, Forward Deployed Engineer:** "Don't share salary. Intro by email, plus book a call through \[calendar link]. Must be able to start on-site soon, at a manufacturing plant." For who not to contact: "None."
* **CTO, DevOps Engineer:** "\[Calendar link]. Don't mention anything comp related. Notice ideally 30 days, but not a hard no. Pitch: work directly with the CTO; we recently raised a Series A extension."
* **HR head, VP Distribution:** "Introduce them to me by email. Maximum salary 60 LPA (Lakhs per annum: yearly pay in Indian rupees (1 lakh = 100,000).). Notice period 90 days or less. Current or preferred location Bangalore."

> [!TIP]
>
> The CTO's "ideally 30 days, but not a hard no" is worth copying: it tells Kello which must-have can bend.

## Do I have to give a calendar link?

No. With a calendar link, each interested candidate books a first conversation directly with whoever takes it. Without one, Kello introduces the candidate by email to the person taking the hire forward. Kello connects candidates only with the people you name. See [first conversations](https://guide.kello.ai/kello/interviews-and-references.md#calendar-link-or-email-intro).

## Who receives introductions?

Whoever you name. It can be one person or several: the hiring manager, two recruiters, a founder. Say how you want it, for example:

```text wrap theme={null}
Connect each candidate to both recruiters, one candidate per email.
```

If you'd rather contact candidates yourself, say so up front. See [contacting a candidate yourself](#can-i-contact-a-candidate-myself).

## What makes a good pitch?

Specifics a candidate would care about. "Fast-growing startup" says little. "Series A, 30 people, you'd be the third engineer on the data team" gives Kello something to work with.

Keep it short. In India the first message usually goes out on WhatsApp, where a few lines land better than a long paragraph. `Standard, as per the JD` is a fine answer too: Kello builds the message from your JD (Job description: the document that describes the role.).

## Should I share the salary range?

It's your call. Sharing it lets candidates decide faster, and Kello shares it. Not sharing it is fine too: Kello asks each candidate's expectation and moves ahead only if it fits your range.

To keep it confidential, say `don't share the salary range`.

**Real example.** Kello replied to one team: *"We only use the range internally to calibrate seniority and benchmark the search, and it won't be disclosed to candidates."*

## When should I send my pipeline?

On day 1, with your outreach answers or earlier. Paste the names (LinkedIn links help) of people you've already spoken to, people in your interview process, and past outreach that didn't work out. Kello checks them against your list and keeps them out of outreach. This matters most for agencies and long-running searches.

**Real example.** An HR team sent the names of 20 people they had already approached. Six of them were already on the 20-person list, so Kello kept them out of outreach, leaving 14 people new to the team. Another team found out after outreach began that several candidates were already in their own database. Sending the pipeline up front avoids that.

## Can Kello screen for specific things?

Yes. Beyond your must-haves, name any topic Kello should check in the conversation, such as `check current and expected pay are within 30 LPA` or `ask about hands-on experience with [product category]`. Add these to your outreach answers, or reply later; Kello checks them from then on.

***

## Who sends the messages?

Our team. A named Kello person reaches out from their own LinkedIn, email and WhatsApp. Kello never uses your accounts.

A real person stands behind every conversation. AI gives them context on each candidate, so the message reads like it was written for them, because it was.

## Which channels does Kello use?

In India, most candidates reply on WhatsApp. Elsewhere, Kello reaches out on LinkedIn and email. Outreach works outside India too.

Have a preference? Say so, for example:

```text wrap theme={null}
Start on WhatsApp; if that doesn't connect, try LinkedIn.
```

## What does the first message say?

It's about the role and why it fits this person. Kello reads each profile closely first, so the message can speak to the candidate's actual work: what they built, the team they've been on, why this next step makes sense. It also carries your pitch points.

The message gets to the point. It doesn't open by asking about life goals.

## When does the candidate learn my company's name?

Only once they say they're open to a role like yours. Until then, the conversation is about the role itself. This keeps sensitive searches quiet.

## What is the private role page?

Interested candidates get a private page with your full JD, so they can read the role properly and decide. It's shared only with candidates you approved.

## How does Kello check fit?

Your must-haves, such as notice period, salary, location, office days or visa, are checked during the conversation. Only people who fit are brought to you.

Candidates can ask questions. The Kello team member answers from your brief and pitch, and checks with you before replying to anything else. Kello never makes up answers.

## Does Kello know a candidate's current pay?

No. Public profiles don't list pay, so Kello can't filter on current salary or confirm it in advance. Kello uses your budget to judge the right seniority when it builds your list.

Current pay, expected pay and notice period come out in the outreach conversation. Before your first call, you know what the candidate shared. See [what you know before the call](https://guide.kello.ai/kello/interviews-and-references.md#what-do-i-know-before-the-call).

***

## Can I take someone off the list later?

Yes, as long as Kello hasn't contacted them yet. Reply with the name, or mark them No on your list page.

**Real example.** One hiring manager wrote "actually, don't worry about \[candidate] unless you've already contacted them." Kello replied: *"I have not contacted him… I will not contact him."*

## Can I change what candidates hear?

Anytime. Reply with the change: `mention the ESOPs`, `ask about night shifts`, `notice period can go to 90 days`, `office days can be two, not three`. Kello updates what candidates hear from then on.

## What happens when a candidate is interested?

If the candidate fits your must-haves, they're connected to the person or people you named:

* **With your calendar link:** the candidate books a first conversation directly with that person.
* **Without a calendar link:** Kello introduces the candidate by email to the person taking the hire forward.

See [first conversations, references and contact details](https://guide.kello.ai/kello/interviews-and-references.md).

## How do I get an update?

Reply to Kello and ask. This is enough:

```text wrap theme={null}
Where are we on outreach?
```

Ask whenever it's useful, for example before a hiring sync. Kello groups every candidate it has contacted:

| Status | What it means |
| - | - |
| Introduced or booked | The candidate is interested, fits your must-haves, and has booked a first conversation through your calendar link, or Kello has introduced them by email. |
| Still in conversation | Kello is talking with the candidate. |
| Not moving forward | The candidate isn't moving ahead right now. You hear why, for example "not looking right now, open to reconnecting early next year." |

## Why do candidates say no?

You hear the reason, usually one of these:

* **Timing**: not the right moment to move.
* **Role**: the scope, level or kind of work isn't what they want.
* **Location**: the city or office days don't work.

These reasons sharpen your next list. If several people pass on the same thing, Kello takes that into account, and you may decide to adjust the role or the pitch.

Kello stays in touch with candidates who pass, in case they change their mind.

## Can I contact a candidate myself?

Yes. Ask Kello for their contact details.

Tell Kello when you reach out, so the candidate hears from one of you, not both. See [contact details](https://guide.kello.ai/kello/interviews-and-references.md#how-do-i-get-contact-details).

## Related

> [card] [Interviews and references](https://guide.kello.ai/kello/interviews-and-references.md)
>
> Calendar link or email intro, references, contact details.

> [card] [Your list](https://guide.kello.ai/kello/your-list.md)
>
> Mark Yes, Maybe or No.

> [card] [Feedback and next lists](https://guide.kello.ai/kello/feedback.md)
>
> How reasons sharpen the next list.

> [card] [For candidates](https://guide.kello.ai/kello/for-candidates.md)
>
> The page for candidates.

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.