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

# First conversations, references and contact details

> Kello sets up first conversations via your calendar link or an email intro, guides your reference checks, and shares contact details at no extra cost.

When a candidate is interested and fits your must-haves, Kello connects them with the person you named, by calendar link or email intro. Kello also tells you who to call for references and what to ask, and shares any candidate's contact details, all included in the role fee.

## Calendar link or email intro?

| Question | Calendar link | Email intro |
| - | - | - |
| How it works | Each interested candidate books a first conversation directly with whoever takes it | Kello introduces the candidate by email to the person taking the hire forward |
| Who sets the time | The candidate, from your calendar | You and the candidate, over email |
| Good for | Moving fast with many candidates | Founders or hiring managers who prefer to reach out personally |

You tell Kello which you prefer when you answer [Kello's outreach questions](https://guide.kello.ai/kello/outreach.md#what-does-kello-ask).

## Who are candidates connected with?

Only the person you name. That could be you, the hiring manager, or a founder. If different people take first calls for different roles, tell Kello per role.

## What do I know before the call?

Before the call, you know what the candidate shared with Kello. Depending on the candidate, that can include:

* Notice period (How long someone must keep working at their current job after resigning.)
* Current and expected pay
* Availability
* CV, when they shared one

Not every candidate shares every detail. Kello passes on what they did share.

You also have their profile on your list page, including the **why this candidate** reasons and the **worth checking (The one thing on each candidate Kello suggests you confirm.)** note. The worth checking note is a good place to start your questions.

## What has the candidate already seen?

The candidate has:

* Heard from a named person on the Kello team about the role and why it fits them.
* Learned your company's name.
* Read your full JD (Job description: the document that describes the role.) on a private role page.
* Had your must-haves checked in the conversation.

See [outreach](https://guide.kello.ai/kello/outreach.md#when-does-the-candidate-learn-my-companys-name).

## What should I do after the conversation?

Email Kello your interview feedback. A line like this tells Kello more than any profile can, and it shapes your next list:

```text wrap theme={null}
Strong on systems design, weak on customer calls
```

If your ATS (Applicant tracking system: the software your team uses to track candidates.) is connected, Kello can pull interview feedback from it. See [Your team and ATS](https://guide.kello.ai/kello/team.md#what-does-the-ats-connection-do).

When you're close to a decision, ask Kello for reference-check guidance.

***

## What does Kello give me for reference checks?

For each candidate you're serious about:

* **Who to speak to**: people who can speak to how the candidate actually works.
* **What to ask**: questions tied to this candidate and your role, not a generic script.
* **Contact details**: so you can reach those people directly.

## Who makes the reference calls?

You do. Kello prepares the guidance and contact details; you or your hiring manager speak to the references. Kello doesn't schedule reference calls.

## How do I ask for reference guidance?

Reply to Kello and name the candidate. This is enough:

```text wrap theme={null}
Can you send reference guidance for Ananya?
```

A good time to ask is when you're close to a decision, after first conversations.

## What makes a reference call useful?

A few habits help:

* **Start with the worth checking note.** Each candidate on your list has one thing to verify. It's a natural first question for a reference.
* **Ask for examples, not ratings.** "Tell me about a time they disagreed with their manager" gets more than "Were they good?"
* **Check what you heard in the interview.** If the candidate described leading a project, ask the reference what their part was.
* **Share what you learn.** Email Kello your takeaways. It helps Kello understand what your team values.

***

## How do I get contact details?

Reply to Kello and name the candidate. For example:

```text wrap theme={null}
Can you share contact details for the three people I marked Yes?
```

## Should I contact candidates myself or let Kello do it?

Either works, and you can mix them. Let Kello handle outreach and step in for first conversations, or reach out personally to one or two people you're especially keen on.

| Question | Kello reaches out | You reach out |
| - | - | - |
| Who sends the message | A named person on the Kello team | You |
| Must-haves checked | In the conversation, before you meet | By you |
| Company name revealed | Once they're open to a role like yours | Immediately |
| Best for | Most candidates | A few people you want to approach personally |

See [outreach](https://guide.kello.ai/kello/outreach.md#who-sends-the-messages) for how Kello's outreach works.

## Why should I tell Kello when I reach out?

So the candidate hears from one of you, not both. Kello's team may already be talking to the candidate, or about to, so a quick note keeps the experience clear for them.

A one-line reply works:

```text wrap theme={null}
I'm reaching out to Vikram directly.
```

## Do I keep the contact details?

Yes. You keep everyone Kello finds and their contact details.

## Related

> [card] [Outreach](https://guide.kello.ai/kello/outreach.md)
>
> Calendar link, must-haves, pitch and status.

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

> [card] [Your list](https://guide.kello.ai/kello/your-list.md)
>
> The worth checking note and more.

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.