> For the complete documentation index, see [llms.txt](https://help.paintscout.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.paintscout.com/support/contacts-and-companies/contacts-and-companies.md).

# Contacts & Companies

Create, manage, and export contacts and companies in PaintScout.

Contacts and companies keep customer records organized in PaintScout. A contact stores details for one person. A company groups related contacts under one business.

Both record types connect to estimates and invoices. With Operations, they also connect to deals, events, tasks, activity, notes, tags, and files.

Use this section to create records, manage linked customer information, and export your contact list when you need it outside PaintScout.

## In This Section

* [Create a Contact](/support/contacts-and-companies/contacts-and-companies/how-to-create-a-new-contact.md) — Create a contact and review linked estimates, invoices, activity, and Operations records
* [Create a Company](/support/contacts-and-companies/contacts-and-companies/how-to-create-a-new-company.md) — Create a company, associate contacts, and manage shared records, activity, and linked Operations data
* [Export Your Contact List](/support/contacts-and-companies/contacts-and-companies/how-to-export-your-contact-list.md) — Filter and export contacts to CSV for Excel, Google Sheets, Numbers, or other tools

  


---

# 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://help.paintscout.com/support/contacts-and-companies/contacts-and-companies.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.