> For the complete documentation index, see [llms.txt](https://docs.hackle.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hackle.io/en/crm-marketing/push-message-guide/recommended-templates.md).

# Push Message Recommended Templates

If you're not sure where to start with push message CRM Marketing, try using the recommended templates. We'll show you examples you can use across various customer journey stages.

![](https://143363954-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FyAVlNQhS253reum0Ce94%2Fuploads%2Fgit-blob-64aae767f0ea1fd8a95184a23b037aee526c0c43%2F68f484b-Frame_427319022_ef463a0b09503834.jpg?alt=media)

Using Hackle's cohort and targeting features, you can send personalized messages and run **customized campaigns** for each customer.

Rather than sending the same message to all customers at the same time, automatically deliver messages personalized for each individual customer at the optimal time.\
Customized campaigns provide a better customer experience while also increasing push open rates.

Customized campaigns require collecting customer behavioral data. By leveraging customer data, you can understand their interests and preferences, and send personalized messages based on that data. Use the templates below to create cohorts suited to your purpose and send personalized messages to 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.hackle.io/en/crm-marketing/push-message-guide/recommended-templates.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.
