WeCom
AI CRM
Brings customer relationships, sales follow-ups, and AI-assisted recommendations into the WeCom workflow the team already uses every day.
Deployed · Continuously evolvingCore workflow
WeCom provides identity and customer-asset entry points; the CRM preserves business facts across the sales process.
Project background
Customer relationships often become scattered across employee contacts, spreadsheets, and personal memory. Using the WeCom workbench as the entry point brings member identity, customer relationships, tags, follow-up records, and pending actions into one operating chain.
AI is deliberately limited to recommendations, summaries, and drafts. It does not contact customers automatically on behalf of sales staff.
Key capabilities
The page reflects the business entry points already covered while preserving the truthful status of continuous iteration.
Opens the H5 application from the WeCom workbench, identifies the member, and establishes a login session.
Synchronizes customer information with clear boundaries for owners, tags, and customer-group relationships.
Supports new customers and leads, plus CSV field mapping and bulk import.
Stores follow-up records and creates pending reminders when a next action is scheduled.
Handles reminder status and provides integration points for WeCom application messages and SMS providers.
Supports pluggable profiles, recommendations, and drafts without sending content to customers by default.
Engineering trade-offs
Vue 3 · NestJS · PostgreSQL · Redis / BullMQ
The frontend and backend share CRM types, while external providers are encapsulated on the backend. WeCom callbacks and synchronization jobs are designed for idempotency, retries, and auditability.
Permission boundary
Customer data requires row-level access controls based on member, department, and role. Standard customer-contact APIs cannot directly read chat content; future conversation archiving would require separate authorization, compliance, and audit handling.
This page does not publish customer-interface screenshots or real/sample names, phone numbers, company names, tags, or sales records.
Public disclosure boundary
The public page describes product goals, workflows, and engineering capabilities only. Screens involving customer assets and enterprise identity are demonstrated solely in authorized, controlled environments.
- Public page
- No CRM workbench, customer list, or customer-detail screenshots
- Data protection
- Real and sample names, company names, tags, and sales records are excluded from public assets
- Controlled demo
- When needed, the system is demonstrated separately in an authenticated environment
Want to understand the actual WeCom CRM workflow?
The system entry point is private, but the product and technical implementation can be discussed by email.