Connect KakaoTalk Business

KakaoTalk is the leading messaging app in South Korea. Unlike most channels, KakaoTalk Business doesn't connect directly — you contract a local BSP (Business Service Provider), typically Bizm, Infobank, or NHN Toast, which sits between Omnifox and Kakao to send Alimtalk (notifications) and Friendtalk (promotional messages).

Requirements

• An active contract with a Korean BSP (Omnifox defaults to Bizm, but also supports Infobank and NHN Toast)
• A Kakao Plus Channel (branded channel) registered with that BSP
• An API Key and Sender Key issued by the BSP

Steps to connect

1. Contract a BSP and register your Plus Channel — the BSP gives you an API Key and Sender Key.
2. In Omnifox, go to Channels → Connect New Channel and pick KakaoTalk Business.
3. Select your BSP Provider (Bizm, Infobank, NHN Toast, or Custom for anything else). The Base URL auto-fills unless you pick Custom.
4. Paste your Plus Channel's API Key and Sender Key.
5. Optionally fill in the public Plus Friend ID and a template prefix (e.g., OMFX_) to identify your Alimtalk templates.
6. Save, then point your BSP's callback configuration to the webhook URL Omnifox shows you.

Configuration

• BSP Provider / Base URL: sets the API host (api.bizmsg.kr, omni.ibapi.kr, api-alimtalk.cloud.toast.com, or your own).
• API Key: for Bizm this accepts the userid:apikey format or a raw bearer token.
• Sender Key: the ID of your Plus Channel registered with the BSP.
• Template Code Prefix: optional, helps identify your Kakao-approved Alimtalk templates.

Example

A customer in Seoul receives an order-confirmation Alimtalk, and if they reply, that message lands in the Omnifox Inbox as a KakaoTalk conversation ready for an agent to continue.

Tips

• Alimtalk requires templates pre-approved by Kakao — you can't send free-form text as a transactional notification.
• The BSP signs the body with HMAC-SHA256 using your API Key, in the X-Kakao-Signature header.

Troubleshooting

• Sends fail: confirm the Sender Key exactly matches the active Plus Channel on the BSP side.
• Inbound events don't arrive: check that the callback configured in the BSP's dashboard points to the correct webhook URL.