UniscrmWeCom private-domain SCRM
Turn WeChat and WeCom user assets into a private-domain growth engine you can operate, measure and replicate. Built on Java / Kotlin and Spring: 16 WeCom business modules and 132 controllers covering customer assets, conversation archiving, group operations, QR-code acquisition, content marketing, customer service and risk control.
Customers are not friends sitting in an employee’s WeChat — they are assets the company can inherit, assign and measure. That is where the entire data model starts.
From the first friend request to repeat purchase — the whole journey is traceable, measurable and reviewable.
What problem does it actually solve
Four core capabilities, mapped to four real business needs.
Customers stop accumulating in personal WeChat accounts and become company assets that can be inherited and reassigned.
SOP-driven welcome, nurturing and win-back for new customers; tasks are dispatched to people automatically and completion is tracked.
WeCom conversation content is archived compliantly, meeting regulatory and internal risk-control requirements.
Channel ROI, conversion cycles and repeat-purchase rates all land on dashboards, so every operating action can be measured.
Capabilities at a glance
- Conversation archiving: compliant retention of chat history, searchable and auditable, with employee consent and watch-list mechanisms
- Customer assetisation: profiles, tagging, custom fields, merge-and-dedupe, and handover on employee departure
- Group operations: group SOPs, welcome messages, group tags, transfers and automated tasks
- Multi-channel acquisition: staff QR codes, customer QR codes, group QR codes, campaign codes and a lead pool
- Content marketing: articles, forms, mini-sites, posters, short links and share tracking
- Risk control: sensitive words, content audit, unfriend alerts and churn warnings
Not a product that lives in slides
The numbers below come from the real code in the uniscrm-coplit repository: modules, tables, endpoints and capability items.
Tech stack
Go deeper
Each subpage answers a specific kind of question — not the same content re-typeset.
Features
8 business domains, 48 concrete capabilities — each one backed by an implementation that exists in the code.
Customer assetisation
uniscrm-customer · customeropEvery customer interaction is booked to the company’s ledger, not to an employee’s phone.
- Customer profiles: full sync of WeCom external contacts with extensible profile fields
- Tag system: enterprise tags, tag groups and auto-tagging rules
- Custom fields: MetadataAttribute / MetadataTaxonomy support business-defined metadata
- Customer segmentation: combine tags, fields and behaviour into operable audiences
- Customer merge: duplicate detection and merging
- Customer transfer: handover on departure and reassignment in post — relationships do not leave with the person
- Customer events: a behaviour event stream that drives downstream automation
Conversation archiving & compliance
uniscrm-msgauditChat history is not stored and done — it must be searchable, auditable and able to prove compliance.
- Session and message archiving: all chat content archived by conversation
- Pull tasks: incremental pulls with resumable transfer
- Group archiving: group chat content is retained as well
- Employee consent forms: authorization is obtained before archiving, with a checkable process
- Watch-lists: conversations of designated employees or customers flagged for review
- Full-text search: locate historical conversations by keyword, time and participants
Group operations
uniscrm-group · groupopOne person running 50 groups takes SOPs, not diligence.
- Group profiles and tags: classification and tiered management of groups
- Group welcome messages: a welcome template fires automatically when members join
- Group SOPs: group operations choreographed on a timeline
- Group transfer: group ownership hands over smoothly when the owner changes
- Group operations: bulk messaging, material delivery and campaign execution
QR codes & acquisition
uniscrm-toker · leadOne code per channel, so the source of every customer is obvious.
- Staff QR codes: scanning adds a designated employee and tags the channel automatically
- Customer QR codes: customer add-codes distributed per channel
- Group QR codes: automatic group assignment that switches when a group fills up
- Campaign codes and code packs: dedicated acquisition codes for marketing campaigns
- Group-join guidance: after adding a friend, users are guided into a group automatically
- Phone-number import: bulk import of existing customers
- The lead pool and lead data: leads consolidated and assigned in one place
Content & marketing
uniscrm-marketing · 内容中心A material library the frontline draws on at any moment, plus a share chain you can track.
- Material library: articles, images and files managed together and callable from the sidebar
- Mini-sites and pages: visually assembled public-facing pages
- Forms and form records: lead-capture forms and data collection
- Posters: campaign poster generation and distribution
- Share tracking: content share chains and view-log analysis
- Short links: tracked short links on your own domain
- Welcome rules: new-friend welcome messages and new-customer nurturing flows
Service & tasks
uniscrm-kefu · missionReception, transfer, follow-up, review — one closed chain.
- Service accounts and conversations: multi-agent reception and conversation assignment
- The service sidebar: scripts and material ready at hand
- The service knowledge base: common questions captured and instantly callable
- Service statistics: reception volume, response time and satisfaction
- Task dispatch: SOP tasks assigned to people automatically
- Completion tracking: task execution made visible
Risk & audit
uniscrm-riskctl · 内容审计Diverted deals, off-book transactions, non-compliant promises — the system notices before the supervisor does.
- Sensitive-word blocking: non-compliant phrasing recognised and blocked in real time
- Content audit: compliance review of outbound content
- Unfriend logs: customer-deletion events recorded with alerts
- Churn alert configuration: churn signals trigger notifications
- WeCom callback governance: authorization, binding and event callbacks managed in one place
Data & dashboards
uniscrm-reportOperating actions must end in numbers.
- Customer asset inventory: total customers, growth and structure
- Conversion funnel: tiered conversion from friend request to deal
- Staff effectiveness ranking: multi-dimensional comparison of adds, follow-ups and deals
- Channel ROI: input–output comparison per source channel
- Real-time dashboards: key metrics monitored live
API contract
12 representative endpoints. What is listed here is the skeleton of the public contract; full definitions ship with the deployment.
/api/wecom/callbackThe main WeCom event callback entry: authorization, binding, directory and external-contact events
/api/customer/listCustomer profile list, filterable by tags, custom fields and behaviour combinations
/api/customer/transferCustomer transfer: handover on departure and reassignment in post — relationships do not leave with the person
/api/toker/staff/codeGenerates a staff QR code; scanning and adding tags the channel automatically
/api/msgaudit/session/searchFull-text search over archived conversations for evidence by keyword and time
/api/mission/dispatchSOP task dispatch to individuals with completion tracking
/api/riskctl/sensitive/checkReal-time sensitive-word validation; non-compliant phrasing is blocked
/api/report/funnelConversion funnel: tiered conversion from friend request to deal
/api/marketing/form/submitLead-capture form submission and data collection
/api/shrlink/{code}Short-link redirect with tracking-parameter recording
/api/report/channel/roiChannel ROI: input–output comparison per source
/api/group/sop/executeGroup SOP execution: welcome messages, bulk delivery and campaigns
One real call
What an endpoint actually looks like says more than a list of endpoints.
01$ curl -X POST https://scrm.zhenbei.tech/api/customer/transfer \02 -d '{"fromStaff":"zhang","toStaff":"li","scope":"all","notify":true}'0304{ "customers": 412, "groups": 37, "transferred": 449,05 "auditId": "tr_9f2c41",06 "handover": { "followUps": 1286, "sessions": "archived" } }Contract discipline
An endpoint is a promise, not an exposure of implementation details. These three rules are ones we always keep.
Breaking changes go through a major version, announced one release cycle ahead. A shipped endpoint never changes semantics because of internal refactoring.
Error codes carry semantics instead of a blanket 500, so callers — including AI agents — can decide whether to retry or give up.
Structured data is returned by default instead of human-readable prose, so AI can read it directly — no human screenshotting and relaying.
Modules
6 groups, 17 code modules — all from the real directory structure of the uniscrm-coplit repository.
uniscrm-server-java/Turning WeChat friends into company assets.
uniscrm-customerCustomer profiles, tags, custom fields, segmentation and customer events
modules-wecom/uniscrm-customeruniscrm-customeropCustomer operations: transfer, merge, dedupe and lifecycle transitions
modules-wecom/uniscrm-customeropuniscrm-staffStaff management: employee profiles, onboarding requests and employee tags
modules-wecom/uniscrm-staffWhere frontline employees do their daily work.
uniscrm-kefuCustomer service: conversation management, knowledge base, sidebar, service accounts and statistics
modules-wecom/uniscrm-kefuuniscrm-msgauditConversation archiving: sessions, messages, pull tasks, groups, employee consent and watch-lists
modules-wecom/uniscrm-msgaudituniscrm-notifyNotifications: message push, reminders and event notifications
modules-wecom/uniscrm-notifyBringing people in, and keeping groups under control.
uniscrm-group / groupopGroup management: group profiles, group tags, transfers and group operations
modules-wecom/uniscrm-group*uniscrm-tokerQR-code acquisition: staff codes, customer codes, group codes, campaign codes, lead import and group joins
modules-wecom/uniscrm-tokeruniscrm-leadLead management: the lead pool and lead assignment
modules-wecom/uniscrm-leadMaterial, campaigns and the sharing chain.
uniscrm-marketingMarketing: campaigns, delivery plans, posters and welcome rules
modules-wecom/uniscrm-marketingContent centreArticles, content items, mini-site pages, forms, form records, shares and view logs
modules-common/uniscrm-contentShort links & mini programsShort-link generation, domain management, redirect tracking and mini-program configuration
Shrlink* / Wxapp* ControllerThe last gate of compliance and internal risk control.
uniscrm-riskctlRisk control: risk detection, unfriend logs and churn alert configuration
modules-wecom/uniscrm-riskctlContent audit & sensitive wordsContent compliance review and sensitive-word blocking
ContentAudit / SensitiveWord Controlleruniscrm-systemSystem: enterprise configuration, WeCom app configuration, storage configuration and permissions
modules-wecom/uniscrm-systemOperating actions must be measurable.
uniscrm-reportDashboards: conversion funnels, staff effectiveness and customer asset inventory
modules-wecom/uniscrm-reportuniscrm-missionTasks: SOP task dispatch and completion tracking
modules-wecom/uniscrm-missionLayered design
From access to runtime — what each layer owns and what it is built with.
Platform*: enterprise onboarding, WeCom authorization binding, suite configuration and callback governance
modules-wecom: WeCom external contacts, sync tasks, media and callbacks
customer / customerop: profiles, tags, fields, events and transfer/merge
group / toker / marketing: group operations, QR-code acquisition, content and campaigns
kefu / lead / mission: service conversations, the lead pool and task dispatch
msgaudit / riskctl / sensitive: conversation archiving, risk control and content audit
report / system: dashboards, reports and system configuration
Key flows
The most important paths, unpacked step by step.
A new customer from QR scan to deal
The main private-domain path, with every step recorded.
- 1
The customer scans a channel QR code and the system identifies the source
- 2
Adding the employee as a friend tags the channel and triggers the welcome message
- 3
A day-one follow-up task is dispatched to the right employee per the SOP
- 4
The employee follows up from the WeCom sidebar using library scripts, recording each touch
- 5
When stage conditions are met, the lifecycle stage advances automatically
- 6
Deal data flows back to the dashboard and channel ROI becomes computable
Customer handover when an employee leaves
The person leaves; the customers stay.
- 1
The employee-departure event enters the system
- 2
The system inventories the customers and groups under that employee
- 3
Successors and group owners are assigned by rule
- 4
Customer and group transfers execute
- 5
Transfer records are written to audit and the new owner is notified
- 6
The new owner sees the full follow-up and conversation history in the sidebar
Conversation archiving and compliance review
When the regulator comes, the evidence is ready.
- 1
Employees sign the archiving consent form; the authorization state is recorded
- 2
MsgauditPullTask pulls conversation content incrementally
- 3
Message bodies, media and participant information are archived
- 4
Sensitive-word and content-audit rules scan historical messages
- 5
Conversations hitting rules are flagged to the watch-list and pushed to administrators
- 6
Auditors retrieve evidence by keyword and time range
Tech stack
Scale & benchmarks
These numbers are not estimates — they are read from the code and runtime configuration. Each one states what it actually means, so it cannot be mistaken for marketing.
uniscrm-coplitHTTP controllers covering 16 WeCom business modules
Conversations and messages archived per session, with employee consent and watch-list mechanisms
Staff / customer / group / campaign codes, each independently attributed
Articles, pages, forms, posters, short links and share tracking
Channel tags applied automatically on customer add; ROI and conversion cycles computable
Customer asset inventory, conversion funnels, staff effectiveness and channel comparison
Facts you can count in the repository
Every item below can be checked in uniscrm-coplit: modules, tables, endpoints and capability items. Whether something is “done” is judged by whether these numbers moved.
Security and compliance support points
What Uniscrm concretely does for security, and where the boundaries are drawn. Every item notes where it is implemented, so you can verify.
Built on WeCom’s official archiving capability; employees give written consent before archiving, with consent state recorded and checkable.
uniscrm-msgaudit · employee consentNon-compliant phrasing is recognised and blocked before sending, not found afterwards in the logs.
SensitiveWord ControllerOutbound content falls under compliance review; rule hits are flagged to the watch-list.
ContentAudit ControllerCustomer deletions are logged and trigger alerts, surfacing churn signals early.
uniscrm-riskctlWeCom authorization, suite configuration and event callbacks are managed in one place, keeping the authorization boundary clear.
PlatformWecomAuthorization / CallbackObject storage can connect to the customer’s own OSS configuration, keeping media inside the customer environment.
storage configuration and domain verificationWhere the data stops
The data boundary is determined by the product form, not a toggle someone can flip. This is the shared judgement across all four business lines.
The minimum boundary for endpoint products. Data at this layer has no upload path by design — it is not switched off by a toggle.
- All legdger ledger data: encrypted locally, only ciphertext reaches the cloud
- legdger on-device AI statistics and Q&A: inference runs on the device
- NewTool desktop and wasm forms: the algorithm kernel has no IO, so data never leaves the process
- pxc captured traffic: the kernel runs locally and does not pass through third-party services
The boundary for private deployment. Models, vectors, business data and audit records are all deployed inside the customer’s own network.
- Uniclaw memory and knowledge vectors: self-hosted Milvus, never leaving the intranet
- Uniclaw model services: can connect to privately deployed compatible-protocol services
- UIAM identity and audit data: the whole deployment sits inside the customer boundary and can run fully air-gapped
- Uniscrm assets and media: object storage can connect to the customer’s own OSS
- Unilearning courseware and learning records: delivered as a single container, with data under the customer’s control
The only things needing external network access are sync and external channels, and what travels is ciphertext or already-desensitised messages.
- legdger cross-device sync: uploads only the latest ciphertext, and the server keeps no history
- Uniscrm WeCom channel: communicates with official WeCom interfaces and uses official archiving capability
- Uniclaw channels: Feishu / DingTalk push APIs, with content isolated per tenant
- NewTool remote calls: transported over MCP, while the algorithm kernel itself makes no network requests
Company-wide security principles
Whichever business line, these six are the shared floor.
Any constraint that can be baked into the compiler, the framework or the query layer does not go into a document for people to remember. Tenant isolation is enforced by a query-layer listener; domain boundaries are rejected at compile time by Go’s internal mechanism.
jOOQ TenantScopeVisitListener · Go internal 墙Sensitive data stays on the user device or inside the customer network by default. All four business lines support private deployment, and legdger does not even send AI analysis off the device.
legdger 端侧 AI · Uniclaw 自建 Milvus · Unilearning 单容器Agents never share human credentials, servers never hard-code long-lived keys, and endpoint integrations use revocable tokens. Any credential can be revoked on its own without affecting other principals.
UIAM MACHINE 主体 · OSS STS AssumeRole · ledger-cli 令牌Authentication, authorization, tool calls and captured traffic all produce structured records. We keep them not for compliance theatre but so that incidents can be replayed.
uiam-audit · collaboration-logger · pxc 会话记录Delegation is expressed with the act claim — who acts for whom — with permissions intersected at every hop. Audit can answer which user authorized which agent, which tool it called, and with which permissions.
RFC 8693 Token Exchange · agent_tools 注册表Database changes go through versioned migrations that produce the same result on repeat; application releases are single-image swaps, so rollback means switching back to the previous image.
Liquibase · 各域方言迁移 · Docker 单镜像Deploy & integrate
Every product line supports private deployment; the concrete form varies by product.
Ready out of the box: complete the WeCom authorization and start operating.
- Self-service enterprise registration and WeCom authorization binding
- Suite configuration and callbacks provisioned automatically
- No servers to build
Data stays inside the customer’s own environment.
- Maven multi-module build, deliverable as a whole
- Standard dependencies: MySQL + Redis + RabbitMQ
- Can connect to the customer’s own object storage (OSS configuration)
The standard WeCom service-provider model.
- PlatformWecomAuthorization: the service-provider authorization flow
- PlatformWecomSuiteConfig: suite configuration management
- PlatformWecomCallback: unified handling of event callbacks
- Enterprise storage configuration and domain verification
Identity and AI capability reuse the other Zhenbei product lines.
- The internal account system can connect to UIAM unified identity
- Service scenarios can mount Uniclaw digital workers
- Conversation data becomes a source of agent knowledge and memory
Comparison
The same job, done in different ways. The left column is our choice; the right is the common alternative — the difference is usually not in the feature table but in where the boundary is drawn.
Who feels the difference
Feature lists do not convince people; role perspectives do. Below are the real before-and-after differences for four roles.
Customer assets are scattered across hundreds of employee WeChat accounts; head office sees neither the whole nor the process
Head-office dashboards show total customer assets, channel ROI and staff effectiveness, so operations can be reviewed
Scripts vary by person, new hires ramp slowly, and follow-up depends on memory
The WeCom sidebar puts the material library at hand, SOPs dispatch tasks automatically, and prompts guide the follow-up
Regulators require traceable conversations, and complete records cannot be produced when asked
Full conversation archiving + sensitive-word scanning + one-search evidence retrieval turns audit from passive to proactive
Sellers leave and take customers; revenue gaps appear and follow-up history cannot be handed over
Customer and group relationships inherit automatically, with full follow-up history and conversations handed to the new owner
Releases and roadmap
Shipped items state what was delivered, in-progress items what is being built, planned items what is intended. Shipped items are never reversed.
v3.0ReleasedAssetisation- Customer profiles and the tag system
- Conversation archiving with employee consent
- QR-code acquisition and the lead pool
- The content centre and mini-sites
v3.5ReleasedOperability- Group SOPs and group operations
- Task dispatch and completion tracking
- Channel ROI and conversion funnel dashboards
- Risk control and churn alerts
v4.0In developmentIntelligence- Deep integration with Uniclaw: digital workers in customer service
- Customer event streams driving automated operations
- AI script recommendations and follow-up suggestions
- Cross-store customer asset allocation
v4.5PlannedService-provider mode- A multi-enterprise service-provider model
- An industry template marketplace
- An open API and webhook ecosystem
- Automated customer asset inventory reports
Integrations and counterparts
Who Uniscrm needs to integrate with, and how.
Service-provider authorization; external contacts, groups and the directory sync in full
Short-link redirects, mini-program configuration and H5 hosting
Material and media storage; can connect to the customer’s own OSS
Async tasks and caching supporting sync and message delivery
The internal account system can connect to unified identity, converging employee login and permissions
Digital workers in service scenarios; historical conversations become the agent’s knowledge source
Adoption scenarios
How this is used in real business settings.
Dozens of stores and over a hundred advisors — customer assets must be visible to head office.
- Per-store QR codes segment acquisition by channel
- A unified script library in every advisor’s WeCom sidebar
- Head-office dashboards compare conversion across stores
Leads arrive from many channels and are assigned to course advisors.
- One lead pool consolidates and assigns
- Follow-up SOPs dispatch tasks automatically
- A full funnel from trial class to enrolment
Regulators require traceable conversations; sales scripts cannot cross the line.
- Full conversation archiving with employee consent forms
- Sensitive words block non-compliant promises in real time
- Auditors retrieve evidence in one search
Long cycles and complex multi-role follow-up.
- Custom fields capture customer business information
- Customer event streams record key touchpoints
- Handover on departure prevents coverage gaps
FAQ
Archiving uses WeCom’s official capability and has a built-in employee consent mechanism — authorization is obtained before archiving and consent state is checkable. Watch-lists and the sensitive-word mechanism let enterprises do internal risk control on a compliant footing.
Hand the complexity of identity, agents and private domain to one governable kernel
Whether you are replacing an existing IAM, building an agent platform, or trying to make private-domain operations actually work — start with a 30-minute architecture call. We will first judge whether this is the kind of problem we are good at, and say so plainly if it is not.