KakaoTalk Business Messaging: Access, Roles & Permissions
TL;DR
Business messaging on KakaoTalk runs through a KakaoTalk Channel upgraded to a Business Channel by registering a Korean business license and passing verification. Its defining governance fact is that brands generally cannot self-serve the business-message API — sending requires a Kakao-issued sender key held through a Kakao-authorized agency. Roles split across a channel (Master/Manager) and a developer app (Owner/Editor/Message Editor/Viewer), and messaging splits into transactional AlimTalk and marketing FriendTalk.
On this page
Account and the business-registration gate
Business messaging on KakaoTalk runs through a KakaoTalk Channel. To send business messages, a channel must be upgraded to a Business Channel by registering legal business information — in practice a Korean business registration certificate — and passing Kakao's business verification review, which takes roughly three to five business days (Kakao Developers).
Foreign companies generally cannot complete this verification directly and typically partner with a local agency; some industries are excluded outright.
Roles: channel and developer app
Roles are split across two surfaces. A channel has a single Master administrator plus Managers the master invites; only master or manager accounts can link a channel to a developer app.
On the separate Kakao Developers side, an app is managed by four named team roles — Owner (full control, including key management and ownership transfer), Editor (all configuration except owner-only actions), Message Editor (message-template registration only), and Viewer (read-only). Billing is governed independently through BizWallet roles.
AlimTalk vs FriendTalk
Kakao splits business messaging into two products with different governance:
- AlimTalk (알림톡) carries transactional notifications, can reach users who have not added the channel, and requires every message to match a pre-approved template inspected by Kakao.
- FriendTalk (친구톡) carries marketing content, needs no template approval, but may only be sent to users who have added the channel as a friend (opted in) (Infobip).
The mandatory agency + sender-key model
Unlike most Western channels, brands generally cannot self-serve the KakaoTalk business-message API. Sending requires a Kakao-issued sender key / sender profile (발신프로필) that certifies the sending company, and this is registered and held through a Kakao-authorized Biz Message agency or reseller (BSP such as NHN Cloud, Infobip, Sinch, or Sendbird).
Infobip's onboarding, for example, states that the partner "manages and configures your KakaoTalk connection" using the business license and channel IDs. Access is therefore delegated to — and revocable through — the authorized partner rather than held solely by the brand. This is the load-bearing fact of KakaoTalk governance.
Frequently asked questions
Can I send KakaoTalk business messages without an agency?
Generally no. Business messaging requires a Kakao-issued sender key that certifies the sending company, and that key is registered and held through a Kakao-authorized Biz Message agency or reseller. Brands cannot obtain the business-message API directly the way they can on LINE or WhatsApp.
What is the difference between AlimTalk and FriendTalk?
AlimTalk is transactional: template-based, pre-approved by Kakao, and able to reach any user by phone even without a friend relationship. FriendTalk is marketing: richer, no template approval, but only to users who have added the channel as a friend.
Do foreign companies need a Korean business registration?
A Business Channel requires Korean business information and verification, and foreign companies usually cannot self-verify — they work through a local agency. Some industries are excluded. This is stricter than the Western platforms, which verify but rarely block account creation.
Related
Business Messaging: Access, Roles & Permissions Across Platforms
Every major messaging platform gates business access differently. The single most important difference is who holds the technical keys: some platforms (Apple, Google RCS, KakaoTalk, Viber) require an approved intermediary you cannot bypass, while others (Telegram, LINE, WhatsApp, Zalo) let a business hold its own API credentials. Role models range from granular named matrices (WhatsApp, LINE, Zalo) to almost none (Telegram, where possessing the token is control). Asian platforms additionally gate account creation on a registered legal entity.
Read →WeChat Official Account: Access, Roles & Permissions
Business presence on WeChat is a registered Official Account tied to a legal entity — a Chinese business license for mainland accounts, and overseas businesses are limited to a single verified Service Account. The permission model is small and fixed: one primary Administrator plus a set of Operators, each bound to a personal WeChat. Verification is the capability gate — a verified Service Account unlocks the advanced API and WeChat Pay; unverified accounts are limited to basic messaging.
Read →LINE Official Account: Roles & Permissions
LINE governs business presence through a badge-tiered Official Account (unverified gray / verified blue / premium green). It has an unusually clear, recently-maintained role model — but split across two consoles: a business console (Admin plus Operator variants) for day-to-day work, and a separate developer console (provider and channel roles) for the API. The Messaging API is authenticated with a per-channel access token the account owner mints and revokes.
Read →What is a Unified Inbox?
A unified inbox consolidates conversations from multiple communication channels — messengers, email, and more — into a single interface, so you can triage, read, and reply across all of them without switching apps and without losing track of who said what.
Read →Last updated