> 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/guides/crm/testimonials/using-testimonials-in-marketing.md).

# Using Testimonials in Marketing

Learn how to incorporate testimonials into your marketing materials to build trust and showcase client success stories.

{% embed url="<https://rechatq.wistia.com/s/02e94vwbhcfqovi>" %}

### Overview

Testimonials can be added directly to marketing assets throughout Rechat.

Common use cases include:

* Email campaigns
* Agent websites
* Listing websites
* Presentations
* CMAs

### Add Testimonials to an Email

#### Desktop

1. Open an email template
2. Open the **Basics** section
3. Drag the **Testimonials** block into your design
4. Select one or more testimonials
5. Click **Next**
6. Save your changes

<figure><img src="https://1031368632-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MJZySovZjoLVT1XAonI%2Fuploads%2FDK8Fdri17aKl1Fk16t1c%2F2026-06-10_09-55-47.png?alt=media&amp;token=6ea39ace-69ba-4703-9dca-d68ca237b666" alt=""><figcaption></figcaption></figure>

### Choosing the Right Testimonials

Match testimonials to your audience whenever possible.

#### Examples

**Presentations (CMA)**\
Use testimonials from past sellers.

**Buyer Campaign**\
Use testimonials from buyers.

**Luxury Marketing**\
Use testimonials from luxury clients.

**Relocation Marketing**\
Use testimonials from relocation clients.

### Best Practices

#### Build a Variety of Testimonials

Try to collect testimonials from:

* Buyers
* Sellers
* Investors
* Relocation clients
* Luxury clients
* First-time buyers

#### Use Testimonials Regularly

Don't collect testimonials just to store them. Feature them throughout your marketing to reinforce credibility and demonstrate your experience.


---

# 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/guides/crm/testimonials/using-testimonials-in-marketing.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.