> For the complete documentation index, see [llms.txt](https://developers.airship.co.uk/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developers.airship.co.uk/basics/contacts.md). # Contacts Working with contacts in Airship Contacts are the basis of all customer data in Airship. Contacts records can store all sorts of data such as contact information and personal details. A contact record can also have any number of transactional records attached to them to represent a contact's timeline of interactions. For example, Table Bookings, WiFi interactions, Feedback, Purchase History and more. ### Contact merging Airship automatically merges contact records together based on unique customer identifiers. These identifiers are `email` or `mobile_number`. In other words, if you write a contact to us with an email address or mobile that already exists as part of a contact on Airship, we'll automatically update and/or append the data you send to the pre-existing contact record. --- # 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://developers.airship.co.uk/basics/contacts.md?ask=&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.