> 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/crm-faq.md).

# CRM Campaign FAQ

Frequently asked questions about In-App Messages, Push Messages, and Kakao Messages.

Frequently asked questions about configuring and sending messages in Hackle CRM campaigns.

#### Can an In-App Message open an external web page from the app?

By default, it opens in the device's browser. You can open it inside the app by using an in-app WebView scheme.

If you enter a web link URL in the click action or in a button, it opens in the default browser such as Safari or Chrome.\
If you have implemented a WebView scheme in your app, enter that scheme in the URL.

***

#### How often is In-App Message and Push Message performance updated?

It is updated every hour.

You can check performance at the top of the detail page. For a more detailed breakdown, use Data Analytics.

***

#### Can In-App Message content be personalized?

If you use In-App Message HTML, you can personalize the content at the moment the message is shown.

***

#### How is the estimated send volume for Kakao Friendtalk, Alimtalk, and Brand Message calculated?

It is calculated based on the number of users whose phone numbers have been collected in Hackle. The actual send volume can differ depending on factors such as whether the user has added your Kakao Channel.

Hackle does not collect whether a user is a Kakao Channel friend or whether the user has blocked Alimtalk.\
The estimated send volume is based on the number of target users whose phone numbers have been collected.

{% hint style="info" %}
An actual send can fail for reasons such as the user not having added the Kakao Channel, having blocked Alimtalk, or not using KakaoTalk.\
Credits are deducted based on successful sends.
{% endhint %}


---

# 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://docs.hackle.io/en/crm-marketing/crm-faq.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.