> 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/placeholders-on-emails.md).
# Placeholders on Emails
## Overview
Rechat has the ability to send two kind of emails:
* Marketing Emails
* Transactional Emails
If you send a marketing email to 10 people, and use `Hi {{recipient.first_name}}` , each of the recipients will receive a personalized email with their name:
```
┌──────────────────┐ ┌──────────────────┐ ┌──────────────────┐
│ Hi Jane, │ │ Hi John, │ │ Hi Sarah, │
└──────────────────┘ └──────────────────┘ └──────────────────┘
↓ ↓ ↓
jane.doe@example.com john.doe@example.com sarah@example.com
```
However, when you send a transactional email, you are sending 1 single email, with the same copy, to 10 different email addresses. Email protocol doesn't allow one email, sent to different recipients, to have different content.
```
┌─────────────────────────────────┐
│ Hi Jane, │
└─────────────────────────────────┘
│
├──────→ jane.doe@example.com
├──────→ john.doe@example.com
└──────→ sarah@example.com
```
If we wanted to allow full placeholder capability on transactional emails, we essentially would've had to disable sending an email to multiple recipients (Multiple `to`, `cc`), because they all require the same email to be sent to multiple people.
#### How do I know what type of email I'm sending?
When sending your email, if you see the option to use `To` or `Cc`, that means it's going to be a transactional email.
Transactional email
However, if you don't have the option to use `Cc` and all recipients are `Locked in` as `bcc`, that effectively means you are sending a marketing email, which means we'll be sending multiple emails (one per recipient), but full placeholder functionality will work as expected.
Marketing email with only Bcc recipients.
---
# 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://help.rechat.com/guides/crm/placeholders-on-emails.md?ask=&goal=
```
`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.