Sinch Community

If your inbound messages have stopped working, we recommend you first review the information in the following article: Why don't I get inbound messages from KakaoTalk users?    If the issue persists, you may have recently modified the KakaoTalk channel configuration for the corresponding Conversation API app. To review your KakaoTalk channel configuration:   Navigate to your list of apps in the  Conversation API section of the Sinch Customer Dashboard. Select the app on which the KakaoTalk channel is configured. Note: If you have deleted the Conversation API app that was previously functioning, you must contact Sinch customer support for help. Navigate to the KakaoTalk channel configuration. Examine the Enable Chat option: If the Enable Chat option is deactivated, you must toggle it in order to reactivate the chat function. The Sinch Developer Documentation site contains comprehensive documentation and tutorials that demonstrate how we support KakaoTalk using the Sinch Conversation API. ... View more

KakaoTalk channel has three BizMessage types: AlimTalk, FriendTalk and ConsultationTalk.  AlimTalk and FriendTalk do not accept sending media message using the GIF format while ConsultationTalk does support  GIF files as long as they are less than 5MB in size.   Sending an animated GIF is a little tricky as the animation will only start when the user opens the image in full. No animation will be shown in the chat window.   The KakaoTalk documentation contains more information about media messages. ... View more

It is important that your media file complies with the KakaoTalk's criteria, which is defined  in the Media Messages section of our KakaoTalk developer documentation: Media included in the Media message will be rejected by the channel if: the width is below 500px, or if the 'width:length' ratio is below 2:1, or above 3:4 or if the image dimension is not equal to [800px * 600px] image file format is different than JPG or PNG file size is bigger than 500KB or for image with dimension [800px * 600px] is bigger than 2MB. Double check your image and make sure it's in the right format before resending your FriendTalk message.  Here are few examples you can use:  500x1000 px, 500x800 px, 500x500 px, 500x400 px 600x1200 px, 600x960 px, 600x450 px 720x720 px (Recommended!) 800x600px (wide image) The Sinch Developer Documentation site contains comprehensive documentation that illustrates how Sinch supports KakaoTalk through the Conversation API. ... View more

AlimTalk is a KakaoTalk channel-specified template message and it requires approval by KakaoTalk. FriendTalk is a marketing message and you don't need KakaoTalk approval for this message type.   When sending an AlimTalk message, you need to specify the template id, recipient, and the set of parameters that you may have defined in the template relevant for the recipient. Here is an example of an AlimTalk template: Template id : package_template Template description: A package #{package_id} has been scheduled to be delivered to you. The expected delivery time is #{expected_delivery}   The following code snippet provides an example of a JSON payload to send package_template to a KakaoTalk user: { "message": { "template_message": { "channel_template": { "KAKAOTALK": { "template_id": "package_template", "parameters": { "package_id": "PACKAGE123", "expected_delivery": "7th June 9:00" } } } } } }   When sending a FriendTalk message, you can send it as a generic message type provided by Conversation API.    It is also possible to create an omni-channel template using the Conversation API's Message Composer or using the Template Management API. The omni-channel templates can be used with any Conversation API channels as it will automatically transcode to the format required by the sent channel.    The Sinch Developer Documentation site contains comprehensive documentation that illustrates how Sinch supports KakaoTalk through the Conversation API. ... View more

When you receive a delivery receipt with a FAILED status for an AlimTalk or a FriendTalk message, then you will not be charged for the FAILED message(s).   For a KakaoTalk chat, it depends if have previously replied successfully. If you have replied successfully before then a session fee will be charged regardless if the subsequent messages FAILED to deliver. If problem persists, you can contact support@sinch.com for help.   You can learn more about receiving delivery receipts on the Sinch Developer Documentation site. There, you'll find comprehensive documentation that illustrates how Sinch supports KakaoTalk through the Conversation API. ... View more

KakaoTalk only provides information on whether message delivered succeeded or failed. It does not provide any additional information, such as a read receipt or button action event. You can learn more about receiving delivery receipts on the Sinch Developer Documentation site. There, you'll find comprehensive documentation that illustrates how Sinch supports KakaoTalk through the Conversation API. ... View more

When setting up the KakaoTalk channel of the Conversation API, it's possible for Sinch customers to configure their solution to send only AlimTalk and FriendTalk messages. These are outbound messages only.   Inbound KakaoTalk messages are delivered as ConsultationTalk messages. ConsultationTalk message support can be added to your KakaoTalk channel configuration as required. When ConsultationTalk message support is enabled for your solution, the chat service in the KakaoTalk Channel Manager will be disabled, and all inbound ConsultationTalk messages will be delivered directly to the customer's webhook via the Conversation API. You will be unable to see the chat history in the KakaoTalk Channel Manager.   Make sure that the 1:1 chatting is enabled on your KakaoTalk Channel Manager. You can do on the dashboard and toggle ON.   Note: For information on how to add a webhook to a Conversation API app, see this article.   The Sinch Developer Documentation site contains comprehensive documentation that illustrates how Sinch supports KakaoTalk through the Conversation API. ... View more

