Support inbox
Inquiries arrive from everywhere. You answer them in one place
Run several services and still have one inbox. Receiving inquiries, assigning an owner, and replying all happen on one screen.
- Email · Receipt reissue request · In progress
- KakaoTalk · Can I get a refund? · New
- Web form · Partnership proposal · On hold
Sample layout. Not real data.
Each service takes inquiries in a different place, so the team checks several inboxes
→ Inquiries from email, the KakaoTalk chatbot, web forms, and the intake API land in one inbox
When a customer asks again, the earlier conversation is hard to find
→ The customer's past conversations show up right next to the current one
Similar replies get written from scratch every time
→ Start from a reply template or an AI draft, then edit and send
Features
Channel intake
Email · KakaoTalk chatbot · Web form · Intake API. If the same inquiry is sent twice, it's saved once
Replies and internal notes
Email replies go to the original thread. Notes stay inside the team
Status, assignee, tags
Four statuses, an assignee, and tags to filter by
AI reply drafts
AI reads the conversation and writes a draft. By default, a person checks it before it goes out
Merge and split
Merge duplicates and split unrelated messages. Conversations on hold reopen at the time you set
Attachments
Email attachments stay with the conversation
Webhooks
Send new conversations and replies to an address your team picks, like your own service or Discord
Customer chat link
Continue a KakaoTalk inquiry through a one-to-one web chat link
Support metrics
Time to first response, measured as median and p90
MCP inbox tools
AI agents look up and organize conversations