How chat orders work
Set up your KakaoTalk order channel
In StackCube, navigate to Channels → Chat and connect your KakaoTalk business account. StackCube links to your designated order channel (a KakaoTalk group or direct account) and begins monitoring it for incoming order messages. Your customers don’t need to do anything differently — they keep using KakaoTalk as usual.
Customers send item names and quantities in chat
Customers message your KakaoTalk channel with their order — typically a list of item names and quantities written in natural language, for example: “사과 5박스, 배 3박스 주세요” or “Apple 5 boxes, pear 3 boxes please.” No special format or command syntax is required.
StackCube creates order candidates from the message
StackCube’s AI reads the incoming message and extracts the item names, quantities, and any special instructions. It then creates structured order candidates in your review queue, matching items to your product catalog where possible and flagging anything that needs clarification.
Why this matters for your team
Moving chat orders into StackCube solves several problems that come with managing orders directly in a messaging app.Full order visibility
Orders are no longer trapped in one person’s KakaoTalk account. Any team member with access to the StackCube order list can see incoming chat orders, assign them, and act on them.
Status tracking
Each chat order gets a status — pending, under review, approved, fulfilled — just like orders from any other channel. No more guessing whether a message has been acted on.
No personal chat dependency
Orders don’t disappear if a sales rep is out sick or leaves the company. Because everything routes through StackCube, the business owns the order history, not an individual’s device.
No manual copy-paste
Your team doesn’t need to copy message text into a spreadsheet or order system by hand. StackCube does the extraction automatically, reducing transcription errors and saving time on every order.
SMS orders work similarly to KakaoTalk. If your customers text orders to a business phone number, StackCube can connect to SMS intake as well — the same AI extraction and review flow applies.
Handling ambiguous messages
Not every chat message is a clean, structured order. Customers sometimes send partial information, use informal shorthand, or reference previous conversations.What if a customer sends an incomplete order (missing quantities)?
What if a customer sends an incomplete order (missing quantities)?
StackCube creates a candidate from what it can extract and flags the missing fields for review. Your team sees the original message alongside the incomplete candidate and can fill in the gaps before approving. You can also reply in KakaoTalk to ask for the missing detail — the updated message will create a new candidate or be linked to the existing one.
What if the item name doesn't match anything in my catalog?
What if the item name doesn't match anything in my catalog?
StackCube flags the candidate with a “needs match” status. You can manually select the correct product from your catalog when reviewing, and StackCube learns from that correction to improve future matching for similar names.
What if multiple customers message the same channel?
What if multiple customers message the same channel?
Each message is attributed to the sender. Orders from different customers are kept separate in the review queue and can be filtered by customer in the order list.