> For the complete documentation index, see [llms.txt](https://support.8seats.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.8seats.com/hints-and-tips/the-basics.md).
# The Basics
### Tap heads up & down
Simply tap the heads up and down to choose who you want included in the conversation. Every combination of people is a different conversation
### Swipe left & right to browse
You can browse through all of your conversations on a Table by swiping left and right. Your conversations are kept in order of how recency.
### Activity – your 8seats inbox
Activity shows your most recent messages, including conversations on all of your Tables, Rooms and DMs.
### Long hold to 'solo' someone
Need to talk to just one person? Simply long hold on their head to quickly jump into a conversation with only them.
### Search for messages
Quickly find the message you’re looking for by searching here.
### More message controls
Access extra options with a long hold on a message. You can copy the image or text, share the message or delete it if you make a mistake.
---
# 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://support.8seats.com/hints-and-tips/the-basics.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.
