Product feature
Owners, sales operators, and CRM users
Customer Management
A customer directory that keeps buyer profiles, contact details, activity, merge handling, exports, and AI memory aligned.
Overview
Customer Management gives Billions+ a reliable memory layer for people who buy, ask questions, return later, or interact with the AI Sales Agent. It is the operational CRM behind the chat-commerce workflow.
The customer record keeps more than a name. It connects contact details, order history, activity, status, and notes into one business-scoped profile. That matters because repeat customers are common in chat commerce. The owner and the AI both need context to avoid asking the same questions again and to make future recommendations feel relevant.
How It Works
The customer list supports KPI cards, search, status filtering, pagination, exports, and bulk activation or deactivation. The detail page splits the customer view into a profile sidebar and tabs for overview and activity.
The create and edit form supports customer data entry and a merge-confirm flow. If a Telegram handle or related identifier would collide with an existing bot-created customer record, the server can return a merge-required response. The interface pauses the save, explains the candidate match, and lets the owner confirm the merge explicitly.
Activity is built from related business data. Customer metrics are derived from orders and conversations, while timeline rows come from the server activity log. This gives owners a more useful profile than a static contact record.
Components
Customer Directory
The directory is the working list for owners. It supports quick search, status filtering, row actions, bulk status updates, and exports. It is meant for everyday use, not just occasional administration.
Customer Profile
The profile panel shows contact and account context in one place. It gives the operator enough information to recognize a customer before editing, replying, or reviewing order history.
Activity Timeline
The activity tab helps the owner understand what happened with a customer over time: orders, conversations, status changes, and recent actions. This is the beginning of a stronger sales memory layer.
Merge Protection
The merge-confirm flow protects data quality when a real customer and a bot-created or imported record overlap. It avoids silent duplicates and prevents accidental overwrites.
Operating Proof
The operating proof is the connection between profile, orders, conversations, AI memory, and activity. A customer record becomes useful when the owner can see what happened before and decide what should happen next.
Related Pages
- Feature: AI Sales Agent
- Feature: Order Management
- Feature: Notifications
- Sub-feature: Business Knowledge