# 3. Search for a Conversation

Users can search for a Conversation by entering a friend's first name, last name, or full name into either the `Input Search Conversation (Desktop)` element or `Input Search Conversations (inside Floating Group - View Conversations)` element. 

![](/files/-LXOAgzmsu1Yr8_S-mkO)

![](/files/-LXOAlM58nkBe0SZ0PUv)

When either of those inputs are not empty, the `Repeating Group Conversations (Desktop)` or `Repeating Group Conversations (Mobile)` elements will only display the Conversations whose "participating Users" field (type: User, list: yes) contains Users with the searched for name.  This is accomplished by using the conditional statements (below) which change the data source of the repeating groups when either of the inputs are not empty:

**Desktop**

![](/files/-LXOClUt-hP018hRz43Q)

**Mobile**

![](/files/-LXOCOP4JmAEeD4SJc9i)

Bubble's search functionality is case-sensitive in this scenario, which we don't want here.  For example, if a User types "lauren" into either of the search inputs, Bubble would only return Users with the name of "lauren" not "Lauren".  The workaround used in the template uses two hidden inputs:

1\. `Input Lowercase (Input Search Conversation (Desktop)`

![](/files/-LXOF6IhS0QLIlCudQ7S)

2\. `Input Lowercase (Input Search Conversation (Mobile)` 

![](/files/-LXOF9a_sHm_BkcIYfCx)

These hidden inputs' initial contents are the Input Search (Desktop) and `Input Search Conversations (inside Floating Group - View Conversations)`elements' values, set to **:lowercase**. This way, the advanced constraints in the Repeating Group Conversations elements take the lowercase values of the Users' names and compares them with the lowercase value of what the Current User typed into the Search inputs. This returns all Users with the matching names regardless of whether the input value is capitalized or not:

**Desktop**

![](/files/-LXOOQg9neToS_zmMOCh)

**Mobile**

![](/files/-LXOOrO98a7u11RCnd88)


---

# 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://docs.littlebaytech.com/templates/messaging-template/page-guides/pages/3.-logged-in/messages/built-in-functionality/3.-search-for-a-conversation.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.