Send Kakao Messages

KakaoTalk Channel Integration and credit top-up are required before sending Kakao Messages.

• If you have not yet completed the integration, please refer to the KakaoTalk Channel Integration Guide.

• To top up your credits, please contact the Hackle team at [e-mail].

Send Settings

Once you have finished composing your message, you can configure the details needed to send the message in the Send Settings step.

Step 1. Recipients

Phone number upload is required for Kakao Message delivery. For the initial upload, please contact the Hackle team ([e-mail]).

1-1. Audience Selection

• All Users

• Cohort

  • You can specify a cohort as the campaign audience for targeting. Use various events and properties to configure the cohort you want.

1-2. Detailed Conditions

You can configure detailed send settings based on the recipient's marketing subscription consent status.

Brand Message Settings

Brand Messages can only be sent to customers who have consented to receive Kakao Messages.

For detailed differences between conditions and how to use them, refer to the Brand Message Recipient Targeting documentation.

Step 2. Send Type Selection

Hackle provides three send types. Select a send type according to the nature of the message.

Send Type	Description
Schedule-based Send	Send messages at your desired date and time.
Event-based Send	Send messages when a user performs a specific action. Sent based on user behavior data.
API-based Send	Send messages based on the API configuration you set. Messages are sent when the internal server requests the send.

2-1. Schedule-based Send

Immediate Send

Send messages to users immediately.

Suitable for urgent announcements or updates about an ongoing event.

After configuring the send settings, it may take a few minutes for the message to actually be delivered to users.

Immediate Send

• Promotional Time Restriction

  • Kakao Friendtalk messages can only be sent between 08:00 and 20:50 Korea time. Messages set outside this window may not be delivered, so please be aware.

• Rate Limit

  • You can set the maximum number of messages to be sent at once in per-minute intervals to prevent service traffic overload.

  • Note that setting the per-minute send count too low may delay message delivery.

Scheduled Send

Schedule messages to be sent to cohort users at a desired time. You can configure the desired timezone.

When the scheduled time arrives, it may take a few minutes for the message to actually be delivered to users.

Scheduled Send

2-2. Event-based Send

Trigger message sends based on when a specific event occurs. You can build campaigns tailored to the customer journey.

When an event occurs, it may take a few minutes for the message to actually be delivered to users.

Event-based Send

• Trigger Event

  • Select the desired event.

  • You can add property filters or configure multiple events with OR conditions.

• Wait Time

  • You can send a push message immediately after the event occurs or after a desired wait period. Example: Send "Check the items in your cart!" 3 days after the [Add to Cart] event occurs.

  • You can cancel the message send if the user triggers a specific event during the wait time. Example: Send "We have a coupon for first-time buyers!" to users who have not yet purchased, 3 hours after the [Sign Up] event. If the user triggers the [Purchase] event during the wait time (3 hours), the message is not sent.

• Send Period

  • Start: Set the start date and time for sending.

  • End

    • No end: No end date is specified. In this case, end the campaign manually.

    • Send until a specific date: Set a desired end date.

• Send Time Restriction

  • Messages will not be sent during the configured time window. For promotional messages, late-night sending (8:50 PM - 8 AM) requires separate 'late-night receive consent'.

  • You can configure separately whether messages not sent during the restricted time should be resent.

2-3. API-based Send

With API-based Send, you can maximize users' push open rates by sending personalized messages at the most appropriate moment.

Messages can be sent at the moment the internal server requests a send, and this can be used for automated message sending triggered by changes in internal server data.

API-based Send

Retrieve your API key and include it in the header when making API calls.

The Hackle Dashboard provides code snippets for API-based sends.

For what to check when actually sending the API, refer to the Kakao Message Send documentation.

Step 3. Customer Fatigue Management

Excessive push notifications can become a burden and nuisance to customers, and may cause them to leave the service. If you are sending multiple push messages, use customer fatigue management to set the number and frequency of messages sent to a specific customer within a given period.

3-1. Duplicate Send

• By default, the same campaign is sent to the same user only once.

• If you want to send duplicates, you can set the period — in minutes, hours, days, weeks, or months — before the message is resent after the initial send, to minimize negative customer experiences.

3-2. Frequency Capping

• You can limit the total number of CRM messages (Push Messages, Kakao Messages, SMS, Webhooks) that an individual user can receive within a given period. (*Based on message send start time)

• The total Frequency Capping can be configured at the workspace level, and you can choose whether to apply the limit per message campaign.

• This can be configured under Frequency Capping Settings in the CRM message list on the Hackle Dashboard.

Push Settings > Frequency Capping

• Click the Frequency Capping Settings button to set the send frequency limit in minutes, hours, days, weeks, or months.

• If no value is set, no frequency capping is applied. When frequency capping is configured, the same settings apply to all push messages with frequency capping enabled within the workspace.

• For more details about message Frequency Capping, check here.

Step 4. Send Details

You can view the estimated send count based on the selected audience and send type.

• Schedule-based: Send count per cycle

• Event-based: Number of trigger event occurrences in the past 1 day

This is estimated data and actual credit deductions and send counts may differ.

Please verify your credit balance before sending.

Step 5. Sending

5-1. Start Sending

Once all settings are complete, click the [Save] button in the upper right to save the settings, or start the campaign immediately.

• Start: Immediate Send: Messages are sent immediately upon start. Scheduled Send: The message schedule is activated upon start.

• Save: After saving, the message send only begins when you click the [Start] button on the detail screen.

5-2. Statistics

When the campaign starts, a campaign statistics area appears at the top. Statistics data is updated every hour.

For Kakao Messages, click data cannot yet be collected, so send success rates are provided.

In progress

To cancel a scheduled send, click the deactivate button to modify.

To stop a campaign, click the End button to end the campaign.

• Real-time Send Status: Check the event status in Event Explorer to confirm messages are being delivered to users right after launch.

• Detailed Performance Analysis: You can analyze campaign results in detail using Funnel Analysis. Configure the user journey after message viewing to see how many users who responded to the message completed subsequent actions.

• Message Send Count and Amount: Check at [Settings > Credit Top-up > Usage History].