Message Center vs saleSmartly+Meta · Item Checklist · 14 items checked
UI-flow completion 29% (4/14 items UI-flow done)
ItemStatus
WhatsApp send/receive⚠ Needs real API backend
Real usability after Meta connectChat UI is complete; real send/receive needs the Meta WhatsApp Business API and works once connected.
QR multi-account login⚠ Needs real API backend
Real usability after Meta connectsaleSmartly-style QR login uses an unofficial protocol with ban risk; we only do official-API business-number binding, no QR multi-login.
Anti-ban strategy⚠ Needs real API backend
Real usability after Meta connectOfficial-API template messages plus send throttling is compliant anti-ban; strategy UI is done, enforcement needs real API quotas.
Broadcast messaging⚠ Needs real API backend
Real usability after Meta connectBroadcast editor is done; real sending needs Meta template approval plus user opt-in, and always goes through Human-Gate.
Staff permission management✅ UI flow implemented
Real usability after Meta connectRole/agent permission UI is done; enforced once the RBAC backend is connected.
Staff chat monitoring⚠ Needs real API backend
Real usability after Meta connectMonitoring view UI is done; real monitoring needs message persistence plus audit backend, on par with saleSmartly.
Customer data protection✅ UI flow implemented
Real usability after Meta connectUI logic hiding customer numbers to prevent order poaching is done; enforced once real auth lands.
Message cloud storage⚠ Needs real API backend
Real usability after Meta connectuc_ message tables are built; real storage needs Meta webhook callbacks writing into the DB.
New-message sound✅ UI flow implemented
Real usability after Meta connectSound and unread-badge UI are done and work right in the browser.
Meta official multi-channel⚠ Needs real API backend
Real usability after Meta connectWA/FB Messenger/IG DM channel-entry UI is done; truly usable once the official API connects — the core saleSmartly parity item.
Quick-reply templates✅ UI flow implemented
Real usability after Meta connectTemplate-management UI is done; used directly in real conversations once connected.
Conversation assignment⚠ Needs real API backend
Real usability after Meta connectAssignment-rule UI is done; real routing needs an agent-presence service.
Read/unread status⚠ Needs real API backend
Real usability after Meta connectStatus-marker UI is done; real read receipts need Meta API callbacks.
Message translation aid⚠ Needs real API backend
Real usability after Meta connectTranslate-button UI is done; real translation needs an LLM/translation API — Indonesian↔Chinese is the must-have.
Honest verdict: once the official Meta API is connected, send/receive, templates, and multi-channel are truly usable; QR multi-login is not built (unofficial = ban risk); broadcast always goes through Human-Gate.
📌 Honest Verdict
Current = UI/flow-level complete; production-grade = after connecting the corresponding APIs + real authentication. Go to /connect/ to connect the services.
PENDING Every executable action (listing/broadcast/go-live switch) is always Human-Gate PENDING: disabled + yellow badge, never automatic.
Go to Connect Center /connect/ →