> 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/social-post-building-blocks.md).

# Social Post Building Blocks

Adding headshots, phone numbers, team logos and more to social posts is important, that's why we introduced building blocks to social posts!

Sharing social media posts across various platforms increases your visibility and reach, ensuring your content connects with a broader audience. It also helps maintain consistent branding, which builds trust and recognition, and enhances engagement, leading to more leads and sales opportunities.

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

Rechat has introduced **Building Blocks** into social media posts. **Building Blocks** include:

* **Headline 1**
* **Headline 2**
* **Text**
* **Image**

Simply drop a building block onto your social post and customize away with items like a **headshot, team logo, phone number, email address, caption and more!**


---

# 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/social-post-building-blocks.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.