> For the complete documentation index, see [llms.txt](https://squarebox-ai.gitbook.io/squarebox/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://squarebox-ai.gitbook.io/squarebox/chat/chat-search.md).

# Chat search

## Chat Search Feature

The **Chat Search** feature in Squarebox is designed to help users efficiently navigate large volumes of customer conversations. Whether you're managing support, sales, or follow-ups, this feature ensures you can find the exact chat you need — instantly.

***

### Overview

Positioned prominently at the top of the **Chats** interface, the search bar allows team members to quickly retrieve any ongoing or past WhatsApp conversation.

This improves:

* Response speed
* Accountability
* Overall operational efficiency

***

### What You Can Search

You can search for chats using the following identifiers:

* **Lead Name** – Locate conversations by typing the lead’s name (e.g., `Sai Prakash`)
* **Phone Number** – Search using the contact’s registered mobile number (partial or full)
* **Message Content** – Search for keywords or phrases from messages (e.g., `Pay now`, `Admission`, `Site visit`)

As you type, Squarebox auto-filters the results in real time, showing all chats that match your input.

***

### Practical Use Cases

* **Sales Follow-up**\
  Search `brochure` to find all leads who were sent course materials.
* **Payment Recovery**\
  Search `Pay now` to locate leads who received payment links.
* **Support Reference**\
  Search by name or keywords like `reschedule` to revisit past issues.
* **Unread Conversation Shortcut**\
  If you remember a lead’s name but haven’t opened their chat, search for the name to respond quickly.

***

### Benefits

* Saves time compared to manual scrolling
* Reduces missed follow-ups or repeated messages
* Enables faster context switching between conversations
* Ideal for teams handling a high volume of leads or chats daily.

<figure><img src="/files/T33boFAJ2ERhLP9RsZUf" alt=""><figcaption></figcaption></figure>