The KakaoTalk BizMessage functionality allows businesses to send outbound messages (AlimTalk and FriendTalk) using their KakaoTalk phone number. Both types of messages can be sent using the KakaoTalk channel of the Conversation API, and doing so creates a contact with a specific channel identity.   Businesses can also receive messages (ConsultationTalk) from a KakaoTalk user. When using the KakaoTalk channel of the Conversation API, KakaoTalk sends the user's message and an ID to the Conversation API. The ID is unique to the channel, and is used to create a new contact. Even if the user sending the ConsultationTalk message is responding to an AlimTalk or FriendTalk message, the unique ID created by the ConsultationTalk message is neither the existing user's original channel identity, nor the existing user's phone number. Essentially, an entirely new contact is created when you receive the ConsultationTalk message.   Therefore, the Conversation API does not automatically merge these two contacts together, as they have separate (and unrelated) channel identities. In order to merge the contacts to get a full conversation history (or to configure the contact to send AlimTalk or FriendTalk messages to later), businesses must request the KakaoTalk user directly for their phone number and verify it independently. Then, they can use that information to merge the two contacts.   The Sinch Developer Documentation site contains comprehensive documentation that illustrates how Sinch supports KakaoTalk through the Conversation API. ... View more

ConsultationTalk or KakaoTalk Chat messages are messages sent and received during a chat session that is initiated by KakaoTalk end-users. When the user has initiated a chat session with a business, all messages sent and received during the session are ConsultationTalk messages. The chat session can be closed by the user at any time, and will be automatically closed if the user has not replied for 30 days.   Note: If there is no open ConsultationTalk chat session, businesses are unable to send ConsultationTalk messages to the user. To send a message to a user outside of a ConsultationTalk session, the business must send an AlimTalk message or a FriendTalk message to the user's phone number, depending on the circumstance and reason for contact.   An end-user can start a ConsultationTalk chat session as a guest from a business' channel profile page. Alternatively, if the user is already a friend of the channel, they can message the business from their contact list. They can also initiate a chat session by responding to an AlimTalk or FriendTalk message.   When sending ConsultationTalk messages, businesses can send any of the generic Conversation API message types, including text, media, choice, card, carousel, and location messages. Businesses do not need to use approved templates to send ConsultationTalk messages.   For more information, see the Sinch Developer Documentation site. There, you'll find comprehensive documentation that illustrate how Sinch supports KakaoTalk through the Conversation API. ... View more

In some cases, KakaoTalk may set your business' phone number to inactive, depending on your location and the level of activity associated with your account.   For example, if you are still in the process of configuring a KakaoTalk channel, and your business is located outside of South Korea, you may not be actively using KakaoTalk on a daily basis. If so, KakaoTalk may set the phone number associated with your account to inactive. Then, when attempting to send an AlimTalk message, you may receive an error with a reason like the one below:   CHANNEL_REJECT : The underlying channel reported: 3018: Unable to send messages (invalid or broken KakaoTalk user)   To address this, simply log on to your business' account and use the KakaoTalk app for a while. Then, KakaoTalk will reactivate your account. To ensure the system is properly synchronized, try sending a new message one day after your account is reactivated.   The Sinch Developer Documentation site contains comprehensive documentation that illustrates how Sinch supports KakaoTalk through the Conversation API. ... View more

You can use omni-channel templates to send FriendTalk or ConsultationTalk messages on the KakaoTalk channel of the Conversation API. In either scenario, the template being used does not need to be approved by KakaoTalk.   Note: Approved templates are only required when sending AlimTalk messages.   You can create omni-channel templates using the Conversation API's Message Composer or using the Template Management API.   You can learn more about working with templates on the Sinch Developer Documentation site. There, you'll find comprehensive documentation that illustrates how Sinch supports KakaoTalk through the Conversation API. ... View more

During development, it's best to have a developer channel to test rather than using the WeChat Official account in production. For every WeChat account, you can create one developer channel. This is a guide to show you how to create a developer channel for test. Step 1: Log into WeChat Official Account Platform and go to Developer Tool and Official Accounts Platform Testing Account.   Step 2: Enter the appID and appsecret as Developer ID and Developer Password on the Conversation API dashboard - channel setup for WeChat.  Sinch Dashboard - WeChat channel setup Step 3: Create a token and add to WeChat Official Account Platform and Sinch dashboard. Enter "optional" to AESKey as developer test account does not support this. Step 4: Click "Save" on Conversation API dashboard - channel setup for WeChat. Copy the Callback URL and paste it to WeChat Official Account Platform.   Now the WeChat developer channel is setup, you will find the QR code further down on the Official Accounts Platform Testing Account page. Scan the QR code using your WeChat app on your mobile device, add as a friend then send a message from the WeChat app to the Conversation API to start testing.   The Sinch Developer Documentation site contains comprehensive documentation and tutorials, which show you how we support WeChat through the Sinch Conversation API.     ... View more