System Architecture

Kono × 1Q Banker
Service Architecture

// KEB Hana Bank PoC · Facebook Messenger · 2017

Customer Layer
👤
Customer
Bank customer seeking in-person financial consultation from a mobile 1Q Banker
Mobile Facebook App
💬
Facebook Messenger
Primary interface channel. No app install required. Supports card carousels, quick replies, outlinks
Chat UI Card Carousel Quick Reply
NLP
Input
Rich
Response
Kono Bot Layer
🤖
Kono Bot (AI Core)
Conversational engine. Handles intent classification, dialogue state management, and response generation
Intent Classifier Dialogue State NLP Date Parser
🧠
NLP Engine
Parses natural language date/time expressions (e.g. "다음주 화요일", "이번주 말") and free-text location input
Date Parsing Location NLP Self-learning
📋
Scheduling Engine
Matches customer request to available 1Q Bankers by district and time. Surfaces up to 3 time slot options
Availability Match District Filter
Schedule
Query
Confirm
+ Write
Backend Services
📅
Google Calendar API
Reads 1Q Banker availability. Writes confirmed appointments. Issues ICS calendar file for download
Read Availability Write Event ICS Export
📱
Notification System
Dual delivery: SMS to both customer and banker on confirmation. Push notification via Messenger on changes
SMS FB Push Email (ICS)
🏦
1Q Banker Backend
Internal KEB system. Stores banker profiles, district coverage, and appointment records. Future: full CRM integration
Banker Profiles District Map PoC: Google Cal
End-to-end Data Flow
💬
Customer
opens chat
🤖
Bot detects
intent
🧠
NLP parses
date + location
📅
Query
banker calendar
📋
3 slot options
returned
Customer
confirms
📱
SMS + ICS
sent to both
Customer / Channel Layer
Kono Bot AI Layer
Backend Services
PoC-scope integration