> For the complete documentation index, see [llms.txt](https://help.rechat.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.rechat.com/whats-new/refreshed-contact-cards.md).

# Refreshed Contact Cards

Your contacts are your most valuable asset, that’s why Rechat has made it even easier to view the important information that matters the most to you.

{% embed url="<https://rechatq.wistia.com/medias/ackbqw3466>" %}

Contacts have been separated into four (4) key contact tabs, each providing key data.&#x20;

{% tabs %}
{% tab title="Details" %}
**Contact Card**: Name, Tags, Primary Contact Information, Social Buttons, Auto-Touch Reminder, Quick Action Buttons for Reminders and Notes

**Relationship:** Last Touch, Auto-Reminder

**Contact Info:** First Name, Middle Name, Last Name, Contact Information, Social Links

**Flows:** This will show you any Flow your contact is currently enrolled in

**Touch Dates:** Birthday, Home Anniversary, Wedding Anniversary, Work Anniversary, Children's Birthdays

**Addresses:** Primary Address, Investment Properties, Work Addresses, etc.

**Deals:** Any Deal this contact is associated with

**Details**: Title, Nickname, Job Title, Company, Marketing Name

**Spouse/Partner**: First Name, Last Name, Email, Phone, Birthday

**Assignee:** Indicates if/when the contact/lead has been assigned to a team member
{% endtab %}

{% tab title="Upcoming" %}
Auto-Reminders, upcoming calendar events and upcoming celebrations.
{% endtab %}

{% tab title="History" %}
Any historic emails, logged calls and text messages, celebrations and calendar events.
{% endtab %}

{% tab title="Notes" %}
Any and all notes you've entered into the contact records.&#x20;

{% hint style="info" %}
**Pro-Tip:** Notes are searchable! Be as detailed as possible so you can reference notes later on.
{% endhint %}
{% endtab %}
{% endtabs %}


---

# 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.rechat.com/whats-new/refreshed-contact-cards.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.