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

# RGO Social Layer

The Social Layer enables secure, real-time communication between issuers and users entirely inside RGO.

It provides a unified environment where discovery, engagement, and conversation happen without relying on external platforms.

### &#x20;Communication Tools

RGO supports multiple formats of communication designed for both everyday interaction and more intensive project needs:

* Encrypted Text Messaging

  End-to-end encrypted chat for basic updates, FQA, and routine issuer–user communication.
* High-Quality Voice & Video Calls

  Suitable for hosting small AMAs, quick announcements, partner discussions, or private KOL conversations.

These tools give issuers flexibility to address community questions, clarify information, and maintain ongoing dialogue.

### Platform-Native Integration

Communication is built directly into the RGO interface, ensuring smooth transitions from platform activity to direct interaction:

* Chat entry points appear on issuer profiles, asset pages, and short-form video content.

  Users can move from browsing to engaging in a single step.
* Wallet-linked identities keep communication accountable and reduce anonymous spam, while still maintaining ease of use.
* Internal messaging reduces dependence on Telegram or Discord, helping issuers manage their audience in a controlled, consistent environment.

**The Social Layer keeps the entire lifecycle—discover → engage → communicate—in one place.**

It strengthens trust, simplifies collaboration, and makes RGO a more connected ecosystem for both issuers and users.


---

# 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://rgo.gitbook.io/rgo/platform-modules/rgo-social-layer.md?ask=<question>&goal=<endgoal>
```

`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.
