> For the complete documentation index, see [llms.txt](https://docs.bluepro.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bluepro.ai/customers-and-sales/contacts-and-leads/contacts-leads-and-jobs-how-they-work.md).

# Contacts, Leads & Jobs: How They Work

Contacts, leads, and jobs are the backbone of BluePro. Once you understand how the three connect, everything else — scheduling, estimates, invoices, follow-up — falls into place. This guide explains what each one is, how they relate, and what you can do with them on both the web and the mobile app.

{% embed url="<https://app.trupeer.ai/view/Kxgi9zs2A/understanding-contacts-leads-and-jobs-in-blue-pro>" %}

### The Big Picture

* **A Contact is a person or business.** The long-lived record holding name, phone, email, address, and history. It sticks around forever.
* **A Lead is interest that isn't committed yet.** They've shown interest but haven't approved work. Leads are where you focus follow-up.
* **A Job is committed, scheduled work.** The customer scheduled an appointment, accepted an estimate, or gave the go-ahead.

**Key relationship:** one contact can have many leads and jobs over time.

{% hint style="success" %}
**Leads turn into jobs automatically.** BluePro moves a lead into a job on its own when the customer **accepts an estimate**, **makes a payment**, or you record that they **approved the work**.
{% endhint %}

### Working With Contacts

A contact holds name, phone, email, property addresses, **residential/commercial** type, lead source, labels, communication preferences, card on file, and full history.

#### On the web

The **Contact Directory** is your full customer list — each row shows phone, email, address, open tasks, active jobs, and last activity.

![](/files/NAc6gzwnb8RroPPpAjIq)

Open any contact for the full detail view: info, labels, properties & access instructions, appointments, recent calls (with recordings), an AI conversation summary, and a messaging panel.

![](/files/vDu5k1ifM6WKyGVBapd0)

From a contact you can: **Call or message**, **start a job/estimate/invoice**, **edit** details and **labels**, **assign a preferred technician**, **manage addresses**, and **review history**.

#### On mobile

Those in the field will have all the same information available to them from the mobile app. They can add notes and photos, send documents to the client, look up previous invoices, etc.

{% columns %}
{% column %}
![](/files/j5v9w4u9F0YeVDVs1m1d)
{% endcolumn %}

{% column %}
![](/files/dfFkaK2sufwyOg9ck7tR)
{% endcolumn %}
{% endcolumns %}

### Working With Leads & Jobs

Leads and jobs are the same record at different points in their life, moving through **stages** — first a **lead pipeline**, then a **job pipeline** once the customer commits.

#### Three ways to view your work

Start in **Follow-Up** each day. Use **Pipeline** to manage stage movement. Use **List** for sorting and bulk review.

<table><thead><tr><th width="218">View</th><th width="488">Best for</th></tr></thead><tbody><tr><td><strong>Follow-Up (Suggested)</strong></td><td>A prioritized list of who to contact next, with a recommended action and urgency badge. Start here daily.</td></tr><tr><td><strong>Pipeline</strong></td><td>A visual board with a column per stage. Drag a card, or watch cards advance as you work.</td></tr><tr><td><strong>List</strong></td><td>A sortable table (source, owner, status, value). Best for bulk review.</td></tr></tbody></table>

<figure><img src="/files/0tFhBIhOzWFGlrWMcavE" alt=""><figcaption></figcaption></figure>

<figure><img src="/files/LBgSSuxAsNxHFm8U2smb" alt=""><figcaption></figcaption></figure>

<figure><img src="/files/BNZMRYp1kVCntrf2uWLK" alt=""><figcaption></figcaption></figure>

#### What the stages mean

Pipelines are customizable, but most teams start with:

* **Lead pipeline:** New Leads → Lead Appt Booked → Needs Estimate → Estimate Sent, plus **Not Interested**.
* **Job pipeline:** Needs Appointment → Service Scheduled → Needs Invoice → Invoicing → Completed, plus **Not Interested**.

You rarely move cards by hand — booking, estimating, completing work, and collecting payment advance them for you.

#### On mobile

Same three views under the work tabs — **Jobs, Leads, Estimates, Invoices.** Follow-Up cards show the customer, wait time, urgency badge, recommended next step, and one-tap **Call** / **Send Text**.

> 📸 **IMAGE —** Mobile Lead Follow-Up card with urgency badge and Call / Send Text.

<figure><img src="/files/aRpCLJzT9GznEhUnuxsz" alt="" width="375"><figcaption></figcaption></figure>

### Finding the Right People

From the Contacts (or Leads) list, filter by **Labels**, **Job Tags**, **Lead Sources** (has / doesn't have), and **Dates** (created, last activity, last appointment).

Then select people and use **bulk actions** to **Add Labels** or **Add to Audience**.

<figure><img src="/files/QalcBpLL2Y84XizAeBAi" alt=""><figcaption></figcaption></figure>

> 💡 **Tip — Label as you go.** Labels like *VIP* or *Maintenance Plan* make future filtering effortless and power marketing audiences.

### FAQ

* **Is a "job" separate from a "lead"?** Same record, different stage; it converts automatically.
* **Multiple jobs per customer?** Yes, any number.
* **Move cards myself?** Normal actions do it for you; you *can* drag manually.
* **Contact Label vs. Job Tag?** Labels describe the person; tags describe the work.
* **Field note visible to office?** Yes — syncs instantly.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.bluepro.ai/customers-and-sales/contacts-and-leads/contacts-leads-and-jobs-how-they-work.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.