> For the complete documentation index, see [llms.txt](https://docs.daylite.app/help/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.daylite.app/help/getting-started/add-your-first-contact.md).

# Add Your First Contact

In Daylite, contacts come in two forms: **People** and **Companies**. Understanding the difference before you start adding records will save you a lot of reorganizing later.

**People** are the individuals you do business with — clients, leads, colleagues, referral sources. Their communication history, preferences, and activity all live on their Person record.

**Companies** are the organizations those people belong to. When you link a Person to a Company with a Role, Daylite keeps the relationship clear — so if a contact changes jobs, your history with the company stays intact and nothing gets lost.

A good rule of thumb: if you're thinking of a human, create a Person. If you're thinking of a business, firm, association, family, or group, create a Company. Most of the time, you'll create both and link them.

Once you have that foundation in place, adding your first contact takes just a few steps.

{% embed url="<https://www.youtube.com/watch?v=46awrwKN5Os>" %}

### Create Your First Contact

1. Click **People** in the sidebar.
2. Click **+ New Person**.<br>

   <figure><img src="https://3312841743-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FofiqhmWwdDTdbdewjbsf%2Fuploads%2FCHiRNuj1jSKiKUlHH7h2%2FCreate%20a%20Person.png?alt=media&amp;token=5084be0f-8cb1-490c-bbf2-3605afbe269d" alt=""><figcaption></figcaption></figure>

   <br>
3. Type in Their Name and details
4. Click **+Add Company** to add and link a new company to your contact
5. Type the name of the company and click **+ New Company**<br>

   <figure><img src="https://3312841743-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FofiqhmWwdDTdbdewjbsf%2Fuploads%2FMPs0P5xzl8pu9ftq9AP9%2FCreate%20Linked%20Company.png?alt=media&amp;token=8ddc6c13-c9aa-4af3-b397-1e7aaad3c1f1" alt=""><figcaption></figcaption></figure>
6. Click Save

That's it. You've just created your first records in Daylite!

<figure><img src="https://3312841743-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FofiqhmWwdDTdbdewjbsf%2Fuploads%2FjQQrQVo2BXujTJ9R3aBy%2FCreate%20Contact.png?alt=media&amp;token=31ab7e35-4b98-46af-9088-a560e4d0b067" alt=""><figcaption></figcaption></figure>

Over the next few steps, you'll link tasks, emails, and more to this Person and start to see how Daylite builds a complete picture of every relationship.

### Bring Your Contacts Into Daylite

You don't need to type everyone in by hand. Daylite can import contacts from Apple Contacts, Google Contacts, or a spreadsheet:

* Go to **File** > **Import** > **Import Contacts**
* Choose your source and follow the prompts

You can even assign a Category, like "Client" or "Prospect", during import to keep things organized from the start.<br>

**Learn more:** [Adding Your Contacts](https://docs.daylite.app/help/learn/getting-started/adding-contacts) — the full guide to importing from Apple Contacts, Google, vCard, and spreadsheets.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.daylite.app/help/getting-started/add-your-first-contact.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.