> For the complete documentation index, see [llms.txt](https://docs.bird.com/connectivity-platform/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bird.com/connectivity-platform/managing-inbox-contacts/add-a-contact-via-a-ticket.md).
# Add a contact via a ticket
All Owners, Admins and Agents can add a contact to Inbox via an incoming ticket.
1. When a new ticket arrives in Inbox from a customer who isn't in the system, their contact details will be empty. In the details panel on the right-hand side of your screen, click the **Edit** icon, then click **Edit contact**.
2. Fill in the form with the contact's First name and Last name.
3. Add a Profile name, which can be the contact's real name or a nickname/screenname. This will be visible to both the agent and the contact when chatting.
4. Click **+ Add channel identifier**, then select **Email address** and/or **Phone number** from the **Type** drop-down menu and enter the relevant information in the **Identifier** field.
5. Click **Save** next to each identifier that you've added.
6. \[Optional] Under **Extra info**, click **+Add attribute** and enter any additional information about your contact.
7. Click **Save** next to each identifier that you've added.
8. Click **Confirm** to add your new contact to Inbox!
---
# 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.bird.com/connectivity-platform/managing-inbox-contacts/add-a-contact-via-a-ticket.md?ask=&goal=
```
`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.