# Contacts

A **Contact** represents an individual your business has or is interacting with, that can be an individual person or a business/group.

Similar to other CRM a contact is based on a unique email address and phone number, you can expand a contact with more details such as names and addresses.

{% code title="GET /contact/{id}" lineNumbers="true" expandable="true" %}

```json
{
        "id": 47355,
        "emailAddress": "richardhull@example.com",
        "phoneNumber": "07837489814",
        "organisation": 3,
        "createdAt": "2025-12-19T21:03:25+00:00",
        "updatedAt": "2025-12-21T21:03:27+00:00",
        "referralInvites": [],
        "firstName": "Richard",
        "lastName": "Hull",
        "name": "Richard Hull",
        "timezone": "Europe/London",
        "totalSpend": 51000,
        "lastInteractedAt": "2025-12-21T21:03:25+00:00",
        "totalOrders": 1
    },
```

{% endcode %}

### Custom fields

**Custom fields** let you store arbitrary data that doesn't fit the standard contact properties — things like dietary preferences or an external system identifier for example. What custom fields make sense will vary with each business and these can often be setup at the start.

You can manage the custom fields via the admin dashboard or the API and populate the fields for the contact in the same ways.

[Read more about custom fields](/docs/concepts/contacts/custom-fields.md)

### **Activity**

**Activities** are the moments where the contact has interacted with your business, they've logged into the wifi, or made a purchase on your store for example. You can design automated workflows that are triggered by activities occuring to reward behaviour, send communication and more.

Its important that any interaction a contact makes is added, some activities will be automatically generated by the Glu platform and any enabled third-party integrations we've supported such as Shopify, Mews, Lightspeed and more.

[Read the full guide on adding activities.](/docs/use-cases/add-an-activity-to-a-contact.md)


---

# Agent Instructions: 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:

```
GET https://glu.gitbook.io/docs/concepts/contacts.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.