Glossary

WeCom (WeChat Work)

Definition

WeCom is a business communication and office collaboration tool developed by the Tencent WeChat Team. It provides a consistent communication experience with consumer WeChat and supports full connectivity with WeChat. In practice, that means a WeCom user can message a consumer WeChat user directly — and the consumer does not need to install a separate app.

The seller of record, per the iTunes lookup API for app id1087897068, is Tencent Technology (Shenzhen) Company Limited. WeCom is distributed through the Apple App Store (id1087897068, vendor-submitted listing) and Google Play (com.tencent.wework). Both listings were accessed 2026-10-02.

WeCom is not a consumer product. It is the enterprise-side bridge to the WeChat ecosystem. Your mainland team, partners, and customers already live on WeChat. WeCom is how an organization operates inside that network: admin controls, company-owned contact relationships, and customer-service conversations routed in from Mini Programs, Official Accounts, or H5 pages.

For a global company entering China, WeCom matters for a straightforward reason. If you need to reach anyone on the mainland — customers, partners, suppliers, local staff — WeCom is the enterprise channel that connects directly to the WeChat network they already use. It turns a consumer social network into a managed business channel.

The rest of this page defines what WeCom is, what it is not, and what this page deliberately does not cover. Every factual claim traces to a vendor-primary source (app-store listing or iTunes lookup API) or to content already published on this site. No claims from memory, no third-party summaries.

Why global companies encounter WeCom

Global companies typically encounter WeCom in three contexts.

B2B contact with mainland partners and customers. When a global brand communicates with mainland clients, distributors, or suppliers who use WeChat as their primary channel, WeCom provides the enterprise interface. Employees add customers' WeChat accounts as friends directly from WeCom. The enterprise retains visibility and control: companies can view and manage the WeChat customers added by their members, and reassign the customers of resigned members to remaining staff. Customer relationships belong to the company, not the individual employee. A sales rep's personal WeChat contact list leaves with the rep.

Teams operating inside mainland China. A local team — whether a WFOE's direct hires or a contracted operations team — will likely run its day-to-day communication through WeCom. It is the enterprise counterpart to consumer WeChat: business messaging and office collaboration with admin controls and company ownership of business contacts. A global company that does not itself operate in China still encounters WeCom when its local partners, agencies, or vendors use it as their primary coordination tool. Work with a mainland development team, a local marketing agency, or a contract manufacturer, and WeCom is the likely default channel.

Customer-service operations tied to the WeChat ecosystem. WeCom integrates WeChat Customer Service across scenarios both within and outside WeChat. For a global brand running a Mini Program or an Official Account, customer inquiries that originate inside those surfaces can route into WeCom for agent handling. The support team works in WeCom; the customer stays on WeChat. No app switch is required on the customer side. For any brand that runs customer-facing surfaces inside WeChat, WeCom is the staffed response layer behind them.

WeCom sits inside the broader WeChat ecosystem that global brands build on when they develop Mini Programs, accept WeChat Pay, or run Official Accounts. It is the internal-operations and customer-communication layer of that ecosystem — not the application layer (Mini Programs) or the content layer (Official Accounts), but the connective tissue between a company's staff and the WeChat network those customers live on. The family's fourth platform, the Weixin Open Platform, is the developer portal that connects native mobile apps to WeChat — not a staff tool like WeCom and not an in-WeChat surface like Mini Programs or Official Accounts.

What WeCom is

The capabilities below come from Tencent's own app-store listings for WeCom (Apple App Store listing id1087897068, vendor-submitted; Google Play listing com.tencent.wework). They describe what the product does, not how to configure it. All accessed 2026-10-02.

