A B2B SaaS that runs KakaoTalk alimtalk, friendtalk and brand-messages on one platform. We designed it full-stack so marketers can wire campaign flows without an engineer, charge against a wallet, and watch dispatch in real time.
The more seriously a company runs KakaoTalk messaging, the more they end up needing their own system.
Alimtalk, friendtalk and brand-message each have different dispatch rules and template constraints. Wiring 'friendtalk on D+1, alimtalk on D+7, brand-message on D+14 for non-responders' meant calling an outside dev every campaign.
And teams couldn't scale campaigns without tracking spend in real time — existing tools settled costs after dispatch, leaving the marketer flying blind in the meantime.
Channels, templates, campaigns and billing stop being separate concerns and become one operating flow, with a flow engine that marketers can draw themselves.
KakaoTalk channel and template management share one home. Campaigns run through a flow engine shaped like 'condition → branch → send → wait → next send.' Once a marketer draws it, the same flow clones into the next campaign and morphs from there.
Billing rides on a wallet that deducts per-message rates in real time. Dispatch stats roll up at the delivered/read level live, so marketers can adjust mid-campaign.
Marketer UI on Next.js, message-dispatch engine on Spring. Stacks split by role.
Dispatch history into DynamoDB at scale, campaign state in Redis for real time.
Queues on SQS, workers on Lambda. Channel-specific dispatch policies isolated per queue.
Alimtalk, friendtalk and brand-message behind one abstraction. Operators just pick a channel.