> For the complete documentation index, see [llms.txt](https://readme.dhee.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://readme.dhee.ai/platform-reference/test-and-deploy/deploy/google-rcs.md).

# Google RCS

Ready to make your chatbot a part of Google RCS? It's a fantastic way to reach more users and create engaging conversations. Here's how you can do it:

1. **Activate Google RCS**: Start by clicking the "Activate Google RCS" slider. This is the first step to bringing your chatbot to the Google RCS platform.
2. **Configure Google RCS**: Now, let's get your chatbot ready for Google RCS:
   * **RCS Client Token**: Enter the RCS Client Token for your chatbot.
   * **API Key**: Safely provide the API Key required for integration.
3. **Save Configuration**: Don't forget to save your Google RCS configuration settings to complete the integration.

With these steps, your chatbot will be seamlessly integrated with Google RCS, allowing you to reach a broader audience and deliver exceptional user experiences on this platform. Get ready to have meaningful conversations and provide valuable assistance to users on Google RCS!


---

# 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://readme.dhee.ai/platform-reference/test-and-deploy/deploy/google-rcs.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.