> ## Documentation Index
> Fetch the complete documentation index at: https://docs-vnext.kiflo.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Kiflo Leads Overview: Types, Statuses, and Lifecycle

> Learn what leads are in Kiflo, the difference between Shared and Submitted leads, and how to manage the full lead lifecycle from submission to conversion.

Leads in Kiflo represent unqualified sales opportunities — prospects that have shown interest but have not yet been vetted or moved into your sales pipeline as deals. Kiflo gives you a structured way to exchange leads with partners, track their status, and convert the best ones into deals.

## Two types of leads

Kiflo supports two directions of lead exchange between you and your partners.

**Shared Leads** — You are the source. You create a lead in Kiflo and assign it to a partner, for example when you want a reseller to follow up on an inbound inquiry. The partner receives a notification and must accept or decline the lead before working on it.

**Submitted Leads** — The partner is the source. Partners submit leads directly from the partner portal (or via a referral link, lead form, or standalone lead form). You review each submission and accept or decline it.

<Note>
  You can also submit a lead on behalf of a partner — useful when a partner
  sends you lead information outside of Kiflo. In that case the lead is
  accepted automatically.
</Note>

## The lead lifecycle

Every lead in Kiflo moves through a defined set of statuses.

```
Submitted / Shared → Pending → Accepted or Declined → Converted to Deal or Customer
```

| Status        | What it means                                        |
| ------------- | ---------------------------------------------------- |
| **Pending**   | The lead has been created and is awaiting review     |
| **Accepted**  | The lead has been approved by you (or auto-accepted) |
| **Declined**  | The lead has been rejected                           |
| **Converted** | The lead has been converted into a deal or customer  |

Once a lead is accepted you can convert it to a deal directly from the lead detail page. If you have matching properties set up between leads and contacts, those values copy across automatically — no re-entry needed.

## Key features

### Auto-accept

If your workflow doesn't require manual review of every lead, you can set the validation strategy to **No validation**. All incoming leads will be accepted automatically the moment a partner submits them.

### Channel conflict detection

Before you accept a lead you may want to know whether another partner — or your direct sales team — is already working with that prospect. Enable channel conflict detection in Account Settings and Kiflo will flag any lead whose client email domain matches an existing lead, deal, or customer.

### Re-assignment

After you share a lead with a partner you can reassign it to a different partner at any time, as long as the lead is still in **Pending** status. You can include a deadline and add a private or partner-visible note when you reassign.

### Standalone lead form

Every partner team member has a personal, bookmark-able lead form URL they can use to submit leads without logging in to the portal. You can retrieve these URLs from the partner's **Team** tab in the admin portal.

## Next steps

<CardGroup cols={2}>
  <Card title="Referral Links" icon="link" href="/leads/referral-links">
    Track partner-referred visitors automatically with unique referral links and first-party cookies.
  </Card>

  <Card title="Lead Forms" icon="file-lines" href="/leads/lead-forms">
    Customize the lead submission form, share leads, and configure validation settings.
  </Card>

  <Card title="Deals Overview" icon="handshake" href="/deals/overview">
    Understand how leads progress into qualified deals and move through your pipeline.
  </Card>

  <Card title="Deal Registration" icon="pen-to-square" href="/deals/deal-registration">
    Configure what partners see and submit when registering a new deal.
  </Card>
</CardGroup>
