> 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-properties/collect-phone-number.md).

# Phone Number Collection

{% hint style="warning" %}
**Is the estimated send count not updating even after changing the campaign's target audience?**

Check whether users' phone numbers are being collected correctly.
{% endhint %}

{% hint style="info" %}
Phone number collection is required to send Kakao Messages and Text Messages.\
Below are several methods for collecting phone numbers.
{% endhint %}

## Collecting Phone Numbers via SDK

You can collect phone numbers of users who have signed up for your service using the Hackle Client SDK.

## Collecting Phone Numbers via HTTP API

In addition to the Client SDK, you can also collect phone numbers using the HTTP API.

e.g.) When phone numbers need to be collected or updated server-side, such as in an admin interface.

## Collecting Phone Numbers via Import

You can import phone numbers for all users who signed up before your SDK/API integration in a single batch.

For details, refer to the CSV example below and send the file you want to import to the [Hackle team](mailto:support@hackle.io).

### CSV Example

User ID and phone number are required fields. Other information can be requested as needed.

For details, please contact the Hackle team.

| User ID        | Phone Number | Marketing Subscription Consent (Optional) |
| -------------- | ------------ | ----------------------------------------- |
| hackle\_richie | 01012345678  | 1                                         |
| hackle\_limo   | 01098765432  | 0                                         |


---

# 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-properties/collect-phone-number.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.