Guide · Operations Center
The Operations Centre holds the overview and asset entry points; account, WeCom and WeCom service desks hold deep operations for an entry point; webchat handles XApp development; each XApp's Admin only manages that app. Find the boundary of responsibility first, then open the right page.
The Control Plane
The entry point is /page/admin/tenant_center.htmlUse it to read operating data, account assets and creation or management relationships, and to jump to the right deep-configuration page. Do not mistake management permission for financial ownership.
Lifetime and last-30-day revenue, withdrawable and withdrawn, order status, total users and 7-day activity, conversations and messages, agent token pool, XApp token pool, and counts of accounts, WeCom, service desks, XApps and products.
Revenue and usage are attributed to the account's creator; managed objects are not mixed into financial ownership. Revenue counts only orders actually paid. Agent and XApp tokens are separate pools — XApp subthreads are not double-counted in the agent pool.
You may hold management rights, enter the console and help operate it, but orders, revenue and creator identity are computed by the backend from the ownership relationship. The front end must not calculate them itself.
Where To Go
Ask "what am I managing" first, then pick the console. The map below is the shortest route for ongoing operations, not an exhaustive feature list.
WeChat Official Account
Enter from My WeChat Official Accounts in the Operations Centre. Create or connect the account, check the self-test, manage administrators and basic info, then finish deep configuration in the console.
Read messages, tokens, edge cases and menu sync status; configure conversation strategy, model, output delivery and quota. When something is wrong, go back to the message log and the entry-point connection state — do not just edit the prompt.
Assistant templates, wizard, basic info, persona, service rules, memory, knowledge, FAQ, edge cases, failure fallback, skill apps, hot words and the operation log together form a maintainable service role.
The WeChat menu configures service entry points; products and entitlements manage products, VIP resources and resource objects; the order centre tracks fulfilment; the user list locates account users. Amounts and licensing are computed by platform commerce, not decided by the page.
Manage templates, scheduled broadcasts, one-off broadcasts and event messages. For first follow, re-follow, QR scans and menu clicks, confirm the template and target audience before enabling a rule.
WeCom & Customer Service
The WeCom console manages shared capability; the service-desk console manages one employee's real service and conversation operations. Mixing them creates duplicate maintenance.
open_kfid code is used for API and message matching; the full kf_link code is used for attribution of entries carrying a scene;kfid_for_link code only opens the service window statically. They are not interchangeable.
Build & Operate XApp
Find the app under My XApps or XApps I manage in the Operations Centre, then open webchat or that app's Admin. Administrators can develop, configure, manage data and release, but cannot impersonate the creator's ownership; only the author can delete an app.
The app list creates and selects; file management handles code, public assets and private resources; data management handles logic tables, fields and records; Preview opens the development build, Run opens the released version; the settings drawer manages basics, administrators, access and the Admin entry.
Open webchat →The entry is usually /page/xapp/xapp.html?xapp_key=<app_key>&surface=run&entry=admincode. It is the author/administrator console for one app, provided the app actually exposes admin/index.html code and the current user has permission.
Workspace is the source of released code; asset is public material; resource is private material; products, VIP, resource objects and licensing are managed by commerce. Never conflate file paths, resource objects and user entitlements.
Save success, Preview working, Run released, payment working and WeChat sharing working are not the same layer of verification. Record the real state of each link instead of one "done" covering everything.
Native Mini Programs
In Operations Centre → WeChat Mini Program, choose the account and complete registration, domain allow-listing and binding a released XApp with the wizard; the Developer Centre shows projects and source versions and issues the WorkBuddy builder. Native pages use the SDK for enabled capabilities; verify source versions and the actual WeChat release state separately.
Enter and verify the mini-program AppID / AppSecret, then enable data, text agent, product membership and authorised file capabilities as needed. When connection fails, check the real binding, credentials and enabled state.
Open the mini-program list →Check the project AppID, use the builder to get the SDK and styles, save private source, pin a version and export. WeChat preview, upload, review and release happen on the WeChat side.
Read the full mini-program guide →A Practical Route
Prepare a verified account with developer interface permissions, then complete the platform self-test in the Operations Centre wizard.
Connect an account →Organise material first, then finish modular configuration and real WeChat testing with the agent guide.
Go to the agent guide →Use the XApp guide to build forms, assessments, records, courses or private-resource delivery, and release in stages.
Go to the XApp guide →Return to the overview and read revenue, orders, users, conversations and the two token pools by creation ownership.
Open the overview →Keep choosing by goal: configure the agent → make a deliverable XApp → catch users and business in the Operations Centre. Next, return to your own entry point and let real questions drive small iterations.