• Full WeChat connectivity. WeCom provides "a consistent communication experience with WeChat" and "supports full connectivity with WeChat." WeCom users can message and interact with consumer WeChat users directly. The two networks are connected, not parallel: a customer on consumer WeChat does not need to install WeCom to communicate with a WeCom user. This is what separates WeCom from a standalone collaboration tool — it reaches people on the network they already use daily.
• Customer contact management. Employees add customers' WeChat accounts as friends from within WeCom. The enterprise retains visibility: companies can "view and manage WeChat customers added by members, and reassign the customers of resigned members." This is the mechanism that prevents customer relationships from walking out the door when an employee leaves. For a global brand building a mainland sales or account-management team, it means the company — not the individual — owns the customer graph. That ownership model is a material difference from sales workflows that run on personal WeChat accounts.
• Customer groups up to 500 members. "The maximum number of members in a customer group can reach 500." That is large enough for community management, product-support groups, or client cohorts. Brands running loyalty communities or product-support channels inside WeChat can consolidate those groups under WeCom administration.
• WeChat Customer Service integration. WeCom integrates "WeChat Customer Service across various scenarios both within and outside WeChat." Scenarios within WeChat include entry points on a Mini Program or an Official Account; H5 pages sit outside it. In each case the customer opens the chat where they already are, and the agent handles it in WeCom — no app switch on the customer side.
• Company Pay. "Companies can use WeChat Pay to make funds with WeChat users, and can also receive payments from members or send red packets." Company Pay is an enterprise funds-movement feature inside WeCom. It enables transfers to WeChat users, member payments, and red-packet distributions. It is not the same product as WeChat Pay merchant acceptance — the distinction matters and is addressed in the next section.

What WeCom is not

• Not consumer WeChat. WeCom is a separate application with a separate account system. Consumer WeChat users do not install WeCom. The two apps connect to each other, but they serve different audiences and run on different identities. An employee's WeCom identity is managed by their employer; a consumer's WeChat identity is personal. The apps look similar and share a design language — which eases the hand-off for the customer side — but they are operationally distinct. A WeCom account is provisioned by the company; a consumer WeChat account belongs to the individual.
• Not a WeChat Pay merchant acceptance agreement. WeCom's Company Pay lets an enterprise move funds with WeChat users and receive payments from members. That is an internal enterprise-funds feature. It is not the same as the WeChat Pay merchant account — the acceptance-side agreement that lets a merchant charge customers at checkout. The merchant account runs on pay.weixin.qq.com and binds a merchant ID to an APPID. It has three onboarding paths — mainland, overseas-direct, institution-partner — differing in eligibility, documents, review time, and settlement terms. Company Pay does not replace any of that, and no WeCom deployment satisfies the merchant-acceptance requirement. If your use case involves charging customers for goods or services, you need the merchant account regardless of whether you also use WeCom.
• Not an Official Account or Mini Program substitute. WeCom does not publish content to followers, run Service Account menus, or host Mini Program experiences. Those functions belong to WeChat Official Accounts and Mini Programs respectively. WeCom can route customer-service conversations that originate from those surfaces, but it does not replace them. A brand that needs checkout inside WeChat builds a Mini Program or H5 page with a WeChat Pay merchant account — WeCom handles the support ticket that follows the purchase, not the purchase itself.

What this page deliberately does not cover

This page is definitional. It explains what WeCom is and what it is not. It does not cover:

• Registration or onboarding paths for foreign companies. WeCom's official registration documentation is Chinese-only. The international site is a JavaScript shell with no verifiable English-language onboarding steps, eligibility criteria, or verification requirements accessible from the landed page. We cannot publish registration guidance here without sourcing it from an English-language primary, and none exists at a precision level we would stand behind.
• Pricing, tier structure, or per-seat costs. Vendor listings do not publish a fee schedule accessible from the landed page.
• Verification requirements or admin-approval timelines.
• API, developer-platform, or webhook specifics. None of the sources banked for this page describe WeCom's API surface, and the citable official documentation is Chinese-only. We do not document integrations from a source we cannot stand behind.

No citable English-language primary source covers these topics for foreign companies with sufficient precision to publish here. Third-party agency guides that rank for "WeCom registration" fill that gap; we cannot verify their claims against a primary source, so we do not republish them. If an English-language primary emerges, we will update this page and note the change.

Common misconceptions

"WeCom is just WeChat with a work badge." No. WeCom is a separate application with its own account system, admin console, and enterprise controls. It connects to consumer WeChat — employees can message WeChat users directly — but the two apps serve different audiences. Consumer WeChat users never install WeCom. The enterprise owns the customer relationships and can reassign them when employees leave; consumer WeChat has no equivalent admin layer. The shared design language eases the hand-off for the consumer-side contact, but the operational model is entirely different. A WeCom account is created and managed by the company; a consumer WeChat account is personal.

"Company Pay inside WeCom means we can accept customer payments through it." Company Pay handles enterprise funds movement: transfers to WeChat users, receiving payments from members, sending red packets. It is not a merchant-checkout product. Accepting payments from customers at checkout requires a separate WeChat Pay merchant account with its own onboarding path, merchant ID, and APPID binding. The two products share the WeChat Pay brand but serve different functions. Do not conflate them in your planning: the merchant-acceptance agreement is the gate for checkout, not Company Pay. A stack that can move internal funds but cannot charge a customer at checkout is the predictable result.

"WeCom replaces the need for a Mini Program or Official Account." It does not. WeCom is the internal-operations and customer-communication layer. Mini Programs are the application layer — catalog, booking, membership, campaigns. Official Accounts are the content and service-menu layer. The three are complementary, not substitutable. A brand may route customer-service conversations from its Mini Program into WeCom — but the Mini Program still needs its own ICP filing and entity foundation. The same filed entity, typically a WFOE, underpins the Mini Program, the domain filing for backend APIs, and the WeChat Pay merchant account. WeCom operates on top of that foundation; it does not replace it.

Where WeCom fits in the China entry sequence

If your company is entering the China market and building any presence inside the WeChat ecosystem, WeCom is likely part of the picture — but it is not the first thing to set up. The sequence matters.

The entity and filing foundation comes first. The same filed entity — typically a WFOE — that holds the ICP filing for your domain typically holds the WeChat Pay merchant account and underpins the Mini Program. WeCom does not change those entity requirements. It does not file on your behalf. It does not substitute for mainland hosting. It does not provide merchant-acceptance capability. Each of those functions belongs to a different layer of the stack; WeCom sits above them as the communication layer, not below them as a foundation.

The customer-facing surface comes next, if your use case involves transactions. A Mini Program or H5 page that takes checkout requires the WeChat Pay merchant account — not Company Pay inside WeCom. The merchant account and the surface sit on the same entity foundation.

Consider a typical sequence for a global brand entering China: the WFOE is established, the ICP filing is submitted, the Mini Program is built with WeChat Pay merchant acceptance onboarded. At that point, the brand needs its mainland staff — sales, support, operations — to communicate with customers and partners on WeChat under company-managed accounts. That is when WeCom deployment makes sense.

WeCom enters the picture whenever enterprise-managed communication with mainland contacts is needed: a sales team managing customer relationships, a support team handling inquiries routed from Mini Programs or Official Accounts, or a local operations team coordinating with partners. It is the staff-side tool, not the customer-side surface.

Two infrastructure notes belong in the same plan. Your backend APIs still need to respond quickly for China users, which means mainland hosting on licensed operators — see the infrastructure service. And any website or Mini Program those APIs serve still needs a valid ICP filing — see ICP compliance.

Deploy WeCom before that foundation exists and you have a communication layer pointing at surfaces that are not there yet. The practical question is not whether to adopt WeCom — if you operate in mainland China, you likely will — but when in the sequence. The answer: after the entity, filing, and hosting foundation is in place, and after the customer-facing surfaces (Mini Program, H5, Official Account) are scoped.

Run the 10-point China readiness diagnostic before planning any WeCom deployment. It surfaces the entity, filing, hosting, and ecosystem gaps that need resolution first.

Deeper coverage

• WeChat Pay Merchant Account — the three acceptance paths, merchant ID binding, and entity prerequisites. The acceptance layer that sits alongside WeCom's Company Pay but serves a different function: merchant checkout, not enterprise funds movement.
• WeChat Official Account — Service vs Subscription accounts, verification, and the JSAPI payment gate. The content and service-menu layer that complements WeCom's customer-communication role.
• WeChat Pay for Foreign Companies — the full article on acceptance paths, documents, timelines, and cross-border settlement. The merchant-acceptance decision that sits next to any WeCom deployment.
• WeChat Ecosystem Service — how we coordinate Mini Program, H5, and WeChat Pay integration on the same entity and filing foundation. WeCom sits inside this ecosystem as the enterprise-communication layer.
• Alipay vs WeChat Pay (Merchant Acceptance) — the two acceptance agreements a foreign merchant may hold, the decision frame for choosing one or both, and what this comparison is not. Relevant when WeCom's Company Pay is being evaluated alongside broader payment-acceptance decisions.

Frequently asked questions

Related terms

• Weixin Open Platform — the developer portal that connects native mobile apps to WeChat — not a staff tool like WeCom and not an in-WeChat surface like Mini Programs or Official Accounts.
• WeChat Official Account (公众号) — the content and service-menu layer that complements WeCom's customer-communication role.
• WeChat Mini Program (微信小程序) — the application layer — catalog, booking, membership, campaigns — that WeCom routes support conversations from.
• Alipay vs WeChat Pay (Merchant Acceptance) — the two acceptance agreements a foreign merchant may hold; relevant when WeCom's Company Pay is evaluated alongside broader payment-acceptance decisions.

Related reading

• ICP Compliance Service — the entity and filing foundation that underpins Mini Programs, Official Accounts, and mainland-hosted services that WeCom connects to.
• Infrastructure Service — mainland hosting and CDN on licensed operators; the infrastructure layer your WeCom-connected backend APIs sit on.
• 10-Point China Readiness Diagnostic — score your site's readiness for mainland users before planning WeCom or any WeChat-ecosystem work.
• China Digital Entry Glossary — the full term set in one place.

Source notes

No claims from memory, no third-party summaries, no unverified statistics. Where a claim appears in quotation marks, it is a verbatim excerpt from the cited listing. Where it is paraphrased, the paraphrase tracks the vendor language closely and the source is cited.

1. 'WeCom is a business communication and office collaboration tool developed by Tencent WeChat Team.' — Google Play listing (com.tencent.wework), accessed 2026-10-02.
2. 'WeCom is a communication and office tool developed specifically for enterprises by the Tencent WeChat team. It provides a consistent communication experience with WeChat and supports full connectivity with WeChat.' — Apple App Store listing (id1087897068), vendor-submitted, accessed 2026-10-02.
3. '[Contact Customers] Add customers' WeChat accounts as friends… Enterprises can view and manage WeChat customers added by members, and reassign the customers of resigned members.' — Apple App Store listing (id1087897068), accessed 2026-10-02.
4. 'The maximum number of members in a customer group can reach 500.' — Apple App Store listing (id1087897068), accessed 2026-10-02.
5. '[WeChat Customer Service] Integrate WeChat Customer Service across various scenarios both within and outside WeChat.' — Apple App Store listing (id1087897068), accessed 2026-10-02.
6. '[Company Pay] Companies can use WeChat Pay to make funds with WeChat users, and can also receive payments from members or send red packets.' — Google Play listing (com.tencent.wework), accessed 2026-10-02.
7. Seller of record: 'Tencent Technology (Shenzhen) Company Limited.' — iTunes lookup API for id1087897068, accessed 2026-10-02.

On-site facts drawn from existing chinagateway.pro content: WeChat Pay merchant, WeChat Official Account, WeChat Pay for Foreign Companies, WeChat Ecosystem Service.

Scope-guard claims — that the international site serves a JavaScript shell and that registration documentation is Chinese-only — trace to our own fetch of https://work.weixin.qq.com/nl/international during wave-5 research, accessed 2026-10-02.

This page deliberately excludes any claim not traceable to one of the sources above. Registration paths, pricing, verification timelines, and API specifics for foreign companies are excluded because no citable English-language primary covers them at a precision level we would publish under our name.