User ManualApplication v1.0.12 (development channel)
About this document
The facts below are the ones a reader needs in order to judge whether this copy still matches the app on their phone.
How to read the status labels
Every feature carries one of three labels. They are not decoration; they are the difference between a manual you can act on and one you cannot.
| Label | What it means | What you should do |
|---|---|---|
| LIVE | Working in the released version | Use it as described |
| PARTIAL | The entry point and the screen exist; part of the data behind them is still being connected | Use the part that works — the text always says which part that is |
| PLANNED | Specified and designed, not shipped | Do not build a workflow on it yet; the manual gives you the workaround |
Contents
Conventions
- "You" is the reader — a member, an operator or a trainer. The platform says "we" only when it is stating what it does or does not do.
- Screen paths are written as
Me → Settings → Language, following the labels on screen. - Names, companies, amounts and posts in the screenshots are sample data. None of them is a real member or a real transaction.
- Feature status is governed by Chapter 6. If the body text and Chapter 6 disagree, Chapter 6 wins — we would rather understate.
0How to use this manual
This is not a button reference; it is a decision manual. For every feature we answer four questions — why it exists, what problem it solves, how to operate it, and what it is worth to you.
Four kinds of reader, four routes. You do not have to start at page one:
| You are… | Start here | What you will have at the end |
|---|---|---|
| A member opening the app for the first time | Chapter 2 → 3.1 → 3.2 → 3.6 | Your profile filled in far enough to be trusted, and a clear idea of how others find you |
| Someone looking for resources or partners | 3.2 → 3.3 → 3.4 → 3.7 → Chapter 4 | A fixed routine from search to closed deal, so you stop reinventing it every time |
| A chamber officer or operator | 3.9 → 3.10 → 3.11 → 3.12 → Chapter 6 → Appendix C | An understanding of the back-office data, events, communities and tasks, plus a monthly SOP you can follow as written |
| A trainer | Appendix D → Chapter 2 → Chapter 4 → 3.13 | A 90-minute course outline, group exercises, an assessment sheet and a 30-day follow-up design |
| Anyone inviting people who are not on WeChat, or who care about language | 10.1 → 10.2 → 10.6 | Knowing when to send a mini-program code and when to send an H5 link, and what a language switch does and does not change |
Three ways to read it
- Read the purpose before the procedure. If you already know what a feature is for, skip the operating steps — this is a manual to consult, not to memorise.
- When you see PARTIAL, turn to Chapter 6. One column there is called "what you can do today": the alternative route that still gets the job done.
- To persuade someone, go straight to the comparison table in 1.5. It sets out, in five dimensions, why a WeChat group is not enough.
How this document may be forwarded
Three uses, three audiences. Choose by occasion; do not drop the whole book into a group chat:
- For someone considering joining: send Appendix B, the one-page sheet plus Chapter 1. They want to know what is in it for them, not how the buttons work.
- For someone who joined but cannot get going: send Appendix A, the seven-day card plus 3.2 and 3.6. They are stuck at "my profile is half-empty and nobody answers".
- For chamber officers and operators: send the whole document and point them at Appendix C. They want to know how to run this population.
1Product overview
WeaveInX is a business network where trust is the medium of exchange. It does not solve "know more people"; it solves "know the right people, and leave evidence that you did".
1.1 The problem we solveWHY
Traditional business networking suffers three structural losses, which together are what we call wasted networking. None of them is an attitude problem; all three are tool problems — nowhere records "find the person, judge the person, remember the deal".
| Loss | What actually happens | What it costs | What the platform does |
|---|---|---|---|
| Cannot find | You leave a 200-person event with a stack of cards and cannot find "the one who does cross-border logistics". | The opportunity happens on site and dies in the car park | Member directory plus five filters |
| Cannot judge | Someone introduces a partner who "knows everyone", and you have no way to check. | Three dinners and two months to find out | Member detail, trade reviews, Radar Score |
| Cannot keep | The deal goes well and leaves no record anyone can cite. Move city and you start from zero. | A network that cannot compound, let alone be handed on | Trust Wall, Case Fingerprint, Pulse Chain Map |
1.2 PositioningWHAT
"End wasted networking. Start precise matching." — turn every real connection into a relationship asset that compounds, can be verified, and can be passed on.
That sentence breaks into three working claims, and they are the three pillars of the product:
Networks become assets. A network is no longer an impression of "who you know" but an asset with dimensions, a score and records: how many degrees away, what you have contributed, who vouches for you.
Trust is the currency. The Trust Wall, trade reviews and Case Fingerprints turn verbal credit into something you can show. The thicker the trust, the further the same sentence carries.
AI is the capability lever; your network is the relationship lever. AI multiplies output, the network multiplies opportunity. A company of one scales only when both levers are pulled.
Five bottom tabs and thirteen modules turn the three claims into daily actions: who → why trust them → how to work together → what is left behind.
The third claim is the easiest to write beautifully and leave empty, so we spell it out: in this system AI is not a chatbot but four specific positions. Two are live and two are still being built; the table says which is which — you should not pay for what is not finished, but you are entitled to know where it stands.
| Position | What it does for you | Status | What you can do today |
|---|---|---|---|
| AI Assistant | You ask, in the chat box, "I want to reach someone in Southeast Asian logistics — how do I open?" It gives you a direction and a script. | PARTIAL | The entry point is open and chat works. Answers that name specific members and give matching reasons are still being built — treat it as an adviser, not a search engine. |
| AI match card | On a member's detail page, it lists "three people you may want to meet" with reasons. | PARTIAL | The entry point exists; the reasons and the ranking are being sourced. Meanwhile use the industry / region / level filters in 3.2. |
| Industry matching advice | Produces an actionable list of directions from your supply-and-demand posts and your industry. | LIVE | Available from the tool box and the dashboard entries. The output is advice; you still judge and make contact. |
| Content assistance | Drafts supply-and-demand descriptions, feed posts and self-introductions. | LIVE | Every draft is yours to approve. The platform never publishes on your behalf. |
1.3 The whole mapHOW
The application is built on five bottom tabs as the main line, with three floating shortcuts and a tool box as side lines. The dot at the top right of each block is its status (green live, amber partial, grey planned):
1.4 Who it suitsWHO
| Role | Their pain | Where they live inside the app |
|---|---|---|
| Company of one / solo professional | No brand department, no BD team; the network is the only sales channel | Me (personal brand page) · Supply & Demand · Opportunity Plaza |
| Chamber or association officer | Membership in Excel, sign-ups in a group chat, nothing accumulates | Members · Events · Communities · data dashboard |
| Professional service provider (consultant, coach, lawyer, designer) | Strong at the craft, invisible to search; trust travels by word of mouth only | Member detail · trade reviews · Trust Wall |
| Cross-strait or cross-border operator | Every new city means rebuilding the network, and you cannot check the other side | Native-place and region filters · Supply & Demand · Pulse Chain Map |
| Event organiser | Sign-up, payment, check-in and follow-up are all manual | Events (publish / sign up / check in / data) · tool box |
1.5 Compared with the old wayWHY NOT
The usual objection is "I can do this in a WeChat group". You can, except for four things. This table does not say groups are useless; it says they have no memory:
| Dimension | WeChat group + business cards | WeaveInX | What changes |
|---|---|---|---|
| Finding | Memory and scrolling back; useless past 200 people | Five filters: name, nearby, native place, level, industry | From "who can I remember" to "what do I need" |
| Verifying | Ask a mutual friend, read their Moments, guess | Radar Score, trade-review tags, citable cases | From "feels reliable" to "on record" |
| Recording | The deal closes and the conversation drowns | Closed supply-and-demand post, review, Case Fingerprint | From one-off to citable |
| Compounding | New phone, new city, new industry — back to zero | Pulse Chain Map and Trust Wall follow the account | From "out of sight, out of mind" to portable assets |
| Reach | One-to-one messages, one person at a time | Public supply-and-demand posts visible to all members | From point-to-point to one-to-many |
1.6 Membership levels and entitlementsthe conversion point
Membership level is the most-seen and least-explained field on the platform. It is a filter in the member directory, an entry requirement for events, and the source of permissions in communities. First, one clarification:
| Tier | Usually who | How it is obtained | What it changes in the app |
|---|---|---|---|
| Member | Ordinary members and company representatives who have joined | Apply → approved → dues paid | All basic functions; can attend Gatherings; listed with ordinary status |
| Adviser | Senior members, professional consultants, trainers, referred resource holders | Nominated by the chamber, or applied for and reviewed | Can attend Convergence-tier events; can be reached first through the level filter; can take adviser assignments |
| Regional council / chapter chair | Organisers and core officers of a region or chapter | Appointed by the council | Can publish Convergence events; can manage communities and members; sees the operator-level dashboard |
Four things a level actually changes
- Ranking: under the same search, higher levels usually come first. That is what the chamber wants (officers are seen first), and it is the visibility you are competing for.
- Event threshold: events come in four tiers — Small Circle (≤8) / Gathering (≤20) / Mid Gathering (≤40) / Convergence (no limit). The higher your level, the larger the room you can open; Convergence is usually initiated by advisers and above. When your level is not enough, the screen tells you what is missing.
- Community permissions: some communities are restricted by level or by identity; see 3.11.
- Entitlements and price: some services in the Mall and some event fees have a member price; the product page or event page governs.
Me → Member profile; the level field shows your current status. To upgrade, go through Members → Apply / Dues, or simply ask the administrator of your community. Final interpretation of levels and fees rests with your chamber; the platform only presents them.
1.7 Crossing cities and borders: your network does not resetcross-strait
This is the most underrated section of the product, and the hardest for a WeChat group to replace. Ordinary business communities serve "people in the same city"; this platform assumes people move — a team from Taiwan landing in Xiamen, a Xiamen firm taking orders in Southeast Asia, officers shuttling between cities. The moment you move, three things break at once:
- You cannot find them: the person you met in Xiamen is a card in a drawer, and you do not know when they will be back.
- You cannot check them: across the strait, "I know everyone locally" is unverifiable, so you fly over.
- You cannot take it with you: move city and the trust and records stay behind.
When you cross a city, these four fields matter most
| Field | Why it matters | How to use it |
|---|---|---|
| Base city | "Nearby members" and the region filter both depend on it; put your household registration and you will never be found | Put the city where you actually spend most time. If you split your time, put your main base and say in your introduction when you are in the other place |
| Native place | Across the strait, a shared hometown often builds first-layer trust faster than a shared industry | When you need an opening, filter by native place and your first sentence has something to stand on (see 3.2) |
| Can offer / looking for | The most expensive thing in cross-city work is information asymmetry; this is the only public place to close it | State the territory: "agent for South China", "Southeast Asia freight", "can host Taiwan teams landing in Xiamen" |
| Itinerary | "When will you be in my city" is the most asked and least answered question in cross-city work | The itinerary tab is not live; meanwhile put it in a feed post or say it in the first message (see 3.6) |
Three moments, one action each
- Three days before you travel: filter by region for the city you are visiting, pick five people, send each a three-sentence message (template ④ in 3.3). Not "I am in Xiamen next week, can we meet" but "I am in Xiamen Wednesday and Thursday; I would like to ask about [one specific thing]; twenty minutes is enough".
- The day you land: post "I am in [city] now" as a feed item or a supply-and-demand post. It is the cheapest, highest-hit exposure you will get — locals come to you because you are rarely there.
- Within 48 hours of returning: the step most people skip. Leave the review that day, post one supply-and-demand item, and write the new contact into your Trust Wall (see 3.13). Without this step the relationships from the trip expire within two weeks.
2Five minutes to a usable account
On first use there are only four things to do: get in, sign in, fill the profile in far enough to be trusted, and learn three shortcuts. Do those four and you are already easier to find than most members.
First the whole path. The three screens below are the compulsory steps; done without hesitation they take about ninety seconds — not counting the time you spend deciding your one-line positioning:
2.1 Getting in
Three ways, same result, but a different relationship is created — a point rarely made clear:
What the inviter gets when you scan
Many people are embarrassed to ask someone to scan, because they cannot say what the other person gets. Saying it plainly makes it easy. The inviter gets three things:
- A traceable referral record — you are recorded as their L1 (direct referral) and written into the Pulse Chain Map. It is never overwritten.
- A referral count and contribution record — counted in the referral dimension of the Pulse Chain index and in the contribution total of Pulse Credits.
- A starting point for your own trust — later, when you ask them to vouch for you, they know who brought you in. That is worth far more than a self-introduction.
official code to be inserted here
2.2 Signing in and verifying
What to have ready for verification
| Have ready | How exact it must be | Why |
|---|---|---|
| A phone number that receives SMS | Registered in your own name, able to receive a code immediately | The unique identifier for the account and the way back in |
| Your real name | Exactly as on your ID; no English name, no title | Bound to the referral record. You can display a nickname separately |
| Full company or organisation name | The registered name, not the short form | Lets others judge your industry and scale; also the basis for industry filters |
| Base city | Where you actually spend most time, not your registered address | "Nearby members" and cross-city matching both depend on it |
2.3 Filling it in to the point of being trusted
This is where most people stall: the profile is not complete, so they feel they should not use the app. There is an order of priority — fill first the fields that affect being found and being trusted:
| Order | What to fill | Why in this order |
|---|---|---|
| 1 | Main business, plus can offer / looking for | Supply and demand is the core of matching. Say what you can give and what you need, or nobody can refer you. |
| 2 | Work history and education | The second source of trust after "who brought you": professional context. |
| 3 | Products and services, certificates | Turns invisible expertise into items and proof you can show. |
| 4 | Avatar and one-line positioning | The list page shows only the avatar and one line; this is what decides whether anyone taps in. |
Below are templates you can copy. Fill in three sentences and your profile goes from "a stranger with a name" to "someone I could introduce tomorrow":
2.4 The home screen
1
2
3
4
5
The home screen is five blocks, deliberately ordered to "first make you believe what this is, then send you somewhere":
| No. | Block | What it does |
|---|---|---|
| 1 | Brand carousel | The one-line claim: "a business matching platform for Chinese speakers worldwide". Swipe sideways for more images; the dots at the bottom left show how many. |
| 2 | Network radar map card | The highest-converting card on the page — "who is nearby, sorted by distance, filter by radius", with "Open" on the right. Tapping it goes straight to the network radar. |
| 3 | Eight-tile shortcut grid | The eight most-used actions (Table 2-4). The two dots below mean it swipes to a second page of entries. |
| 4 | Brand banner | "Welcome to WX脈鏈鏈 / connect with trusted partners, create value together". The "中文" box at the top right is one of the language entries (see Chapter 10). |
| 5 | Floating buttons and tab bar | Left ball: functions / assistant / plaza. Right ball: AI matching / plaza. They never scroll away, so AI and the plaza are always one tap from anywhere. |
Where the eight tiles lead
The grid is a shortcut that bypasses the tab bar. The table maps each tile to a chapter and says whether you should tap it at your stage:
| Tile | Leads to | How to use it as a new / growing / established member |
|---|---|---|
| About WeaveInX | Chapter 1 | Read this first as a newcomer: understand what the platform does before deciding how much to invest |
| Member map | Figure 11-13 | Before a trip: see who you know in the destination city |
| Digital business card | Figure 11-23 | At any stage: send your card out, or look at someone else's |
| Communities | Figure 11-25 | Growing stage: join a small room — it beats shouting in the main square |
| Contacts | Figure 11-22 | Established stage: once the conversations pile up, manage them here |
| Supply & Demand | 3.4 | Your main tool while growing: make the need public so others have a reason to find you |
| Events | 3.10 | The best value for a newcomer: one Gathering beats ten messages |
| Event sign-up sheets | Chapter 12 | When you are organising: publish, review, check in — one line |
2.5 The tab bar: five entries, five intentions
The five bottom entries are not five features but five intentions. Once you see them that way you stop getting lost:
Five places a newcomer gets stuck
| Where you are stuck | The real reason | What to do |
|---|---|---|
| "My profile is incomplete, I dare not use it" | Treating all fourteen fields as mandatory, then giving up | Fill only the four priorities in 2.3; add the rest when you need them |
| "I do not know how to open" | Afraid of intruding, afraid of being left on read | Use the three sentences in 3.3: context, specific request, equal value |
| "I posted a need and nobody replied" | The title is a job title, the description has no boundaries, no tags | Rewrite it using the example in 3.4; put the outcome in the title |
| "I cannot find the person I need" | Searching by name only; never using the filters | Use the five dimensions in 3.2: industry → region → level |
| "I added people and nothing happened" | Names in a list, no next action | Work through Appendix A, the seven-day card |
Me → Edit profile. It raises the chance of being found more than any other single step, and it is the only one that needs nobody else's cooperation.3The thirteen core modules
Every section follows the same structure: purpose (why it exists) → meaning (what it changes) → functions (how to operate it) → value (what you get), ending with "if you only have one minute". Read only the section you need now.
The thirteen sections need not be read in order. Three labels tell you whether to bother: ESSENTIAL marks the four everyone needs; OPTIONAL means read it when the situation arises; OPERATORS is for chamber officers and organisers only.
| Order | Module | Class | When to read it |
|---|---|---|---|
| 1 | 3.1 Home | ESSENTIAL | Day one. Work out where everything is |
| 2 | 3.6 Me | ESSENTIAL | Day one. Turn your details into a version someone can introduce |
| 3 | 3.2 Members | ESSENTIAL | Week one. Learn to find people, and see how others write theirs |
| 4 | 3.4 Supply & Demand | ESSENTIAL | Week one. Post your first need — this is where inbound starts |
| 5 | 3.3 Member detail and messaging | OPTIONAL | Before you contact anyone for the first time |
| 6 | 3.8 Pulse Chain Map and radar | OPTIONAL | When you want to audit the shape of your network |
| 7 | 3.10 Events | OPTIONAL | When you want to attend or to organise |
| 8 | 3.7 Opportunity Plaza | OPTIONAL | When you have no specific target and want ideas |
| 9 | 3.13 Trade reviews | OPTIONAL | The day a deal closes — important, do not postpone |
| 10 | 3.11 Communities | OPTIONAL | When you want your own kind, or need someone to vouch for you |
| 11 | 3.5 Mall | OPTIONAL | When you want to redeem credits or buy a service |
| 12 | 3.12 Tasks and Pulse Credits | OPTIONAL | When you want daily actions to accumulate into entitlements |
| 13 | 3.9 Dashboard and tool box | OPERATORS | You are a chamber officer, organiser or operator |
3.1 HomeESSENTIALfirst impression
Let a first-time visitor know within ten seconds what this is, what it has to do with them, and where to tap next.
The home screen is the shopfront and the place where value is declared. It establishes "a network is an asset" first, which is what makes everything behind it persuasive.
Brand key visual, notice carousel, eight-tile shortcut grid, member feed, three floating shortcuts.
A new member does not have to explore: any main function is within three taps. A chamber can use the notice slot for immediate mobilisation.
The same home screen reads completely differently to three kinds of people. That is why the order of the blocks is not arbitrary:
| Role | First thing they do here | Why |
|---|---|---|
| Ordinary member | Look at the grid and ask "which tile have I never used?" | The value of the home screen is not browsing; it is reminding you what else is available |
| Event organiser | Check the notice slot and how warm the feed is | The notice slot is the highest exposure on the platform; the feed decides whether anyone sees your event this week |
| Chamber / operator | Check whether the notice is current and whether the feed has content | The home screen is the only evidence that this community is alive. Three days without an update and members stop opening it |
How to operate it
3.2 Members (member showcase)ESSENTIALfinding people
Turn a stack of business cards into a live directory that anyone can search, filter and open.
This is the platform's most basic asset: how structured the member data is determines how precise matching, referral and brokering can be.
Search by name, nearby members, native place, membership level, industry category; four views (member / unit / company / group); apply to join, pay dues.
Finding one specific resource goes from "ask three groups and wait two days" to "type a keyword, thirty seconds".
Five filters
| Filter | When to use it |
|---|---|
| Search by name | You already know who you want — most often after a referral |
| Multi-dimensional filter | Cross four conditions (level, industry, region, distance); it tells you how many results before you commit |
| Nearby members | Business trips, trade fairs, a meeting arranged at short notice — start with the same city |
| Native place | Cross-strait and cross-border: a shared hometown builds first-layer trust faster than a shared industry |
| Membership level | When you need decision-makers or adviser-level resources |
| Industry category | Vertical search for partners (logistics, education, green energy, cross-border e-commerce…) |
The Radar Score on each card is an entry point, not a verdict — it tells you how much verifiable record this person has accumulated. Open the profile for the detail.
Five checks before you ask to be referred
The "golden formula" is about how to write. This is about whether you can actually be referred. Pass all five and others can introduce you:
- ① You can say who you are in one sentence — without reading your profile, can you explain in fifteen seconds who you help and with what? If not, nobody remembers.
- ② "Can offer" is a noun, not an adjective — "a list of twelve factories in South China" can be referred; "well connected" cannot.
- ③ "Looking for" has boundaries — volume, region, timing or budget, at least one of them. Otherwise nobody knows whether to introduce you.
- ④ There is something to open — a product page, a case, a certificate, a video: at least one. Without it you can only be judged in person.
- ⑤ Someone can vouch for you — at least one trade review. Zero reviews is not bad, but it does mean "nobody has proved it yet".
The operator's view: getting a whole group online
The question chamber officers ask most: "I have three hundred members — do I have to call each one?" No. There are three standard routes and they combine:
| Route | How | Suits | Watch out for |
|---|---|---|---|
| Import a roster | The chamber imports its member list (name, phone, organisation, title) in the back office; the system creates accounts awaiting activation | Chambers with a complete Excel roster | Confirm the roster was lawfully obtained and tell members what it is used for (see Chapter 9). Entry point and fields follow the chamber back office |
| Personal code / poster | Each officer or member gets a poster carrying their own code; scanning it creates the referral relationship automatically | At events, forwarded in groups, one-to-one invitations | The relationship is recorded permanently — never scan on someone else's behalf or pad referrals |
| Scan at the door | A standee at the registration desk: signing in registers the account and can attach the event automatically | Small Circle, Gathering, Mid Gathering, Convergence | Someone must walk each guest through thirty seconds; a standee alone works half as well |
How to operate it
3.3 Member detail and messagingESSENTIALjudging
Give you enough material — checkable material — to answer "should I work with this person".
It compresses the cost of three dinners' worth of verification into one page. This is the platform's central trust design: see the evidence, then decide whether to spend time.
Basic profile (main business and secondary lines, company, base city, chamber), can offer / looking for, market, trust, feed, itinerary; message from the bottom bar.
Lower cost of misjudgement: you can decide whether this person can solve your problem without meeting first.
How to read this page
| Block | What to look at |
|---|---|
| Three metrics | Visitors (how many looked at them unprompted), trust likes (how many vouch for them), shares (how many were willing to pass them on) |
| Six tabs | Profile / work / education / skills / video / articles — check "profile" for fit first, then "articles / video" for what they have actually done |
| Voice introduction | People who recorded one feel noticeably more trustworthy; a blank shows "no voice introduction yet" |
| Shared chain | Whether you share a referral source — if you do, your first sentence has a reason to exist |
The thirty-second check
Before deciding to spend time, look at these five in order. If the first two do not fit, stop — that saves both of you:
- ① Do your needs complement? Does their "can offer" match your "looking for"? If not, stop here.
- ② Is industry and geography workable? Same industry but 1,500 km apart — price the cost of cooperation in first.
- ③ Look at what makes up the Radar Score, not the total — a high score with no cases is more suspicious than a middling score with three.
- ④ Is anything moving recently? Someone whose feed stopped six months ago usually replies slowly.
- ⑤ Shared context — a common L1, an event you both attended. If so, your first sentence has an opening.
Three sentences for a first message
A direct message has one job: let the other person decide within ten seconds that it is worth answering. Three sentences is enough; the fourth is usually surplus.
What if they do not reply
This is the biggest psychological barrier in messaging. The conclusion first: no reply is not a rejection, it is a question of priority. Work through the three steps below and do not keep chasing:
3.4 Supply & DemandESSENTIALmatching
Turn "this is what I need" into a public, searchable request that others can answer, instead of something buried in a chat log.
This is the only module with two-way exposure: you post once and every member sees it; someone else posts and you see it. It is how weak ties become strong ones.
Four states (all / recruiting / closed / my industry), posting a need (title, description, tags, region, deadline), view counts and shares, moderation.
The life cycle of a need becomes visible: from recruiting to closed, which is social proof that deals really do happen here.
The title decides eighty per cent of the outcome
| Style | Example | Result |
|---|---|---|
| Job title (worst) | "Logistics partnership" | Nobody knows what you want, at what scale, by when — nobody can respond |
| Need (middling) | "Looking for a Southeast Asia cross-border logistics partner" | The direction is clear but the scale and terms are not, so most replies are fishing |
| Outcome (best) | "Looking for a cross-border e-commerce logistics partner (SE Asia, 3 containers/month, from Q1)" | Readers know immediately whether they fit; most replies can actually be negotiated |
Two complete examples (different industries, editable)
How to operate it
3.5 MallOPTIONALentitlements
Turn the services of the platform and its members into products with a price, an order and a delivery, rather than favours.
A business community's value usually stops at "networking". The Mall pushes it to "transaction" — the step from community to commercial loop.
Categories and product detail, cart, ordering and payment, order lookup, refund requests, delivery addresses.
Corporate services (in-house courses, consulting, delegation places) can be bought directly, and a member's expertise can be listed as income.
The purchase path
Five steps: add to cart → choose quantity → confirm the order → pay → order detail. To return something, open the order from "My orders", choose "Request refund" and complete the fields the product type requires.
| Product type | How it is delivered |
|---|---|
| Corporate services / courses | The provider contacts you to schedule; redeemed against the order |
| Event places | Wired to the Events module; signing up creates the order |
| Physical goods | Delivery address entered, shipped |
Payment, invoicing and refunds: the three questions asked most
| Question | In practice |
|---|---|
| How do I pay | Start payment from the order page and complete it with WeChat Pay. The payment page shows the actual receiving entity — read it before confirming. If the platform collects, the payee is the operating company; if the merchant collects directly, the payee is that merchant. This step protects you. |
| Can I get an invoice | Yes, issued by whoever actually sells (the platform for platform products, the merchant for merchant products). Request it from the order detail, giving the invoice title and tax number; electronic invoices usually go to the address you leave. The flow and timing shown on the order page govern. |
| Can I get a refund | Depends on the product. The product or order page states whether it is refundable and for how long. If it is, use "My orders → Order detail → Request refund". Services already redeemed and courses already started are usually not refunded, or refunded pro rata, per the product description. |
"Can I list something?"
Yes, and the barrier is not technical but a question of delivery capability. The requirement is that you dare to write it as a product: defined deliverables, price, timeline and refund rules. Prepare four things:
- ① A delivery list: after the buyer pays, what exactly do they get? How many meetings, how many pages, how many places?
- ② Price and tiers: unit price, group price, member price — at least two tiers thought through.
- ③ Delivery period: how many days after payment it starts, how long it takes.
- ④ Refund rules: what qualifies, at what proportion. A product that does not say will not pass review.
Me → Feedback or contact your chamber officer; the operator reviews the item and the copy. The Mall currently focuses on platform-run and chamber-partnered services; individual listings are reviewed case by case.3.6 MeESSENTIALyour brand page
Upgrade "Me" from a list of functions into your personal brand page: your assets, your work, your credit, on one screen.
In a business community, this page is your shopfront. It is both your own back office and other people's summary of who you are.
Pulse Credits asset card (balance, check-in, redeem, statement), fourteen tiles (profile / experience / education / skills / products / certificates / dues / joining / video / articles / notices / FAQ / settings / feedback), Trust Wall, dashboard and plaza entries.
A digital CV and credit file you keep updating, which travels with you across cities and industries.
You need not fill all fourteen. Ranked by "does this affect being found and trusted", only four are critical; the rest are bonuses:
| Priority | Tile | What it affects | If left empty |
|---|---|---|---|
| Critical 1 | Profile (main business + supply and demand) | The only basis for being searched, matched and referred | You effectively do not exist in the directory; only hand introductions reach you |
| Critical 2 | Products / services | The concrete evidence of what you can do | Only a job title remains, and half the persuasion is gone |
| Critical 3 | Certificates / qualifications | Verifiable proof of expertise, and the source for certificate lookup | You have to earn the trust in person instead |
| Critical 4 | Articles / video | Your portfolio — it lets people see what you have done | They can only imagine your capability |
| Bonus | Experience, education, skills, dues, joining | Adds context and identity | Minor, but the profile reads thinner |
| Tools | Notices, FAQ, settings, feedback | Administration, not display | No effect on visibility |
Three things to do immediately
How to operate it
3.7 Opportunity PlazaOPTIONALdiscovery
An entry point that is not search, so you meet the people and chances you did not know you needed.
Search only finds answers you have already thought of. The plaza uses randomness plus curation to manufacture accidental connections — the part of a community an algorithm cannot replace.
"Random members" with a shuffle (every shuffle is a new encounter) plus an opportunities feed (revenue share, equity, course-fee splits and similar).
Cheap expansion of weak ties; for someone who has just joined and has no clear target, it is the best starting point.
Worth taking on? Three tests
| Test | Ask yourself |
|---|---|
| ① Are the terms written down | Revenue split, settlement cycle, who carries the cost — if one of the three is missing, do not rush to negotiate. An opportunity that only says "to be discussed" usually works against you. |
| ② Can I take only a slice | A good opportunity allows partial cooperation. One that demands your full-time commitment without matching terms is usually hiring, not partnering. |
| ③ Does the poster have a checkable record | Open the poster's page: reviews, cases, activity. All three missing means treat it as advertising for now. |
How to use the plaza
Treat it as two minutes of card-turning a day: read three opportunities and ask "could I take a slice of this", then draw three random members and see whether anyone is worth a hello. The value is not in finding the single best one — it is in letting the system learn what you look at. Who you tap and where you pause shapes what it shows you next.
How to operate it
3.8 Pulse Chain Map and indexOPTIONALnetworks as assets
Turn your network from a feeling into a visible structure and score, so the asset can be audited, inspected and improved.
This is the platform's most distinctive design: referrals are traceable and never overwritten. Who brought you in, and whom you brought in, stays on the chain.
The map itself (a referral tree you can zoom and drag), the index (a seven-axis score), the system view (size at each level), adviser assignments.
Turns "I am well connected" into a number that can be checked, and gives every referral a record and a return.
Four views, four questions
| View | What it answers | When to open it |
|---|---|---|
| Chain tree | Who sits below you and who sits above (the up/down structure) | When you want to see who built that line |
| Cloud relations | How this group clusters (density and grouping) | When you want to see which cluster is most alive |
| Referral rings | Who is closest to you (referral distance) | The everyday view; when you need someone to introduce you |
| Full chain rings | The layered distribution of all relations, including non-referrals | When you want the overall shape and scale |
The numbers actually on screen: chain 1 107, chain 2 41, chain 3 25, chain 4 and beyond 186 — 359 in total. That 359 counts people on the chain; it is smaller than the 612 in "my network" (Figure 11-8). The difference is members who registered themselves with no referral source.
The seven axes: seven things you can do
| Axis | What makes it up | How to raise it |
|---|---|---|
| Profile completeness | Whether all eight profile items are filled under your real name | Complete basics, work, education, skills |
| Active presence | Sign-ins + shares + card visitors | Check in daily; share your card |
| Content creation | Number and interaction of supply-and-demand posts, articles and videos | One post a week beats ten sentences a day |
| Hosting events | Sessions you have organised | One Gathering of 6–10 people starts earning points |
| Attending events | Sessions you signed up for and checked in to | Actually turn up — only check-ins count |
| Connecting others | Introducing people to the right person; being referred | Make one introduction; both sides gain |
| Trade reviews | Reviews of completed deals (F1) — not live yet | Shown honestly as 0 and excluded from the average; it will move once live |
Relationship levels: what L1, L2 and L3 mean, and how to use themthe app calls it "chain N"
The map expresses distance in layers: L1 is someone you referred directly, or who referred you directly; L2 is one layer away; L3 is two. The closer the layer, the thicker the trust base and the higher the chance a referral lands. On screen this reads chain 1 / 2 / 3 / 4+ — L1 is chain 1, and so on.
| Level | Good for | Not for | How to ask |
|---|---|---|---|
| L1 | Asking for introductions, asking for a reference, proposing a partnership; also the person who should mediate if a deal goes wrong | Do not ask for five introductions at once — L1 capacity is finite social capital | "I would like to meet someone who does X. Who comes to mind? No problem if not." |
| L2 | Asking an L1 to introduce you; or meeting naturally at an event | Do not message an L2 saying "so-and-so sent me" — confirm the L1 actually agrees first | "Lin Borui mentioned you; he said you are working on Southeast Asia. May I ask one question?" |
| L3 | As a source of information (read their feed, their posts); watch first, then decide whether to approach | Do not skip two layers to ask for help — it rarely works and spends the intermediary's credit | Interact first (comment, share); talk about contact after three exchanges |
3.9 Data dashboard and tool boxOPERATORSthe operator's view
Give operators and chamber officers a view from above: is this community alive, where do people come from, do events work?
Community operations without data run on feel; with data you can answer "where should the next event be, and for whom".
Dashboard: sessions, attendance, gender, age, industry, region, time-of-day. Tool box: certificate lookup, surveys, contacts, event sign-up sheets, promo posters, albums, institution search, feedback.
Turns "running events" into a process you can optimise, and "serving members" into metrics you can measure.
How to use the four headline metrics
| Metric | What it decides | If it is low, check first |
|---|---|---|
| Registered members / partner institutions | Scale and ecosystem thickness | Whether only one invitation route is left; whether anyone guides people after import |
| Cumulative events / open needs | Liveness and matching heat | Whether moderation is backed up; whether events are too infrequent |
| Pulse Credits in circulation | Total contribution (internal economy) | Whether task rewards are too low; whether redemption items attract anyone |
| Average Radar Score | Overall trust level | Whether anyone prompts "submit a review after the deal" |
The dashboard also charts gender, age, industry, region and time of day. Use them before and after an event: read the audience structure before, the participation structure after.
The tool box: eight small utilities
| Tool | When to use it | Who it suits |
|---|---|---|
| Certificate lookup | Verify whether someone's qualifications (training, certification, awards) are genuine | Anyone about to sign or pay a deposit |
| Surveys | Collect needs before an event, satisfaction after | Organisers, chamber officers |
| Contacts | Find chamber contacts quickly | Chamber officers, secretariat |
| Event sign-up sheet | Quick sign-up for a small gathering without building a form | Hosts of Gatherings |
| Promo poster | Generate a shareable poster carrying your personal code | Anyone inviting anyone |
| Albums | Collect event photos to look back on | Organisers and attendees |
| Institution search | Find communities or institutions and their members | Anyone looking for a particular organisation |
| Feedback | Ask the platform for something directly — this channel is actually read | Everyone, support questions included |
How to operate it
3.10 EventsOPTIONALmeeting offline
Turn an offline gathering from "sign-up list in a group, clipboard at the door, everyone lost afterwards" into a process with records.
Events accelerate trust: one meeting beats ten messages. The platform connects before, during and after, so the meeting leaves something behind.
Four tiers (Small Circle 8 / Gathering 20 / Mid Gathering 40 / Convergence unlimited), publishing with four review states, sign-up and payment, capacity control, QR check-in, event data, attendee list, targeted invitations.
The organiser saves labour and attendees can still find each other afterwards; every event becomes a record and a step forward in a relationship.
Two views, two questions
| View | The question it answers | When to use it |
|---|---|---|
| List | "What is on this week?" | General browsing; checking time and fee before signing up |
| Map | "Which cities have something on?" | Before a business trip or holiday |
The small print on the list is worth reading: "same city (Taipei) first, then popularity — one rule for everyone, not an AI prediction". The ordering logic is public, not a black box.
From sign-up to check-in: five stages
| Stage | What happens | What attendees do | What organisers do |
|---|---|---|---|
| ① Publish | Complete 18 fields and submit for review | — | Field-by-field guidance in Chapter 12 |
| ② Review | Manual review; states are under review / published / rejected | — | If rejected, revise per the advice and resubmit (use "reuse" to copy) |
| ③ Sign up | The "non-member sign-up" setting decides who may register; paid events require payment | Check the level requirement and fee before tapping | Chase sign-ups, answer questions, remind the day before |
| ④ Check in | With check-in enabled, a QR scan completes attendance (self-service or administrator) | Show the event QR code, or scan the organiser's | Choose one method and run it at the door |
| ⑤ Settle | List, photos and attendance data stay in "My events" | Add WeChat or message afterwards; keep the relationship | Compare sign-ups with check-ins for the attendance rate (Figure 11-18) |
Choosing a tier (a decision table, not a size table)
| Your aim | Choose | Why | Risk of getting it wrong |
|---|---|---|---|
| Close a few concrete deals | Small Circle (≤8) | Within eight people everyone can finish describing their need, and you get your turn | Any bigger and it becomes a round of self-introductions |
| Build a themed community | Gathering (≤20) | A theme creates shared language; 20 is the ceiling at which everyone can still speak | Too broad a theme ("let's talk startups") turns into a mixer |
| Training, chapter meetings | Mid Gathering (≤40) | Needs a stage and a run sheet, but still allows named interaction | Above 40, question time is always too short |
| Open to the public, maximise reach | Convergence (no cap) | Numbers are set by venue and catering; suits forums and investment promotion | Numbers, venue and catering get hard to control |
| Policy briefing, rallying officers | Convergence + members only | Use "visibility = members only" to control the list | Non-members cannot see it, so reach is limited |
3.11 Communities (institutions)OPTIONALbelonging
Give one group — same hometown, same trade, same chamber — a space where they can gather, interact and be managed.
The platform is the main square; a community is a small room. Real cooperation mostly happens in small rooms, because those rooms have shared language and shared rules.
Community list (seven categories), community detail (members, introduction, entitlements), apply to join, shared chain, community chat, community board.
For members: belonging and your own kind. For operators: tiered management, so service can be targeted.
Three kinds of community, three purposes
| Kind | Why you join | When not to |
|---|---|---|
| Industry | Find peers to work with, find supply-chain partners, exchange industry information | If what you need is cross-sector resources — peers compete for the same clients |
| Regional | Land in a city, find local contacts you can actually meet | If you are only passing through; you will not interact |
| Thematic | Deep exchange on one topic (ESG, cross-border, AI) | If you are only curious and have nothing to do about it |
Cold start: the first thirty days of a new community
What kills a community is silence. The goal of the first thirty days is not headcount but getting everyone to speak at least once. Four steps:
3.12 Task centre and Pulse CreditsOPTIONALcontribution as mining
Turn behaviour that contributes to the platform into points that accumulate, so effort is rewarded and good behaviour pays.
Pulse Credits are not discount vouchers but a measure of contribution: whom you introduced, what you shared, what you completed, all settle into credits. They also give a "free user" a reason to become a contributor.
Daily tasks (check-in, visit three member pages, three interactions, share content, post a need), weekly tasks, achievement tasks, consecutive check-in bonus, redemption and statement.
Builds a steady habit, and converts scattered interaction into real entitlements (courses, consulting, places).
How tasks are designed (values are illustrative; the screen governs)
| Task | Reward | Frequency |
|---|---|---|
| Daily sign-in | +40 | Daily |
| Visit three member pages | +15 | Daily |
| Three interactions (like / comment / save) | +20 | Daily |
| Share content | +10 | Once a day |
| Post a valid need | +30 | Up to 3 a week |
The consecutive check-in bonus rises from day 1 to day 7 (+40 to +100) and resets on a missed day. It is deliberate gentle anchoring: two minutes a day in exchange for long-term accumulation.
What credits can be exchanged for
| Type | Typical items | Suits |
|---|---|---|
| Learning | Course places, online workshops, handout packs | Newcomers who want knowledge before合作 |
| Services | One-to-one consulting slots, document preparation, introduction assistance | People in the growth stage stuck on a specific problem |
| Occasions | Event discounts, priority seats at Gatherings, partial credit on delegation trips | Established members who want to raise the efficiency of meeting people |
The operator's view: can tasks be customised
Yes, but currently as an operator configuration, not member self-service. If a chamber wants a themed campaign ("complete three cross-city matches this month"), it can request it through the operator, who sets the task name, conditions and reward. Ordinary members see configured tasks and cannot add their own.
Packaging tasks as a 21-day habit
If you are a trainer or a community manager, run learners through this: days 1–7 only "check in + visit three people + post one need"; days 8–14 add "one message + one review"; days 15–21 add "one introduction + one event". After three weeks most people have formed the habit of opening it once a day — worth more than any reward.
3.13 Trade reviewsESSENTIALclosing the trust loop
Make "the deal is done" leave a record, and give the next deal something to stand on.
Reviews are the last mile of the trust circuit: with them trust closes the loop (cooperate → review → trust accumulates → better cooperation). Without them it is always a one-off transaction.
Submit a review (score + tags + text), reply to a review, update a review (within the window), aggregate tags (reliable / well resourced / professional).
Every serious delivery becomes leverage in the next negotiation.
How to write a review that is actually useful
| Style | Example | Value to the other person |
|---|---|---|
| Vague (worst) | "Nice person, pleasant to work with" | Equivalent to nothing; the next reader cannot judge |
| Specific (good) | "Solid follow-through, transparent pricing, told us a week ahead when delivery slipped" | Shows their strengths and their honesty |
| Verifiable (best) | "Signed in March, delivered 2 containers in April, within 3 days of the date; placed a follow-on order" | Gives the next reader a benchmark to compare against |
How to ask for a review gracefully
Most people do not write reviews because they do not know what to write, not because they are unwilling. Lowering the cost works better than raising the will. Three sentences:
Rewrite practice: three real examples
If you are a trainer, this section works as a classroom exercise; if you are a user, check whether you have written the left-hand version:
| As written | The problem | Rewritten |
|---|---|---|
| "Very reliable partner, recommended!" | No information; "reliable" cannot be checked | "Gave a cost breakdown before quoting, and when raw material prices rose mid-project still delivered at the original price. Rare." |
| "Pleasant cooperation, no issues." | The reader cannot tell what kind of work it was | "Helped us complete company formation and tax registration in Xiamen within six weeks; we only had to fly over once." |
| "Good product but a bit slow." | Emotion without facts; the other side cannot improve | "Quality matched the sample; delivery was ten days later than agreed (customs), and they told us in advance." |
4Three usage scenarios
Memorising features is useless; stringing actions together is what works. The three scenarios below cover about 80% of real use. Each comes with a flow diagram and step-by-step instructions — the diagram shows you the whole picture, the steps tell you what to do on the phone.
Scenario 1: I have just joined and have nothing Cold start
Here is an example under a pseudonym; you will probably recognise yourself in him. Mr Lin, 42, exports hardware fittings, has just joined the chamber. His first sentence was: "I don't know anyone here — nobody will read anything I post." Three months later he has 11 supply-and-demand posts, 4 reviews, and one eight-person Small Circle he ran himself. He did nothing clever — just the five steps below.
Scenario 2: I need one specific resource Precision matching
This scenario is for people who know exactly what they need. The key is step ④: most people only send one-to-one direct messages, and forget that a demand post is a one-to-many amplifier.
Scenario 3: I want to run an event Organiser
After the three scenarios: the deal path end to end
Lay the three scenarios on top of each other and you see one trunk road. This diagram is the whole book in one picture — whichever entrance you come in by, you end up on the same path:
The diagram has three uses:
- Diagnose where you are stuck — if you are always "seen" but nobody contacts you, the problem is "trusted" (go and collect cases and reviews); if deals keep dying at the end, the problem may be "chosen" (your demand description is not specific enough).
- Plan your day — three minutes a day on steps 1 and 2 (exposure and being found), seven minutes on step 3 (collecting cases), and only then go and talk.
- Persuade someone to join — these five steps are the entire value of the platform. When you explain it to someone, these five steps work better than a feature list.
5The three mechanisms
Three mechanisms carry the credibility of the whole platform: the Pulse Chain Index (where you sit on the chain), Pulse Credits (how much you contribute), and the Trust Wall (your evidence locker). Understand these three and you understand the rules — and you will know how to work hard in the right direction.
5.1 The Pulse Chain Index: turning relationships into a number you can look at
The index is made of seven dimensions — trust value, reliability value, activity value, referrals made, recommendations received, shares, and trade reviews — which in substance weight three kinds of behaviour: being trusted (reviews and endorsements), contributing (referring and sharing), and being present (logging in and interacting). The detailed definitions and the "three things this week" list are in 3.8; here we only explain the design principle.
5.2 Pulse Credits: a measure of contribution, not a discount voucher
Credits are earned through tasks and contributions (check-in, interaction, sharing, posting demand), and can be exchanged for courses, consultations, event seats and other benefits. They mean three things:
| Layer | Explanation |
|---|---|
| Behaviour | Gives a newcomer a starting point — "I know what to do today" — which lowers the cost of a cold start. |
| Economy | Forms a small internal economy: contribution → credits → benefits → more contribution. |
| Governance | Credits accumulated over time are evidence that you are an insider, and may later be used in community governance and priority access. |
5.3 The Trust Wall: your evidence locker
The Trust Wall is built out of individual collaboration cases. Each has a counterpart, a date and a case fingerprint (for example CASE-2026-0918-77A3). Its purpose is not to show off but to lower the other side's cost of deciding: when someone sees three traceable collaborations, their question changes from "can you do this" to "when can we start".
Who sees what
| Content | Who can see it | Note |
|---|---|---|
| Case summary (counterpart, date, tags, fingerprint) | Signed-in members of the platform | Lets others judge your track record; contains no contract value or detail |
| Review scores and tags | Signed-in members of the platform | Shown in aggregate, not as itemised personal data |
| Full review text | According to the visibility setting on the review | If the author chose anonymity or "both parties only", a third party cannot see it |
| Collaboration detail, amounts, contracts | The two parties only | The platform does not publish these and does not give them to the chamber |
Three ways to use the Trust Wall
- Before negotiating: send the link to your Trust Wall (or a screenshot) instead of saying "I am professional".
- When quoting: use a case to show "I have done exactly this three times" — more persuasive than cutting your price.
- When questioned: produce the case fingerprint and let them look it up themselves. That works better than any explanation.
5.4 Four common failure patterns What not to do
Knowing how to succeed matters less than knowing how people fail. These four patterns are the most common in our data, with symptom → consequence → fix:
| Pattern | Symptom | Consequence | Fix |
|---|---|---|---|
| The collector | Two hundred connections, not one real conversation | Contacts become a list that earns nothing; nobody remembers you either | Pick three people a month for a real conversation and keep the rest as weak ties. Quality beats quantity here more than anywhere |
| The broadcaster | Only advertising, only reposting your own product, never replying to anyone | Zero interaction, high risk of being reported, demand posts often rejected | The three-to-one rule: reply to three people's posts before you publish one of your own |
| The diver | Logs in every day, never posts a demand, never speaks | Activity score yes, referrals zero; nobody knows what you can do | Post one demand first — the cheapest form of exposure — and talk about the rest afterwards |
| Waiting for the doorbell | Fills in the profile and waits, assuming "if someone needs it they will find me" | Three months later concludes the platform is useless, when in fact nothing was done | Three fixed actions a week: message three people, reply to three posts, update one demand |
6What works today, and what comes next
This chapter is for people who intend to use the platform seriously: we separate "already usable", "partly usable" and "scheduled". A manual should promise only what can be delivered — that is the first lesson in credibility, and it is also the basis on which you plan your own workflow.
These three states are used consistently throughout the book:
The behaviour described matches what is online; you can rely on it.
The main route works but one link in it is limited. The table names the type: display-limited (visible but incomplete data) / channel-limited (only one way in) / data pending (waiting on a backend service).
Not live yet. No date is promised, only a priority order (see 6.3).
6.1 Status of every feature, with "what you can do today"
The last column is the most important addition in this edition: for every "partly usable" or "scheduled" item we tell you the workaround for now. Saying only "not yet" is a way of turning you away, and we will not write that.
| Feature | Status | Notes (including the type of limit) | What you can do today |
|---|---|---|---|
| Five main entries and the overall structure | Live | Home, Network, Events, Supply & Demand, Me — plus the floating shortcuts and the tool box | Use normally |
| Member directory and search | Live | Search, nearby, native place, level, industry; unit / enterprise / group views | Use normally; narrow by industry → region → level |
| Contact detail (profile / demand / activity) | Live | Basic profile, can offer / looking for, market, activity feed | Use normally |
| Posting and reviewing a demand | Live | Four states, tags, views, shares, review queue | Use normally; review takes time, so post a day early |
| Mall and orders | Live | Products, basket, order, payment, orders, refunds, addresses | Check who receives the money before paying (see 3.5) |
| Pulse Chain Index / Pulse Chain Map | Live | Seven-dimension score, referral tree, network structure, adviser assignment | The index is not calculated in real time; no point refreshing repeatedly |
| Whole event flow | Live | Publish, review, sign-up, payment, check-in, materials, attendee list | Screenshot the check-in code before the event, in case the signal is poor |
| Communities (institutions) | Live | List, detail, application, shared pulse chain, group chat | Use normally |
| Task centre and Pulse Credits | Live | Daily / weekly / achievement tasks, streak check-in, redemption | Task items are configured by the operator; members cannot define their own |
| Trade reviews (submit / reply) | Live | Score, tags, text, reply, update within the window | Same-day is most effective; who sees the full text depends on the page setting |
| Data dashboard (events and member structure) | Partly usable | Data pending: events and gender / age / industry / region already shown; content, demand and trust data not yet opened | Decide with "events plus member structure" for now; if you need content or demand data, count it yourself from the view counts in the demand list, or ask the operator for help |
| Direct messages | Partly usable | Channel-limited: text works; images, voice and business cards not yet open; unread badge missing | Send important material as "one sentence plus a link" (put the file in a demand post or on a cloud link) rather than waiting for images; judge unread by the last timestamp in the conversation list |
| Reviews shown on the detail page | Partly usable | Display-limited: the panel is ready; it will fill in the moment the review data service is connected | Read itemised reviews on the trade review page, or ask the person for a screenshot of their Trust Wall |
| AI match cards and the AI assistant | Partly usable | Data pending: the entry point and the conversation interface exist; the match data source and the reasons behind recommendations are being built | Find people with the multi-dimension filters by hand (3.2); treat the AI assistant as an adviser to ask "how", not a search engine to look up names |
| Follow / add friend | Scheduled | The underlying relationship data comes first; the feature follows | Use "shared community plus met at an event" instead; record the person in a Trust Wall collaboration |
| Business trips | Scheduled | The trips tab is expected to arrive with the service | Ask in a message "will you be in Xiamen next month"; once live, trips will be filled in automatically |
| Content feed / event interaction | Scheduled | Likes, comments, reposts, saves, and what is kept after an event | Browse the activity feed and give feedback by message; after an event use the photo album and reviews |
| Language switch (Traditional / Simplified / English) | Built awaiting release |
Code delivered, ships with v1.0.13: three language packs (89 keys each), the language page and the settings entry are all done; users on v1.0.12 cannot see them yet | Use Traditional Chinese until you update; when English is needed, prepare your own bilingual version of anything important (see 10.1) |
| Platform switch (mini program ↔ H5) | Built awaiting release |
Code delivered, ships with v1.0.13: the dual-platform page is done; but H5 is still a local prototype with no public address, so after release it will only copy an address that does not open (see 10.8) | To give material to a client who does not use WeChat: screenshot it or make a PDF; use the link once H5 has a real domain (see 10.2) |
6.2 By role: are the features you need in place?
The same table, read by different people. This small one helps you locate "is there a gap in my own area":
| Role | Core features | Readiness | The one gap |
|---|---|---|---|
| Ordinary member | Members, contact detail, demand, Me, reviews | Sufficient | Messages cannot carry images (use a link) |
| Chamber officer | Member management, events, communities, dashboard | Broadly sufficient | The dashboard lacks content and demand data; bulk member import depends on the back office |
| Event organiser | Whole event flow, tool box | Sufficient | Post-event interaction (likes / comments) not live yet |
| Heavy user | Index, AI matching, following | Partial | AI recommendation reasons and following are being built; you have to fill the gap by hand |
6.3 Known issues
We already know about the following. Listing them is not a disclaimer; it is so you take fewer detours:
| Issue | Impact | Workaround |
|---|---|---|
| No unread badge on messages | Easy to miss a message | Check the conversation list once a day; for important contacts use the demand thread |
| Visibility of full review text is inconsistent | Sometimes you cannot see what the other side wrote | Go by what the review page shows; ask for a screenshot if you need the full text |
| The index updates with a delay | Something you just did is not reflected yet | No need to refresh; go by the update time shown on the page |
| The dashboard excludes content and demand data | You cannot judge content performance from it | Count demand views and feed interaction by hand |
| Images load slowly on some older phones | Home and lists take a long time | Load once on Wi-Fi beforehand; avoid opening it for the first time at the venue |
6.4 How we decide what to build (and why we give no dates)
Many users ask "when will this feature arrive". Our answer is: an order, not a date.The reason is practical — a date that slips damages trust more than no date at all. Rather than promise, let us show you our ordering logic:
| # | What | Why this position | What you will notice when it ships |
|---|---|---|---|
| 1 | Connect the review service | Lights up three places at once — mutual reviews, commercial reputation, the trust dashboard — so the return is highest | You see on the detail page what others say about them |
| 2 | Following and adding friends | The relationship graph already exists, and the discover feed needs a basis for its ordering | People you follow stop disappearing from the list |
| 3 | Upgrade messages (images / voice / cards) | Keeps the information complete before the conversation leaves the platform | You no longer have to jump back to WeChat to send a file |
| 4 | AI matching and the reasons behind it | Moves from "same institution / same city / same industry" to "shared chain and mutual reviews / shared events" | The three people recommended are actually worth looking at |
| 5 | Content and trust data dashboards | Lets operators answer "did the content work, did trust grow" | The monthly report is no longer only event numbers |
The four criteria we order by (you can hold us to them): ① how many people it affects (reach); ② how many critical routes it unblocks (blocking); ③ whether it depends on something outside our control (controllability); ④ whether anyone will notice once it ships (perceptibility).
6.5 What this manual promises, and how to check it
To avoid "the manual reads well and the product is not like that", here are the main promises with a way for you to verify each one. If a check fails, tell us through Feedback — that is how we revise the manual.
| The promise | Where | How you verify it |
|---|---|---|
| Five dimensions are enough to find a specific person | 3.2 | Pick any "industry plus city" combination and see whether you get under twenty results within thirty seconds |
| Demand posts are public to all members | 3.4 | Post one, then ask a friend outside your community to search a keyword from the title |
| A collaboration can leave a traceable record | 3.13 / 5.3 | Complete one mutual review and see whether a case fingerprint appears on the Trust Wall |
| Events run end to end from sign-up to check-in | 3.10 | Sign up for an event and see whether a check-in code appears in My Events |
| Every "partly usable" feature has a workaround | 6.1 | Follow the last column once and see whether the job gets done |
| Credits cannot be cashed out or transferred | 5.2 | Check the redemption and statement pages: there is no "withdraw" or "transfer" entry |
6.6 Quotas and limits
To prevent flooding and abuse, some actions have caps. Below are the principles; the exact numbers are whatever the page tells you (we deliberately do not hard-code figures here, so that a rule change cannot make this manual lie):
- Demand posts: there is a daily / weekly cap and every post is reviewed. When you hit the cap the page says so; post again the next day.
- Direct messages: the first message to someone outside your first chain is rate-limited (against harassment). If you are limited, publish a demand instead or ask a mutual contact to introduce you.
- Reviews: one per collaboration, updatable within the window; you cannot pile reviews onto the same person.
- Tasks: each task type has a cap (for example "publish a valid demand" counts a limited number of times a week); beyond that no reward is given.
- Invitations: a burst of invitations is treated as abnormal and the feature may be suspended; invite people you actually know.
6.7 What happens after you report something
Everything submitted through Me → Feedback enters the operations queue. The flow is: received → categorised (missing feature / how-to problem / content report / dispute) → answered or passed on → scheduled into a release where needed. Content reports and disputes are handled first. If you want an answer, leave a way to reach you; you may also leave none, but then we cannot reply.
7Frequently asked questions, by situation
This chapter is not organised by feature. It is organised by the moment you hit a problem. Find where you are stuck, then read down.
Start with these three (nine out of ten questions)
② "How much time does it take?" Fifteen minutes to get started, then two to five minutes a day (check in, look at three contacts, answer one message), and twenty minutes once a week (post a demand, update your profile).
③ "Can I use it without paying?" Yes. Finding people, posting demands, attending free events and leaving reviews are all free. Some services and event seats are charged, and the page says so.
Situation 1: I have just registered and do not know where to start
Q: Is real-name verification compulsory?
Yes. Trust is the core of the platform, and without real-name verification there is no Radar Score to calculate. Verification data is used only for identity checking and compliance; it is not shown publicly and is not given to your chamber either (see Chapter 9).
Q: Can I have two identities (personal and company)?
Yes. The personal identity is for social and collaboration; the enterprise / unit identity presents your company and products. Both sit under one account.
Q: What if I filled something in wrongly?
Me → Edit profile changes it at any time. Work history, education, skills and products are maintained separately, so changing one does not affect the others. Changing your name or phone number requires re-verification.
Q: Do I have to complete all fourteen fields?
No. Four key ones (profile, products, certificates, articles and video) are enough to be useful; the rest are a bonus. See Table 3-9.
Q: I do not know which level I belong to.
Open Me → Membership to see the level field. To upgrade, go to Members → Apply / Fees. Your chamber decides your level under its own rules; the platform only displays it faithfully (see 1.6).
Situation 2: I cannot find the person I need
Q: Why can't I find someone?
Possible reasons: they have not completed real-name verification, their profile has not passed review, or their privacy setting limits visibility.
Q: How do I make myself easier to find?
Three actions: make "can offer / looking for" specific, attach industry tags, and stay active (at least one interaction or post a week).
Q: Does a low Radar Score mean I have no chance?
No. The score measures the thickness of your record; a newcomer starts behind, but one collaboration plus one review closes most of the gap fast. A high score with no concrete cases is in fact more suspicious.
Q: The search returns a crowd — how do I narrow it?
Industry → region → level, in that order. If you still have more than twenty after all three, your criteria are too broad: go back and pick a finer industry category.
Situation 3: I posted something and nobody responded
Q: Does posting a demand cost money?
Posting is free. Some promoted placements may be charged; the order page shows what applies.
Q: Why is my demand not showing yet?
New posts are reviewed (against advertising and fraud). This is normally done within a working day; a rejection comes with the reason.
Q: Three days and no reply — is the platform useless?
Check three things first: does the title state result, scale and timing; does the description state the boundaries; are there two or three tags. If all three are right and still nobody replies, repost from a different angle (different audience, different scale) and message three people who fit the criteria.
Q: Can I just repost the same thing repeatedly?
Not advisable. Duplicate content is rejected at review, and people who saw it will read it as flooding. Repost an updated version instead, and leave the old one up until the matter is closed.
Situation 4: Events and communities
Q: Can I cancel after signing up?
Depends on the organiser's setting (chosen when publishing). Cancel before the event starts so the seat is not wasted.
Q: How do I check in on site?
Show the check-in code in My Events; the organiser scans it. One code, one entry, no repeats. If the signal is poor, show a screenshot taken in advance.
Q: What obligations come with joining a community?
Follow the community rules, do not flood it with advertising, and get both sides' consent before introducing them. Breaches may lead to removal.
Q: Who sets a community's rules?
The institution that owns it. Read the community introduction before joining; different rules are normal.
Situation 5: Money and credits
Q: Can I return something bought in the Mall?
Depends on the product. If marked refundable, go to My Orders → Order detail → Request refund and supply whatever that type requires.
Q: Can I get an invoice, and who issues it?
Yes, and whoever actually sells issues it (platform products by the platform, merchant products by the merchant). Request it in the order detail; the process and timing are shown on the page.
Q: Can credits be converted to money?
No. Credits are contribution points: not cashable, not transferable, not convertible into cash, usable only for benefits inside the platform. Do not trade them by any means.
Q: Who receives the event fee?
The payment page shows the payee: if the platform collects on behalf, it is the operating entity; if the merchant collects directly, it is that merchant. Read that line before paying — it is also the basis for any later refund.
Situation 6: Privacy and safety
Q: Will my contact details be visible?
Not published directly. Others have to reach you through platform messages; your details appear only if you give them out.
Q: What do I do about harassment or fraud?
Report it on the conversation or content page and also through Feedback. The platform acts on the record and may suspend serious cases.
Q: Can my "nearby" location be tracked?
Nearby Members only works if you grant location permission; without it we do not obtain your location. The scope and how to switch it off are in Chapter 9, 9.1.
Q: How do I delete my account?
Apply through Feedback, or contact your chamber officer. What happens to your data afterwards is in Chapter 9, 9.6.
Situation 7: A collaboration went wrong
Q: Will the platform step in if a deal goes wrong?
The platform provides three things: records (the demand post, reviews and case fingerprint serve as evidence), a channel (helping the two sides talk), and rule enforcement (if platform rules were broken). The platform does not decide who is right and does not replace legal process; for disputes over money or contracts, use the formal legal route. What the platform can guarantee is that the record you left is real and can be produced.
Q: I believe a review is untrue — can it be changed?
You may object. The process and time limit are in Chapter 9, 9.2.
Q: If I am removed from a community, do I lose my data?
No. Your account, Trust Wall and reviews stay; what you lose is membership of that community and its exclusive benefits.
8Glossary
The platform has its own language. The purpose of this page is not definition for its own sake, but so that when you meet a word you can jump straight back to where it is explained.
Member (會員) — a status. Your relationship with the chamber (level, fees, benefits), decided by that chamber. It appears in contexts such as "membership level", "apply to join", "member benefits".
Chain contact (鏈友) — a form of address. What platform users call each other, meaning "people on the same chain", regardless of level. It appears in "chain contact showcase", "chain contact activity", "dear chain contacts".
One line to remember it by: a member is "whose member you are"; a chain contact is "what we call each other".
| Term | Meaning | Section |
|---|---|---|
| Member 會員 | Your status level within the chamber (member / adviser / regional congress and so on), decided by your chamber under its own rules. | 1.6 |
| Chain contact 鏈友 | What platform members call one another, regardless of level. From "people on the same chain". | This chapter |
| Pulse chain 脈鏈 | The chain of relationships formed by referrals; its origin can be traced and it cannot be overwritten. | 3.8 |
| Pulse Chain Map 脈鏈圖 | The tree visualisation of referral relationships; zoom, drag and tap to inspect. | 3.8 |
| Pulse Chain Index 脈鏈指數 | A multi-dimension score (trust / reliability / activity / referrals / recommendations / shares), out of 100, showing your relative position on the chain. | 3.8 / 5.1 |
| Radar Score 雷達分 | The combined score of the seven-axis people radar (0–5), the single number on the directory and detail pages (e.g. 4.6). The seven axes: trade reviews / profile completeness / active online / content creation / hosting events / attending events / referral contribution. Trade reviews (F1) are left out of the average until that feature ships. | 3.2 |
| Trust Score 信任分 | A separate indicator, not the same thing as the Radar Score. It measures accumulated trust behaviour (for example trust likes from chain contacts). Calculated differently from the Radar Score, and the two cannot be converted into each other. | 3.2 / 5.3 |
| Relationship level 關係層級 | L1 (directly referred), L2 (one step away), L3 (two steps away). On screen these read "chain 1 / chain 2 / chain 3". | 3.8 |
| Referral 引薦 | The act of introducing A to B, recorded on the chain by the system. | 5.1 |
| Pulse Credits 脈鏈積分 | Behaviour points inside the platform (the number in the credits tile of "Me"), earned through tasks and contribution, redeemable for benefits; not cashable, not transferable. Distinct from Pulse Ore, a different asset — the two cannot be exchanged. | 3.12 / 5.2 |
| Pulse Ore 脈礦石 | A different asset, used only in mall / mining-related contexts; held in a separate ledger from Pulse Credits, not exchangeable and not additive; likewise not cashable or transferable. | 3.12 |
| Trust Wall 信任牆 | The wall of collaboration cases on a personal page, each with a case fingerprint. | 5.3 |
| Case fingerprint 案例指紋 | The unique reference for each collaboration (for example CASE-2026-0918-77A3), used for citation and tracing. | 5.3 |
| Supply & Demand 供需 | Your post of what you "can offer" and what you are "looking for" — the core unit of matching on the platform. | 3.4 |
| Opportunity Plaza 機會廣場 | The discovery page with random contacts and a feed of collaboration opportunities. | 3.7 |
| Community 社區 | A group of members gathered by industry, region or theme (also called an "institution" in the system). | 3.11 |
| Adviser assignment 顧問指派 | The platform assigning an adviser to a member to help sort out their network and make introductions. | 3.8 |
| Check-in 核銷 | Confirming at the venue, by scanning, that a registered person attended. One code, one entry. | 3.10 |
| Review tags 評價標籤 | The three tags you can choose when reviewing: honest and reliable, well resourced, professionally reliable. | 3.13 |
Five questions to test yourself (trainers may use these as pre-reading)
- What is the difference between a "member" and a "chain contact"?
- How many steps do L1, L2 and L3 each represent, and which one should you ask for an introduction?
- Can Pulse Credits be converted to cash? Why?
- Are the "Radar Score" and the "Pulse Chain Index" the same thing?
- Can an event check-in code be reused?
9Compliance and the limits of responsibility
This chapter exists for a simple reason: a platform that sells trust, and cannot say clearly how it handles your data, how it scores you, and who answers when something goes wrong, is selling an empty word.
9.1 Your personal data: what we collect, why, and who sees it
| Type of data | What it is for | Who sees it | Retention and deletion |
|---|---|---|---|
| Mobile number | Registration, sign-in, identity verification, important notices | Platform systems only; other members cannot see it | While the account exists; after deletion, per 9.6 |
| Real name and identity documents (verification) | Identity checking, legal compliance, preventing impersonation | Verification only; not displayed, not given to the chamber | Retained as required after verification; never used for marketing |
| Professional data (company, title, city, history, products) | Building a searchable directory, matching and referrals | Signed-in members (according to your visibility settings) | You may edit or hide it at any time; once deleted it is not shown |
| Location ("nearby members") | Finding people in the same city | Your precise position is not shown, only "same city / nearby" | Requires your permission; can be switched off in system settings |
| Behaviour data (views, interaction, reviews, fulfilment) | Calculating the index, ordering, fraud prevention | Shown in aggregate; individual actions are not published | Handled per the scoring explanation in 9.2 |
| Message content | Providing messaging, handling reports and disputes | The two parties only; the platform does not read messages on its own, only when a report is filed or as required by law | Retention per the Privacy Policy; you may delete a conversation yourself |
Your four rights (available at any time)
- Access and correction: view and edit in Me → Edit profile. For things you cannot change yourself (such as verified identity), apply to us.
- Withdraw consent: location and notification permissions can be switched off in system settings; once off, related features (such as nearby members) will not work.
- Deletion: you can delete individual items (posts, demands, images). Account-level deletion is in 9.6.
- Refuse marketing: switch it off in Settings → Notifications. You will still receive notices necessary for your account and transactions.
9.2 Automated scoring and reviews: where they come from, how to object
The Pulse Chain Index and the Radar Score are calculated automatically by the system, not judged by a person. Here are the principles:
- Platform data only: reviews, fulfilment, interaction, referral records. We do not use your behaviour outside the platform and we do not buy third-party data.
- No judgement of the person: the score reflects only "behaviour record on the platform". It does not represent your character, ability or credit rating, and is not used for lending decisions.
- It can fall as well as rise: long inactivity, a upheld report, an unresolved dispute — all lower it. That is by design, not a punishment.
- Weights are not published: the reason is in 3.8 (to prevent score-gaming and to avoid mechanising human behaviour).
If you believe a score or review is wrong
9.3 Transactions and money: who is paid, how refunds work, invoices
| Setting | Payee | Paperwork | Refunds |
|---|---|---|---|
| Mall purchase | Whoever the payment page names (platform's own products: the operating entity; merchant products: that merchant) | Issued by whoever invoices; request it in the order detail | Per the refund rule shown on the product page; apply in the order detail |
| Event registration | Whoever the event or payment page names (the organiser, or the platform collecting on their behalf) | Per the organiser's arrangement; ask them if you need one | Per the "refundable" box the organiser ticked when publishing |
| Chamber fees | Your chamber, by the method it specifies | Issued by the chamber | Per the chamber's rules; the platform does not decide this |
9.4 Content and conduct rules: what we review and how we act
The purpose of review is to block advertising and fraud, not to restrict expression. These are the criteria — use them to check your own post:
| Content | Passes | Sent back |
|---|---|---|
| Supply & Demand | A specific need or offer, a way to make contact, information that can be verified | Pure advertising, no specifics, exaggerated claims ("guaranteed profit"), unrelated to business |
| Events | Clear time and place, clear fee and refund rule, an identifiable organiser | Incomplete information, unclear charging, suspected fundraising, content that differs from what was registered |
| Posts and reviews | Based on real experience, about the matter rather than the person | Personal attacks, disclosure of private information, flooding, undisclosed paid promotion |
Prohibited conduct (acted on once established)
- Impersonating someone or registering on their behalf; faking invitations or reviews.
- Collecting fees in the platform's name, soliciting investment, or recruiting downlines.
- Harassment, threats, discriminatory speech, or spreading another person's private information.
- Posting content unrelated to business (political mobilisation, gambling, pornography, exaggerated medical claims).
The ladder of action (by seriousness — it does not always start at step one): content removed or sent back → warning and a requirement to correct → feature restriction (posting or messaging suspended) → account suspension → referral to the authorities. Where fraud or personal safety is involved, suspension is immediate and the matter is handled according to law.
Eligibility: who may use it, and who may not
The platform serves business matching and does not aim at "traffic", so there are basic eligibility requirements. The following four situations cannot register, or will be restricted:
- Anyone below the age of legal majority: requires consent from a legal guardian, and the platform does not actively offer its service to minors.
- Anyone who cannot complete real-name verification: verification is the precondition of the Radar Score; without it, full features cannot be enabled (see 9.1).
- Anyone whose main purpose is promotion, soliciting business or recruiting downlines: such accounts have their demands and posts sent back, and repeat cases are suspended (see prohibited conduct 2 above).
- Anyone previously suspended and not restored: re-registration with the same verified identity is detected and refused.
One more caution: the platform is not a recruitment agency, an investment adviser, or a legal or tax service. What you obtain here is people and records; professional judgement remains yours to make, or to buy elsewhere.
9.5 The limits of responsibility: what the platform does and does not do
Setting out the boundary is not about shifting blame; it is so that you expect the right things from us:
| The platform does | The platform does not |
|---|---|
| Provide a searchable, verifiable directory and record-keeping tools | Decide who is right or arbitrate commercial disputes |
| Review content, handle reports, keep traceable records | Endorse or guarantee the performance, quality or payment of any individual deal |
| Maintain system security and protect your data under the rules | Do your due diligence for you; what should be checked before signing is still yours to check |
| Announce rule changes in advance | Promise launch dates for specific features; take responsibility for the content of third-party links |
9.6 Closing an account and what happens to your data
What happens to referral relationships after you leave
"A referral relationship cannot be overwritten" raises a common question: "if I leave the chamber, or close my account, is that line still there?" Three cases — find yours:
| Your situation | Referral record | What you can and cannot do |
|---|---|---|
| Left the chamber or community, account still open | The record is kept; it is not deleted or reassigned to someone else | You can still sign in and see your own pulse chain map; what you lose is that chamber's membership and its exclusive benefits (event tiers, community rights, member pricing) |
| Suspended | The record is kept but frozen: not counted in the index, and no new referrals are added | You cannot sign in or interact; once the dispute is resolved and access restored, records count again |
| Account closed voluntarily | Handled per 9.6: collaborations involving others are kept in de-identified form (because they are also the other party's credit record) | Cannot be transferred to a new account or assigned to anyone; re-registering creates a brand-new account and the chain starts from zero |
9.7 Compliance information and contacts
10Two switches: language and platform
This chapter is about no business module at all. It is about two switches that belong to nothing and affect every single session: which language you read, and which container you come in through. The first decides whether you understand what you are looking at; the second decides what the product can do for you. Both live in the same place: Me → System settings.
Mind the gap in time: the v1.0.12 on your phone still has only four settings items (see 6.1). We do not write "the code is written" as "it already works".
If you are reading the HTML edition, that control bar is at the very top of this page and works right now: press 简体 and the whole manual switches to Simplified Chinese; press English and you come back here; press H5 and the preview above turns into a browser frame listing the differences between the two platforms. Remember one thing — what is clickable is this manual; the same set of buttons inside the app on your phone appears only after the v1.0.13 update (see 10.8).
10.1 Language switch: one button, three languages Traditional / Simplified / English
Purpose:so that a first-time reader does not have to learn this vocabulary before they can understand what the screen says. Users span Taiwan, the mainland and overseas Chinese communities, plus partners who read only English; the same features present three quite different levels of difficulty to those three groups.
Meaning:language is not merely a translation problem; it is a precondition of trust. A Taiwanese business owner in Southeast Asia opens the interface and finds a screen full of simplified-character terminology he is not sure about. He does not dare press "publish demand", because he might fill it in wrongly, be misunderstood, or say the wrong thing. What the language button really solves is not daring to start — not "not understanding".
What it does:a three-way button switching between Traditional Chinese, Simplified Chinese and English. Three behaviours need stating plainly:
- On first entry it follows the phone's system language.A Traditional Chinese phone gets Traditional, a Simplified phone gets Simplified, an English phone gets English. Most people never need to set it — the button is for those whose system language is not the language they want to do business in (a Taiwanese user whose phone is set to English, for example).
- It takes effect immediately, with no re-login.Language is a display preference: it does not touch your account, your data or your referral relationships. Choose wrongly, choose again; there are no side effects.
- The preference is remembered.Next time you come in on the same phone, it stays as you left it and is not reset each time.
After switching: what changes and what does not
This is the most important passage in the section. Most misunderstanding about "switching language" lives here — people assume the whole world turns English. In fact:
| Item | Changes? | Note |
|---|---|---|
| Interface copy, buttons, menus, prompts | Yes | Text the system owns: bottom navigation, form field names, error messages, FAQ headings |
| Content members wrote themselves | No | Names, companies, self-introductions, demand descriptions, event titles, review text — that is someone else's writing and the system does not translate it. A reader in English still sees Chinese member profiles |
| Proper nouns (referral chain, Pulse Credits, Radar Score) | Partly | The English edition keeps the brand name WeaveInX and glosses the core nouns; undecided terms stay in Chinese rather than acquiring a fourth name |
| Content you have already published | No | It is not rewritten or retranslated; to say the same thing in another language, post it again |
| Account, data, referral relationships, Radar Score | No | Language is purely the display layer; switching does not change identity and does not affect the index |
$t() wired in page by page — the next stage. So at present English means "the entry points are readable, member content is still Chinese". We mark the coverage honestly in Table 6-1 and 10.8, and do not write "the whole interface has been Englished".
Traditional to Simplified is not character substitution: six pairs people genuinely misread
Converting Traditional straight to Simplified goes wrong in business settings. Below are the pairs most likely to mislead; the book uses them consistently, and so does the interface:
| Traditional (Taiwan) | Simplified (mainland) | Why you cannot just swap characters |
|---|---|---|
| 資訊 | 信息 | It is not "資 → 资"; the whole word differs |
| 資料 | 数据／资料 | In the mainland 数据 leans towards numerical statistics and 资料 towards documents; which one applies depends on context |
| 網路 | 网络 | 網 against 网 — the shapes are far apart and conversion tools miss it |
| 品質 | 质量 | A literal conversion produces 质量, which reads as "weight" |
| 預設 | 默认 | An entirely different word; character-by-character conversion fails |
| 專案 | 项目 | Taiwan's 專案 is the mainland's 项目, not 专案 |
Three limits of the English version (stated now, to avoid disappointment)
- It is not a complete translation.The core flows come first (registration, finding people, demands, events, reviews); long legal documents and detailed FAQ entries may still be in Chinese and marked "English version coming".
- It is not native-speaker standard.The English serves "understandable and safe to operate", not external marketing. For signing contracts or filing with a government, use the Chinese edition or a formal English contract.
- Support is still mainly in Chinese.An English interface does not mean twenty-four-hour English support; if you need help in English, say so in a message first, or book through the contacts in 9.7.
10.2 Platform switch: mini program ↔ H5 Two containers
Purpose:so that you can pick, for the occasion in front of you, the container with the right capabilities — the native mini program inside WeChat when you are doing business there, and a single web address when you need to send material to an overseas client who does not use WeChat. Same platform, same account, two entrances.
Meaning:this is often mistaken for "they built two things". They did not. It is one backend and two front-end containers. The real point is this: relationships formed in a WeChat group cannot leave WeChat, and business often happens outside it — Line, WhatsApp, email, the follow-up after a real visit. H5 is the road out. Without it, everything you accumulate here can only be shown to WeChat friends.
What it does:Me → System settings → Platform offers the switch, shows which container you are in, and explains what will happen. The two directions behave differently and need separate explanation:
| Direction | What happens when you press it | What you need to know |
|---|---|---|
| Mini program → H5 | Opens H5 in an embedded web view inside the mini program, or (where embedding is restricted) shows the address with a "copy link" button for you to paste into a browser | Embedded, you are still inside WeChat, just in a different container; to send the link to someone outside WeChat you must copy it into Line, WhatsApp or email |
| H5 → mini program | Shows the mini program code and a "open in WeChat" prompt; anyone already inside WeChat can jump with one tap | A browser outside WeChat (Safari, Chrome) cannot jump into the mini program directly; you must open WeChat and scan |
10.3 What a mini program is: a "near-native app" inside WeChat Must read
Purpose:to state clearly what the entrance you use every day actually is, what it gives you, and what it can never do.
A mini program is an application that runs inside WeChat. Nothing to download or install, but with app-like capabilities: camera, location, payment, message notifications. For a business community the implication is direct — the cost of inviting someone drops to almost zero. You do not ask them to "download an app"; you send a code, or forward a card.
Four ways in
- Scanning a code:on site at an event, on a business card, on printed material. This is the most valuable route, because it also puts you on a referral chain — whoever's code it is, that is whose line records you (see 5.1, the trust flywheel).
- WeChat search:search "WX脈鏈鏈" or WeaveInX. For people who already know the name.
- Share cards:a member forwards a card or a piece of content into a group or conversation, and tapping it opens the detail. This is the main engine of internal growth.
- Official account menu or association:set up by the operator, entering from the official account in one tap (where enabled).
What the mini program gives you
| Capability | What it is actually for |
|---|---|
| WeChat Pay | Mall orders and event fees, completed on the spot without leaving |
| Subscription messages | Review outcomes, order status, event reminders — sent only if you pressed "allow" |
| Share cards into groups and chats | Business cards, demands, events: one tap into a group, and the other side lands on the detail page |
| Scan | Check-in on site, redemption, adding contacts |
| Identity and verification | Bound to your WeChat account, so signing in is almost invisible |
Three things the mini program cannot do
- It cannot leave WeChat.You cannot paste a mini program card into Line or WhatsApp, and the other side could not open it. Cross-platform sharing means an H5 link or an image.
- Every release needs review.Fixing a single character goes through the process, which can take a day or two. So the mini program is always one step behind H5.
- The other person needs WeChat.Anyone without a WeChat account simply cannot get in — which is precisely why H5 exists.
10.4 What H5 is: one address is one entrance Must read
Purpose:to let in the people who have no WeChat, do not want to install anything, or are sitting at a computer — and to let what members accumulate be forwarded outside WeChat.
H5 is the web version. It runs in a browser: the one inside WeChat, Safari, Chrome, Edge, any of them. You give someone an address and they open the same platform and the same interface. For cross-border work this matters enormously — a client in Southeast Asia, an older relative in Taiwan who does not use WeChat, a partner abroad: all of them can open it.
Three ways in
- Tap a link:in a Line group, on WhatsApp, in an email signature, on the last slide of a deck, inside a QR code on a business card.
- Scan an ordinary QR code:with the phone camera, which opens the browser directly, no WeChat needed.
- Type the address into a desktop browser:this is where H5 beats the mini program in practice — you can project it during a presentation and compare windows side by side.
What H5 gives you
| Capability | What it is actually for |
|---|---|
| A link that goes anywhere | Send it to any messenger, any device, any country, and the other side installs nothing |
| No install, no account wall | See the content first, sign in only to interact — which lowers the cost of taking a look |
| Instant updates | The day of a release is the newest build; no review queue |
| Works on a computer | Read the directory on a big screen, organise data, present |
| Can be indexed by search engines | Public pages can be found by Google, bringing traffic from outside WeChat (depending on settings) |
Three limits of H5
- WeChat sign-in and WeChat Pay depend on the environment.Opened inside WeChat with the right configuration, H5 can use WeChat Pay; opened in Safari or Chrome it must use another payment route or send you back to the mini program.
- No subscription messages.It will not proactively tell you a review outcome or an event reminder; you rely on SMS, email, or coming back to look.
- Location and camera are less precise."Nearby members" needs location permission, and a browser's accuracy is worse than the mini program's; photo upload is also constrained by the browser.
10.5 The two platforms side by side: sixteen dimensions Core table
This is the page of the chapter most worth printing. Pick your situation on the left, read the capability on the right, and stop guessing in between.
| Dimension | WeChat mini program | H5 web version |
|---|---|---|
| How you get in | Scan, WeChat search, share card | Any link, camera scan, typing the address |
| Installation | △ needs WeChat (but no separate app) | ✓ nothing at all |
| Sign-in | ✓ WeChat authorisation, almost invisible | △ mobile code or password; WeChat authorisation inside WeChat |
| Account and data | The two share one account, one set of data, one referral chain | |
| WeChat Pay | ✓ complete | △ inside WeChat with configuration; not in an external browser |
| Notifications | ✓ subscription messages | ✕ none (SMS or email only, or look yourself) |
| Sharing into a WeChat group | ✓ a card that opens the detail page | △ paste the link only |
| Sharing to Line / WhatsApp | ✕ the card cannot leave | ✓ one link, pasted anywhere |
| Scan and check-in | ✓ native | △ needs camera permission, poorer experience |
| Location for nearby members | ✓ more precise | △ needs permission, less precise |
| Camera and upload | ✓ native | △ constrained by the browser |
| Desktop use | △ needs WeChat for desktop | ✓ open it in a browser |
| Update speed | △ review required, slower | ✓ instant |
| Findable by search engines | ✕ | ✓ (public pages, depending on settings) |
| Offline use | ✕ cache only | ✕ cache only |
| Current status | Live (v1.0.12) | Prototype v0.5, not open |
10.6 Which one, when: four situations
No need to memorise sixteen dimensions. Memorise four situations.
| Your situation | Use | Why |
|---|---|---|
| Meeting people at an event, adding contacts, paying | Mini program | Scan straight in, pay on the spot, cards drop into a group |
| Sending platform material to a client who does not use WeChat (Southeast Asia, Europe, America, an older relative in Taiwan) | H5 | One link solves it and they need no WeChat account; a mini program card will not open for them |
| Working at a computer: sorting the directory, preparing a deck, comparing data | H5 | Big screen, multiple windows, no WeChat desktop client |
| Needing to be notified (did the review pass, where is the order, event reminder) | Mini program | Only the mini program has subscription messages; H5 will not call you |
10.7 Where the data divides: what syncs and what does not
"Will I lose my data if I switch" is the question asked most. The answer has three layers, and the third is where people trip.
- Syncs:account data, demands, orders, event registrations, reviews, referral relationships, Pulse Credits. These live on the server; changing container is changing the skin.
- Does not sync: form drafts.A demand you half-filled, a message you did not send — none of it is visible on the other platform. To continue across platforms, submit or copy the text first.
- May not sync: sign-in state and permissions.H5 needs one fresh sign-in, and location and notification permissions must be granted again separately. That is not a bug; the two containers hold permissions independently.
10.8 What has been implemented, and how to accept it delivered
This section is for operators and developers; ordinary members can skip it. It lists the files, routes and acceptance steps actually delivered — not "we plan to", but already committed to the repository.
The nine delivered files
| File | Type | Purpose |
|---|---|---|
common/i18n/index.js | New | A lightweight i18n core: language state, switching, key lookup, and fallback for missing keys (current language → Traditional → the key name, so undefined never appears). No third-party package, to stay under the 2 MB main-package limit |
common/i18n/zh-TW.js | New | Traditional Chinese dictionary, 89 keys |
common/i18n/zh-CN.js | New | Simplified Chinese dictionary, 89 keys (aligned key by key with the Traditional one) |
common/i18n/en.js | New | English dictionary, 89 keys, covering settings / language / dual platform / bottom navigation (business pages are not yet wired to $t()); the terms are in Table 10-9 below |
pages/mine/settings/language.vue | New | The language page: three cards (Traditional / Simplified / English), each with a sample line in that language; choosing applies at once and writes to local storage |
pages/mine/settings/platform.vue | New | The dual-platform page: explains the difference, and offers two routes — copy the H5 link, or scan back into the mini program |
pages/mine/settings/system.vue | Rewritten | System settings now has three groups (interface and display / account / about), with new entries for Language and Platform and the current value shown on the right of each |
pages/component/tab-bar/tab-bar.vue | Modified | Bottom navigation now uses $t(), so all five tabs change the moment the language changes |
pages/mine/index.vue | Modified | Adds a Settings entry to the Me page (previously you had to take a detour) |
The two new routes
Registered in pages.json as pages/mine/settings/language and pages/mine/settings/platform. Both reuse the existing title-bar component, and the title follows the language.
The English terms (settled)
This is what Appendix F, item 8 had been missing. The decisions below follow the principle "meaning first, not literal", and are used in both the manual and the code:
| Chinese | English | Why |
|---|---|---|
| 引薦鏈 | Referral Chain | "Chain" here means a record of relationships, link by link, not a blockchain; Chain keeps the sense of being strung together and not overwritable, and stresses sequence more than Network would |
| 引薦 (verb) | refer / referral | In business English, to refer is to introduce someone and vouch for them — a layer of responsibility beyond "introduce", which matches the platform's design that a referral carries obligation |
| 脈鏈積分 | Pulse Credits | The points shown on screen as 積分. Pulse comes from the platform's name; Credits rather than Points, because credits cannot be transferred, cashed out or converted — "Points" suggests something redeemable for money |
| 脈礦石 | Pulse Ore | A separate asset held in a different ledger (see 3.12). Ore is the literal reading of 礦; never interchangeable with Pulse Credits |
| 雷達分 | Radar Score | The combined score of the seven-axis radar (0–5), the number shown on the right of a profile. Score is more neutral than Rating: it measures accumulated verifiable behaviour, not a subjective verdict |
| 信任分 | Trust Score | A different indicator, measuring accumulated trust behaviour (for example trust likes); calculated differently from the Radar Score and not convertible into it |
| 供需 | Supply & Demand | Not Post or Listing, because the field carries two directions at once — what I can offer and what I am looking for |
| 機會廣場 | Opportunity Plaza | Plaza keeps the openness of 廣場; not Market, to avoid confusion with the Mall |
| 社區 | Community | The member grouping under a chamber, not a residential estate |
| 案例指紋 | Case Fingerprint | A non-reproducible digest of a collaboration record; fingerprint keeps the three senses of unique, identifiable and unforgeable |
Six acceptance steps before release
Do them in order; if any step fails, go back and fix it rather than skipping ahead:
- ① Build:
npm run build:mp-weixincompletes without errors; confirm the main package grows by less than 30 KB (the three dictionaries total about 13 KB). - ② Three-language walk-through: in the developer tools, cycle Traditional → Simplified → English → Traditional and check that the four pages (Me, System settings, Language, Platform) have no missing strings and no
undefined. - ③ Persistence: after switching to English, close the mini program completely and reopen it; the language should still be English (stored in
wx_lang). Clearing storage should return it to the system language. - ④ Content is not translated: confirm that names, self-introductions and demand descriptions written by members do not change with the language — that is a design principle, not a bug.
- ⑤ Dual-platform page: the H5 link copies; before opening H5 inside WeChat, confirm the business-domain allowlist is in place, or you get a blank screen.
- ⑥ Submission: set the version to v1.0.13 and write "adds language switching (Traditional / Simplified / English) and an H5 entry" in the release notes.
Until all three are done, ship the language switch first and postpone the platform switch — better one working switch than two half-finished ones.
common/i18n/ in the repository and you will find three dictionary files with 89 keys each; open pages/mine/settings/ and you will find the new language.vue and platform.vue. If your copy has none of these five files, you have not pulled this change yet.
11Screen by screen: 25 real-device screenshots
The first ten chapters explain how the platform works. This chapter shows what it actually looks like. All 25 images come from the live mini program (v1.0.125 development channel) — nothing redrawn, nothing simulated, no placeholder mock-ups. Each card is split into five parts: what this page does, what you can see on screen (element by element), how to operate it, why it is designed this way, and what to watch out for.
1. Version: captured from the v1.0.125 development channel (the green bar at the top of the screen shows vdevelop and an internal test URL). The production build will not have that bar; everything else is identical.
2. Data: names, amounts and event counts in the screenshots are real test data, not numbers invented to look good. Some screens (figure 11-5, for example) show zeros or blanks because nobody has filled them in yet, and we show them as they are.
3. Timing: screens change as versions ship. If your phone shows something different from the picture here, your phone is right — report the difference through "Me → Feedback" and we will re-shoot that screen.
11.0 Index: how to find any of the 25 screens
If you are looking for one particular screen, this table is the fastest way in. The left column is the figure number, the middle is the screen, and the right is where you tap to get there — follow the right column and you will see the same page.
| Figure | Screen | Where to tap | What it is for |
|---|---|---|---|
| 11-1 | Home | Tab bar → Home | The first screen you open every day: it packs “what this platform is”, “how to find people” and “what is happening now” onto one page. |
| 11-2 | People Radar (map + list) | Home → People Radar card → Open | Turns “who is nearby” from a feeling into a list you can sort, filter and measure in metres. |
| 11-3 | AI Member Assistant (conversation sheet) | Home → floating button on the left → Assistant | For the moment when you do not know how to start the conversation: it helps you state the question properly first. |
| 11-4 | Opportunity Plaza | Home → floating button → Plaza (also reachable from the eight-tile grid) | Uses randomness against the algorithmic bubble: it brings you the people and opportunities you would never have searched for. |
| 11-5 | AI Matching (Discover) | Home → floating button on the right → AI Matching | Turns “flipping through the directory” into “one card at a time”: eight per day, then you stop, so you cannot scroll forever. |
| 11-6 | Member Showcase (directory) | Tab bar → Members | Three ways of finding people on one page: search if you know the name, filter if you know the criteria, browse by industry if you know neither. |
| 11-7 | Multi-filter (filter panel) | Member Showcase → Multi-filter → Start | Four groups of criteria, set once, and it tells you how many people you will get before you press the button. |
| 11-8 | My Network (network asset sheet) | Members → My network banner, or Me → My network | Turns your network from a feeling into a balance sheet: how many countries, cities, people and companies. |
| 11-9 | Seven-axis Network Radar (choosing people) | Member Showcase → floating button → Seven-axis network radar | This page is not about finding people, it is about choosing them: who is worth the time before you spend it. |
| 11-10 | Seven-axis Radar detail (single person) | Figure 11-9 → any card → “See seven axes” | Breaks “how to become more credible” into seven things you could do this week. |
| 11-11 | Event list | Tab bar → Events | From “add your name in the group chat, sign a paper sheet on the day, lose touch afterwards” to a process with a record. |
| 11-12 | Event map (map view) | Event list → map icon at the upper right | See which city is active: before a trip, check whether the destination has anything on this week. |
| 11-13 | Member map (world) | Home → eight-tile grid → Member map | This is “where in the world my network is”, not “who is near me”. |
| 11-14 | Supply & Demand | Tab bar → Supply & Demand | Turns “I have a need” into a public, searchable request that people can respond to, instead of something buried in chat history. |
| 11-15 | Profile (Me) | Tab bar → Me | Your CV, your report card and the master switch for every setting, all on one page. |
| 11-16 | Data board (personal overview) | Me → Data board | Turns “how am I doing” into six numbers, then gives you a shortcut to fix them. |
| 11-17 | Network asset annual report 2026 | Me → data entries / annual report entry | Settles a year of social labour into an asset statement you can share. |
| 11-18 | My events | Me → Data board → Event data → My events | The thing a host fears most is many registrations, few arrivals. This page opens the funnel so you can see where people drop out. |
| 11-19 | Data dashboard (platform / operator view) | Me → Data board (operator entry) | The page an event organiser reads for decisions: which month dropped, which industry is biggest, what start time works. |
| 11-20 | Targeted invitations (who to invite) | Event entries → Targeted invitations | Turns a list into attendance: works out who to invite and where to go, with a reason attached to every suggestion. |
| 11-21 | Pulse Chain Map (referral circles) | Me → network entries / Pulse Chain Map | How you were brought in, and who you brought in — a chain that cannot be overwritten and can be traced. |
| 11-22 | Member messaging (conversation list) | Members → Messages, or card → Message | The move that turns a public business card into a private relationship, packaged as a manageable list. |
| 11-23 | Member detail (business card page) | Any list, map or card → tap a person | The card page is their shopfront: the footfall at the door, the work on the wall, and the “message me” at the end. |
| 11-24 | Info sheet and “Ask them to talk” | Card page → Info sheet / Invitation | The most honest page in this manual: there is no calendar here, so it hands you a paragraph you can actually send. |
| 11-25 | Communities (the seven and the list) | Home → eight-tile grid → Communities | The platform is a square; a community is a small room. Most real collaboration happens in the small room. |
11.1 Home and global entries11-1 to 11-4
Four screens that make up your first thirty seconds: home gives entries, radar gives distance, the assistant gives clarity, the plaza gives accidents.
Fig. 11-1
Home
The first screen you open every day: it packs “what this platform is”, “how to find people” and “what is happening now” onto one page.
Home is not a feed. It is an entry matrix. People here are not scrolling for content — they are looking for people — so the first screen answers “where do you want to go”, not “what should you read”. Four layers, top to bottom: the claim (carousel banner) → finding people (People Radar card) → tools (eight-tile grid) → activity (brand banner and floating buttons).
| Element | What it shows | How you use it |
|---|---|---|
| Top carousel | “Global Chinese business matching platform” over an animated world map; three small dots at the lower left | Swipe left and right to move through several banners; tapping one opens the matching introduction page |
| People Radar card | Subtitle “see who is nearby, sorted by distance, filter by radius” plus an “Open” button on the right | The highest-traffic entry on the whole platform — one tap to figure 11-2 |
| Eight-tile grid | Pulse Chain intro / Member map / Digital card / Communities / Contacts / Supply & Demand / Events / Event sign-up sheets | Shortcuts that bypass the tab bar; the two dots underneath mean you can swipe to a second page |
| Brand banner | “Welcome to WX WeaveInX / connect with trusted partners, create value together”; a “Chinese” tile at the upper right | Opens the brand page; the “Chinese” tile is one of the language entries (see chapter 10) |
| Floating buttons (left / right) | Left: Tools, Assistant, Plaza. Right: AI Matching, Plaza | Global shortcuts that stay on every page — they do not disappear when you navigate |
| Tab bar, five slots | Home / Members / Events / Supply & Demand / Me | The trunk of the product; everything else is a branch |
- Want to see who is nearby → tap “Open” on the right of the People Radar card.
- Want a particular module → tap the eight-tile grid directly (two pages, swipe across).
- Have a question → tap “Assistant” on the left (AI Member Assistant, figure 11-3). Want to be introduced → tap “AI Matching” on the right (figure 11-5).
Separating “entry” from “content”: home only has to send you to the right place, not keep you here. Every release that adds a feature then just adds one tile instead of disturbing the whole page logic.
The floating buttons cover the lower right corner — watch out when you scroll to the bottom of a list. The green bar at the very top (vdevelop 1.0.125 and a URL) only exists in the internal test / development channel; the production build does not have it.
Fig. 11-2
People Radar (map + list)
Turns “who is nearby” from a feeling into a list you can sort, filter and measure in metres.
This is the most tool-like page on the platform: map on top, list below, the two kept in sync. The map answers “where”, the list answers “who”, and the radius plus sort controls are what connect them.
| Element | What it shows | How you use it |
|---|---|---|
| Location line | “Located: Taipei City (based on the centre of members in the same city) · 24 members nearby” | Check the city first; if it is wrong, tap “Taipei City ▾” at the upper right to change it |
| City switcher | City name plus dropdown at the upper right | Before a business trip, switch to the destination city to see how many members are there |
| Map and radius rings | 1 km / 3 km / 5 km / whole city, four concentric rings with member avatars scattered on them | Tap a radius to zoom instantly; the smaller the ring, the more it becomes “who could I actually meet today” |
| Sort toggle | “Nearest first” / “Smart match” | Use nearest first to arrange a meeting; use smart match to find the right counterpart |
| Level filter chips | All 433 / Chapter president 28 / Advisor member / FP-M 11 / FP-L 49 / Member… | Narrow by level first, then look at people one by one |
| List card | Avatar, name, level badge (Close friend / FP-L / Member), industry · city, distance on the right (496 m) | Tap any card to open the card detail page (figure 11-23) |
- Confirm the city
- tap a radius ring (3 km, for example)
- choose a sort order
- narrow with the level chips
- tap a name to open the card
- message or invite.
“24 nearby” is only worth anything if you are willing to go out. That is why the default sort here is distance, not match score — first make the meeting possible, then make it the right meeting.
“Based on the centre of members in the same city” means this is not precise GPS — it is inferred from the city centre point. Distances are straight-line, not travel distance. Only members who granted location permission and filled in a region appear at all.
Fig. 11-3
AI Member Assistant (conversation sheet)
For the moment when you do not know how to start the conversation: it helps you state the question properly first.
This is a sheet, not a new page: home is still visible behind it, closing it returns you exactly where you were, and it does not interrupt what you were doing. The assistant is driven by DeepSeek (the screen says v1.0.50) and is positioned as “link-finding” — it clarifies your thinking, it does not send messages on your behalf.
| Element | What it shows | How you use it |
|---|---|---|
| Title and version | “AI Member Assistant” plus “Link-finding · powered by DeepSeek v1.0.50” | Quote the version number when you report a problem |
| Welcome line | “Tell me what resources or connections you want to link, and I will help you think it through” | It asks what you want to link, not who you want to meet — state the purpose first |
| Three suggested questions | “How do I turn my network into a reusable asset?” / “I am looking for cross-strait OPC partners” / “What should I say the first time I meet a client?” | They map to: building awareness / concrete action / preparing your wording. If you do not know what to ask, tap one |
| Input box | “Any question about your network…” | You can keep asking follow-ups, the way you would talk to an advisor |
| × at the upper right | Close | Back to home; closing does not lose your place in the conversation |
- Tap the floating button → Assistant.
- Tap one of the suggested questions first to see how it answers.
- Then type your real situation: industry, city, what you want, what you can offer.
- Keep asking until you get one sentence you can actually act on.
Most people are not stuck because they lack resources — they are stuck because they cannot say what they want. So the first question is not “who are you looking for” but “what do you want to link”, which forces the vague “I want to meet some people” into the specific “I need a contract manufacturer in South China”.
The assistant gives suggestions and reasoning, and cannot promise the other person will reply. Never type anyone's phone number, ID number or undisclosed deal terms into the conversation.
Fig. 11-4
Opportunity Plaza
Uses randomness against the algorithmic bubble: it brings you the people and opportunities you would never have searched for.
The plaza works the opposite way to the directory. The directory is for when you know who you want; the plaza is for when you do not know who you need. So it uses two mechanisms — random members (a new batch each time) and an opportunity feed (gatherings / opportunities) — plus “my collaboration card”, which turns you from passive to active.
| Element | What it shows | How you use it |
|---|---|---|
| Top banner | “Opportunity Plaza | random connections × opportunities happening now” plus three small cards: random members / themed gatherings / live opportunities | The three cards are three ways to use the page; tap one to jump to that section |
| My collaboration card | “One-tap poster: who I am and why I want to collaborate” | The most overlooked feature here: generate a poster about who you want to work with and post it in a group — far more effective than posting a business card |
| Random members | Three member cards (name, level, one-line tag) plus “Shuffle” at the upper right | Every shuffle is a new encounter; tapping a card opens the business card |
| Opportunity feed | Tabs: All / Gatherings / Opportunities; each card shows title, time, address and fee | Gatherings are offline events with a time and place; opportunities are collaboration proposals |
| Opportunity card | For example “Global Travel Club”, 11/14 14:00, No. 66, Lane 69, Section 2, Daxing West Road, Taoyuan District, Taoyuan City, free | Tap the card for details and to register |
- When you have a spare minute, tap “Shuffle”, look at three people, and open the card of anyone interesting.
- Tap “My collaboration card” to generate one and post it to your groups.
- Switch to “Gatherings” to see where you could go this week.
Search can only find the answer you already thought of. The plaza uses randomness plus curation to manufacture accidental connections — the part of a community that algorithms cannot replace, and the fastest way for a new member to build a first circle.
Random recommendations are a system rule, not paid placement. Event details in the opportunity feed are indicative; the event detail page governs. Confirm time, place and fee before registering.
11.2 Finding people: directory, filter, AI matching11-5 to 11-7
Three ways of finding people for three intentions — you do not know who (AI matching), you know the criteria (filter), you know the name (search).
Fig. 11-5
AI Matching (Discover)
Turns “flipping through the directory” into “one card at a time”: eight per day, then you stop, so you cannot scroll forever.
The design point here is not how clever the AI is, it is the pacing. The screen says “real-time matching · member data (rule-based)” — meaning matching is currently a rules calculation, not a generative model inventing stories. “Today's quota: 8 cards” turns browsing into something with a cost.
| Element | What it shows | How you use it |
|---|---|---|
| Header | “Matched for you” plus “Discover / high-fit business connections” and “609 people nearby” on the right | 609 is the size of the pool, not the number of recommendations |
| Quota line | “Today's quota: 8 cards” plus “Standard member (more with each upgrade: Advisor 15, Chapter president 25, FP 30)” and “Upgrade” | When the quota runs out you wait for tomorrow; upgrading raises the daily count |
| Rule-based label | “Real-time matching · member data (rule-based)” | An honest label: this is rules matching today, not free-form AI generation |
| Large profile card | Full-bleed photo, “50% fit” at the upper right, arrows left and right | The arrows move to the next person; the fit percentage is a reference, not a promise |
| Identity and three metrics | Zeng Guodong, FP-L / Licheng District, Quanzhou, Fujian; 36 visitors, 7 trust likes, 3 shares | Three numbers: how many looked at him, endorsed him, passed him on |
| Tabs | Profile / Work / Education / Skills / Video / Posts | Check “Profile” for fit first, then “Posts / Video” for what he has actually done |
| Matching fields | Industry, region, level, “What he offers”, “What he is looking for”, bio | Whether “offers” and “looking for” intersect is your entire decision |
- Read the “What he offers / What he is looking for” lines first.
- Only if they intersect, switch tabs and look at his work.
- If they do not, move to the next card — do not waste the quota.
- If they do, message or invite.
The limited quota is deliberate: it makes you look properly instead of swiping fast. The platform wants a small number of high-quality openings, not a large number of views.
“50% fit” is a rules calculation (weighted industry, region, level and so on) and says nothing about the other person's willingness. Quota numbers may change between versions; the page is authoritative.
Fig. 11-6
Member Showcase (directory)
Three ways of finding people on one page: search if you know the name, filter if you know the criteria, browse by industry if you know neither.
The directory is the most basic asset on the platform. What matters is not how many people are in it but whether it can be sliced. This page splits three intentions into three entries: the search box (known), the multi-filter (partly known), the industry grid (unknown).
| Element | What it shows | How you use it |
|---|---|---|
| Search box | “Enter a name to search” | The most used path after a referral: someone gives you a name, you find them in thirty seconds |
| Multi-filter card | “Level · industry · region · distance, narrow it in one pass” plus “Start” | Four dimensions crossed — built for queries like “an FP-L in Taipei in tech” |
| My network banner | “Global network map · network structure · meet offline” | Opens the network asset summary (figure 11-8) |
| Industry grid | Beauty / Travel / Blockchain / AI / Internet / Mind and body / Telecom / Agriculture… | How to browse when you do not know who you want; scrolls vertically |
| Three tabs | Nearby / By home region / By level | Nearby is geography; home region is fellow natives (especially useful in cross-strait communities); level is circle |
| List card | Name, level, region, distance (1976.4 km), industry | A cross-sea distance means cross-strait; tap the card for the full profile |
| Floating button at the bottom | “Seven-axis network radar” | Jumps to the “choosing people” view (figure 11-9) |
- Have a name → search directly.
- Have criteria → use the multi-filter.
- No idea → tap an industry icon or switch to “By home region” to find fellow natives.
- Found someone → tap the card → save or message.
The “By home region” tab is the most locally distinctive design on the platform: in a cross-strait community, where you are from builds trust faster than what you do.
Distances are straight-line estimates and are hidden for members who did not grant location permission. The directory only shows members who agreed to publish their details.
Fig. 11-7
Multi-filter (filter panel)
Four groups of criteria, set once, and it tells you how many people you will get before you press the button.
The classic mistake with a filter panel is finding out you have zero results only after pressing. Here the button itself reads “See 611 people” and updates as you tick boxes — you know the size of the result before you commit.
| Element | What it shows | How you use it |
|---|---|---|
| Search bar | “Search name / industry / city” plus “Filter” on the right | Search and filter stack; you can use both |
| Result preview | “611 members match (showing the nearest 50)” | Know the size of the pool first; only the nearest 50 are listed, so tighten the criteria to see more |
| Member level | All / Chapter president / Advisor member / FP-M / FP-L / Member / Standard member / Other | Level equals circle and entitlements — decide which layer you want first |
| Industry | All industries / Health and wellness / Professional services / Education / Finance / Technology / Healthcare / Wholesale and retail / Manufacturing / Construction / Agriculture / Entertainment / Human resources | Pick the two or three that genuinely apply, not all of them |
| Region | All regions / Taipei / Taichung / Kaohsiung / New Taipei / Foshan / Shanghai / Wuhan / Xiamen / Suzhou / Guangzhou / Beijing / Tainan | Mainland and Taiwan cities side by side — that is the real footprint of a cross-strait community |
| Distance | Any / 3 km / 5 km / 20 km | If you want to meet this week, use 3 km |
| Bottom buttons | “Reset” / “See 611 people” | The number changes as you tick — that is your result preview |
- Tick a level
- tick industries (three at most)
- choose a city
- set a distance only if you need to meet
- read the number on the button and loosen one criterion if it is too small
- press “See N people”.
Moving the result count onto the button is a tiny design decision that removes the biggest frustration: not failing to find people, but not knowing why you failed.
Only the nearest 50 matches are listed. The distance filter depends on whether the other person has shared their location, so members who have not may drop out of the results.
11.3 Network assets: my network and the seven-axis radar11-8 to 11-10
From “how many people” to “how worth knowing are they”: three screens forming one chain of judgement from coarse to fine.
Fig. 11-8
My Network (network asset sheet)
Turns your network from a feeling into a balance sheet: how many countries, cities, people and companies.
The key word on this page is definition. 612 total, 425 referral chain, 32 interacted — three numbers answering three different questions. Mixing them is self-deception: 612 is how many people, 425 is how many relationships have a source, 32 is how many relationships are still alive.
| Element | What it shows | How you use it |
|---|---|---|
| Update time | “Network assets · updated daily at 06:00” | What you added yesterday shows up today — do not read it as real-time |
| Four KPIs | 3 countries / 101 cities / 425 connections / 22 companies | Four dimensions: countries, cities, individuals, organisations |
| Three definitions | All 612 / Referral chain 425 / Interacted 32 | All is the directory total; referral chain is relationships with a source; interacted means there has been actual exchange |
| Definition note | “Only members in the referral chain are shown” plus “How are these two counted?” | Tap to see the calculation and avoid misreading |
| Global network map | 301 of 612 have coordinates; red dots graded by density (20+, 6–19, 5 or fewer) | See at a glance which cities your relationships cluster in |
| Map filters | Industry ▾ / Level ▾ | For example, map only “tech FP-L” |
| Network distribution | Cross-strait 142 / Mainland 200 / No region 83 | Three bars showing your geographic structure — and how many profiles are incomplete |
- Read the four KPIs to get the overall picture.
- Switch to “referral chain” to see the relationships that actually have a source.
- Switch to “interacted” to see which are still alive.
- Use the map to find which cities you have people in.
- Before a trip, look at those names.
The referral chain is the biggest difference between this platform and a generic social app: relationships have a traceable source. 425 is worth more than 612 because it means somebody was willing to vouch for the relationship.
The three definitions cannot be added together or compared (612 ≠ 425 + 32). 301 of 612 having coordinates means nearly half of members have no region on file, and data completeness directly affects both the map and every filter result.
Fig. 11-9
Seven-axis Network Radar (choosing people)
This page is not about finding people, it is about choosing them: who is worth the time before you spend it.
The seven axes are peer review, profile, activity, content, hosting, attendance and connecting. They break “can I rely on this person” into seven observable things, each drawn from real back-end records. The note on screen matters: trade reviews only score once F1 ships, so it currently shows 0 honestly and is excluded from the average.
| Element | What it shows | How you use it |
|---|---|---|
| Definition line | “Peer review · profile · activity · content · hosting · attendance · connecting”, all seven from back-end records | Understand what the seven axes are before you read the score |
| Honest note | “Trade reviews (F1) only score after launch; shown as 0 for now (excluded from the average)” | So what you see today is a six-axis average, not seven |
| Perspective tabs | Overall radar / Profile completeness / Content / Event hosting / Event attendance | Looking for someone who runs events? Switch to event hosting |
| Level chips | All 670 / Chapter president 29 / Advisor member 2 / FP-M 12 / FP-L 57 / Member… | Lock the layer first, then look at scores |
| Talent card | Name, level, title (New Light / Trust Cultivator), industry · city, radar score (4.6 / 3.5) | Titles are behavioural labels, not ranks |
| Four counters | Posts 5 · hosted 10 · attended 48 · communities 4 | Tells you at a glance whether someone is a content type, a host type or an attendee type |
| AI recommendation reason | “He has hosted 10 events and is a convener in his circle” | The reason matters more than the score: the score says high or low, the reason says why |
| Bottom metrics | Likes received 10 · shares 11 · card visitors 83 | External validation: how many endorsed, passed on, or actively looked at him |
- Decide which kind of person you want (hosts events / writes content / complete profile).
- Switch to the matching tab.
- Narrow by level.
- Read the “AI recommendation reason” rather than only the score.
- Tap “See seven axes” for detail (figure 11-10).
- Decide whether to open the conversation.
The right order for choosing people is: behavioural evidence (how many events hosted, how many posts written) → external validation (likes, shares) → score. The score is a summary; the evidence is the substance.
The radar score measures recorded behaviour, not character. A low score for a new member usually just means there is not much record yet. Scores update daily, so filling in your profile will not change them immediately.
Fig. 11-10
Seven-axis Radar detail (single person)
Breaks “how to become more credible” into seven things you could do this week.
The value of a radar chart is not whether the shape looks good, it is which axis is shortest. The shortest axis is what you should fix this week; the bar chart and the four notes below tell you how each axis is built.
| Element | What it shows | How you use it |
|---|---|---|
| Header | “Seven-axis radar / Radar score 4.6/5 · New Light” | Score and title side by side: read the score, then the type |
| Person row | Avatar, name, level FP-L, Professional services · Wuhan, 4.6 on the right | Confirm you are looking at the right person |
| Radar chart | Trade reviews 0 / Profile 4 / Activity 4.9 / Content 5 / Hosting 5 / Attendance 5 / Connecting 3.6 | Find the flat side of the shape — that is your answer |
| Bar detail | The same seven items as horizontal bars with values | Easier to compare than the radar; good for a screenshot to keep |
| Four notes | Profile = 8 items filled in with real details; Activity = login + sharing + card visitors; Content = 5 supply & demand posts; Trade reviews = 0 (not live, excluded from the average) | These four lines are the operating instructions for raising the score |
- Look for the lowest axis.
- Read the notes below to see what that axis is made of.
- Go back to “Me” and fill in the matching data (all eight real-detail fields, for example).
- Come back in a week to see whether it moved.
It turns abstract trust into an actionable list: not “you should be more trustworthy” but “your profile completeness is only 4, go and add two items”.
“One flat side” is normal — everyone has a weak axis. Scores update daily, so completed data does not show immediately. Trade reviews are not live yet: a 0 there does not mean you were rated badly.
11.4 Events: list and map11-11 to 11-12
Two readings of the same data: the list for dates, the map for cities.
Fig. 11-11
Event list
From “add your name in the group chat, sign a paper sheet on the day, lose touch afterwards” to a process with a record.
Events are the only channel that takes an online relationship to offline trust. This page is both discovery (city-first popular list) and entry (map view at the upper right, publish at the lower right). Note the small print in the middle: “same city (Taipei) first, then popularity · consistent rules, not AI prediction” — the sort logic is public.
| Element | What it shows | How you use it |
|---|---|---|
| Status tabs | All / Open for registration / In progress / Finished | The first thing to do before registering: switch to “Open for registration” |
| Map view | Map icon at the upper right | Switch to the map to see which city is active (figure 11-12) |
| City-first popular | “5 popular in your city” plus “same city first, then popularity” | What you see is explainable, not a black box |
| Small horizontal cards | Cover, title, date and weekday, venue, category tag (for example “Resource matching · business exchange”) | Scan title and category to decide whether to open it |
| Large event card | Host (name and level), category tag (for example “Me time · travel together”), title, time, venue, “Members” (level restriction), fee, popularity, distance | The “Members” line decides whether you are eligible — read it first |
| Two floating buttons | Map toggle / “+” to publish | “+” requires publishing permission (see chapter 12) |
- Switch to “Open for registration”.
- Check the “Members (level)” line to see whether you qualify.
- Tap a card for details.
- Register (payment may be required).
- On the day, scan to check in (if the host enabled check-in).
Writing the sort rule on the screen is a rare piece of candour: same city first, then popularity. Users stop wondering why they keep seeing another city.
Popularity is a rough count of views and follows, not registrations. “Distance” is straight-line. A fee shown as “free” means the registration fee is zero; anything you spend on site is separate.
Fig. 11-12
Event map (map view)
See which city is active: before a trip, check whether the destination has anything on this week.
The same event data in a different coordinate system. The list answers “what is on this week”; the map answers “where it is happening”. For people who travel between cities often, the map is more useful.
| Element | What it shows | How you use it |
|---|---|---|
| Event bubbles | Thumbnail plus title, for example “Taiwan experts charity health day” (Tianjin), “305HK × WeaveInX: cross-strait goat milk industry cooperation summit”, “Cross-strait livestream e-commerce festival (Taiwanese youth under 45)”, “Craftsmanship snacks: 2026 first investment fair”, “[7/10 Shenzhen Luohu] business afternoon tea · resource matching salon” | Tap a bubble to open the event |
| Map controls | Drag, pinch to zoom | Zoom to the city you are going to, then read bubble density |
| Bottom-right buttons | List icon / “+” | Back to the list, or publish a new event |
- Drag to the city you are going to.
- Judge from the number of bubbles how active that city is.
- Tap a bubble for details.
- Switch back to the list at the lower right to compare dates.
The distribution of bubbles is itself intelligence: which cities hold events regularly, which hold one or two a year. Free input for choosing venues and planning trips.
The map only plots offline events with an address. Purely online events (format = online) do not appear.
11.5 Map and Supply & Demand11-13 to 11-14
One answers “who do I know in that city”, the other “who is looking for what right now”.
Fig. 11-13
Member map (world)
This is “where in the world my network is”, not “who is near me”.
Different from the previous map: People Radar (figure 11-2) is centred on you; the member map uses the world as its base. The first answers “who can I see today”, the second “who do I know in that city”.
| Element | What it shows | How you use it |
|---|---|---|
| World map | Asia / Oceania view with members scattered as avatar bubbles | Zoom to the city you are going to |
| Avatar bubbles | Huang Mingxun, Lin Luobo, Ge Mei, Hu Zhi…, Zhu Licheng, Huang Chuanwei, Li Xin, Hang Zhang, YJ and others | Tap an avatar to open the business card |
| Expand list | “Expand list >” at the upper left | When bubbles overlap, switch to a text list |
| Map attribution | “Tencent Maps ©2026 Tencent GS(2026)1190” at the lower left | A compliance label that must be kept in the production build |
- Open it before going abroad or on a trip.
- Zoom to the destination.
- Tap an avatar to see who it is.
- Message before you fly: “I will be in XX next week — time for a coffee?”
Network value is strongly geographical: the same person who has no time in Taipei may be happy to talk when you turn up in Shenzhen. The map makes “being on the way” something you can plan.
Only members who filled in a region and agreed to publish appear. When several people share a city their bubbles overlap — zoom in or use “Expand list”.
Fig. 11-14
Supply & Demand
Turns “I have a need” into a public, searchable request that people can respond to, instead of something buried in chat history.
Supply & Demand is the only module on the platform with two-way exposure: post once and every member sees it; they post once and you see it. Its categories are not industries but intentions — collaboration, hiring, crowdfunding, events, questions.
| Element | What it shows | How you use it |
|---|---|---|
| Intention tabs | All / Collaboration / Hiring / Crowdfunding / Events / Questions | The wrong category means sending it to the wrong people — the most common mistake here |
| Search | Magnifier at the upper right | Search old requests by keyword (many people do not know this exists) |
| Post card | Avatar, name, level (standard member / FP-L), date, phone icon at the upper right, excerpt, attached image | The phone icon contacts them directly if they allowed it |
| Interaction row | Shares / likes / views / comments (for example 1 like, 40 views, 0 comments) | High views with zero comments usually means “I understood it but did not know how to reply” — make the ask explicit in the title |
| Floating “+” | Publish | Posts go through review (see 6.3) |
| What posts look like | Example 1: “Life regeneration business briefing [2026 national tour, August, Xiamen]”. Example 2: “Guangling, Shanxi, home of millet — refining millet germ oil and fibre from millet” | Supply & Demand is not only “what I need”; it also carries “what event I am running” and “what goods I have” |
- Switch to an intention such as collaboration or hiring.
- Search with keywords to check whether it has already been asked.
- If not, tap “+” and post.
- Write the title as what you need + to what specification + by when.
- After posting, watch the comments and the phone.
A request's life cycle becomes visible, from open to closed, which builds the social proof that deals really do happen here. Posts also accumulate into your content score (figure 11-10).
Posts are reviewed, and wording about investment, medical claims or student recruitment is often rejected. Never put a personal mobile number or ID number in a public post.
11.6 Me: the centre and five data views11-15 to 11-19
Five screens, five dashboards: personal overview, data board, annual settlement, event performance, market trend.
Fig. 11-15
Profile (Me)
Your CV, your report card and the master switch for every setting, all on one page.
Three layers: identity (avatar and brand card), results (four metrics), drawer (four entries). Many people treat it as a settings page, but it is the page most worth tending — your primary field and secondary development directly determine who finds you.
| Element | What it shows | How you use it |
|---|---|---|
| Top row | Avatar, name, notification bell (one red dot) | The red dot means unread notifications; tap to see who has been looking for you |
| Brand card | FP-L / Taipei City / “Edit brand” | Editing the brand changes your primary field and secondary development — the core of your exposure |
| Primary field | Chips: Technology, Founder of WX WeaveInX | These two phrases are the keywords people find you by |
| Secondary development | Tags: cross-strait integration, capital market enablement | Your second curve; it is how others judge whether there is another angle for collaboration |
| Four metrics | 45 Pulse Credits / 159 connections / 248 card visitors / 35 likes received | Credits are redeemable; connections are scale; visitors are passive exposure; likes are endorsement |
| Four entries | Feature centre (88 modules · 569 real data points) / Data board / My network / My team | The feature centre is the master index; the other three are three kinds of dashboard |
- Tap “Edit brand” and write your primary field as industry + role.
- Add two secondary development tags.
- Open the data board and see which metric is zero.
- Go back and fix that one.
“248 card visitors” is a passive metric: it is not you going to meet people, it is people coming to look at you. That number says more about the quality of your exposure than your connection count does.
Credits and likes are two different assets (credits are redeemable, likes affect trust) and should not be conflated. Visitor counts are cumulative, not real-time.
Fig. 11-16
Data board (personal overview)
Turns “how am I doing” into six numbers, then gives you a shortcut to fix them.
The first line on the board reads “choose the data set you want to see · 18 of 18 available” — it admits that this is a collection of data sets, not one pretty chart. The real way to use it: find the cell that is zero and tap the entry beside it.
| Element | What it shows | How you use it |
|---|---|---|
| My content data | Supply & demand posts 0 / Posts 2 / Videos 0 / Events hosted 20 / Events attended 105 / Card visitors 248 (live count, excluding saves) | The zeros among the six are next week's homework |
| Content extension row | “Saves 35 · shares 166 · for your content score see My seven-axis radar” plus “See radar” | Jumps from number to diagnosis (figure 11-10) |
| My team | Open circle · bind members · invite code | A team is a different network structure and is counted separately from your personal network |
| Communities and organisations | Community list (new: seven categories · price · closed status) / organisation list (old version, entry only) | Prefer the new version; the old one is a compatibility entry |
| Growth and assets | Growth centre (festivals / health checks / itineraries / tasks / CV in one place) / My CV (work, education, awards, work samples — searchable) | The CV is another way to be found, and many people leave it blank |
| Event data | My events | Goes to figure 11-18 |
- Scan the six cells for zeros.
- Tap “See radar” to find which axis is dragging.
- Use the entries below to fix it (post a request, upload a video, host a small circle).
- Come back in a week and compare.
Hosting 20 events and attending 105 says this user is an attendee rather than a host. That is not a flaw, it is a strategic choice — but if they want a higher radar score, hosting is the fastest lever.
“My team” only has data after members are bound. Figures are live counts and exclude saves and indirect metrics. The old “organisation list” keeps only an entry; its function has been replaced by the new communities.
Fig. 11-17
Network asset annual report 2026
Settles a year of social labour into an asset statement you can share.
The annual report is the most shareable page on the platform. It does not just give numbers, it gives three narratives — seen, trusted, remembered — turning cold statistics into your own year-end summary. The attached referral code turns sharing into inviting.
| Element | What it shows | How you use it |
|---|---|---|
| Title and identity | “Network asset annual report 2026” / YJ, Technology, FP-L | The report is tied to an identity, so people know whose numbers these are when you share it |
| Six metrics | 248 card visitors / 35 likes / 166 shares / 2 posts / 197 content reads / 8 community links | Exposure (visitors) → endorsement (likes) → spread (shares) → deposit (content and reads) |
| Referral code | “My referral code WX00000022” plus “entering this code at sign-up makes your account your referral” | Attach the code when sharing and the invitee sits under your referral chain |
| Two buttons | “Copy” / “Share report” | Copy pastes into WeChat; share generates an image |
| Narrative 01 | Seen: “248 people opened your card, an average of 21 a month. This is not a scroll-by impression — somebody chose to tap in.” | Turns the number into meaning |
| Narrative 02 | Trusted: “35 likes, shared 166 times. Of every 100 visitors, 14 chose to do something.” | Only people who act are people you can talk to |
| Narrative 03 | Remembered: “2 posts, 197 reads. Content is the only thing that speaks for you 24 hours a day.” | Content is your passive salesperson |
- Open the report and read the six metrics.
- Read the three narratives and identify your strength and your gap (in this example: strong exposure, weak content).
- Tap “Copy” and send the referral code to whoever you want to invite.
- Tap “Share report” to generate an image for Moments or a group.
It answers the hardest question in community building: what did I actually accumulate this year? Not follower count, but how many people sought you out, endorsed you, passed you on, and remember what you said.
The numbers are cumulative totals, not this year's increment. Before sharing publicly, check that you are comfortable making these numbers public (visitor and like counts, for example).
Fig. 11-18
My events
The thing a host fears most is many registrations, few arrivals. This page opens the funnel so you can see where people drop out.
Two levels on one page: yours on top (20 events hosted, 288 registrations) and the platform's below (82 events all-time, 824 registrations). Keeping them apart matters — your 20 events are a quarter of the platform's 82, which is your weight here.
| Element | What it shows | How you use it |
|---|---|---|
| Search and filters | Search event name or category; all events / hosted by me / attended by me; any time / last month / last three months / this year, plus category | Start with “hosted by me + this year” |
| Four summaries | 20 events hosted / 288 registrations / 79 members reached / 30 actual check-ins | Registrations versus check-ins is your attendance rate — the number to watch |
| Platform overview | 82 events all-time / 824 registrations / 260 check-ins / 114 members reached / 35 events attended by me | Where your events sit within the platform |
| Monthly counts | Feb 2 / Mar 3 / Apr 2 / May 4 / Jun 2 / Jul 3 / Aug 2 / Oct 2 (eight months) | Look at the rhythm: a steady two a month, or clustered in a few months? |
| Matching events | “22 events match” | Actual row count after filtering |
- Switch to “hosted by me”.
- Compare registrations with actual check-ins to get the attendance rate (30 of 288, about 10% here).
- Compare against the monthly counts to find the bad month.
- Recall that event's timing, topic and fee, and change one variable next time.
A low attendance rate usually means nobody reminded them, not that nobody wanted to come. Enabling check-in (QR) plus a reminder the day before is the cheapest possible improvement.
Check-in counts only accumulate when the host sets “check-in required = yes”. Events without it show 0 — which means no record, not no attendance. The platform overview is site-wide, not personal.
Fig. 11-19
Data dashboard (platform / operator view)
The page an event organiser reads for decisions: which month dropped, which industry is biggest, what start time works.
Different from 11-18: that one is your report card, this one is what the market looks like. Pick one of four periods (last 7 days / last 30 days / year / all) and read three charts: monthly trend, industry split, time-of-day split.
| Element | What it shows | How you use it |
|---|---|---|
| Period switch | Last 7 days / last 30 days / Year (current) / All | Use the year for trends, the last 7 days for current heat |
| Four KPIs | 81 events / 806 registrations / 113 members / 7 industries | Four numbers to establish scale first |
| Monthly trend | 2026-02 4 / 03 6 / 04 12 / 05 23 / 06 18 / 07 5 / 08 8 / 09 3 / 10 3 (nine months) | May was the peak; September and October dropped sharply — a scheduling gap |
| Industry split, top 7 | Health and wellness 117 (14.5%) / Education 68 (8.4%) / Technology 61 (7.6%) / Other 36 / Professional services 35 / Wholesale and retail 27 / Other 84 (10.4%) | Decides who to invite next time: the top two are your base |
| Time-of-day split | Morning 6 (06:00–12:00) | If most events are in the morning, an afternoon slot is your differentiator |
- Switch to “Year” and read the trend.
- Find the month that dropped hardest.
- Use the industry split to choose a topic.
- Use the time-of-day split to choose a start time.
- Write those three conclusions into next quarter's schedule.
The real output of a dashboard is not a chart, it is a decision: which month, which industry, what time. Reading it without deciding anything is the same as not reading it.
Two separate bars are both labelled “Other” (36 and 84), which shows how inconsistent categorisation distorts the statistics — always use an existing category when publishing, never invent one.
11.7 Invitations, chain map and messaging11-20 to 11-22
Three screens for three moves that advance a relationship: invite to attend, see the structure, start the conversation.
Fig. 11-20
Targeted invitations (who to invite)
Turns a list into attendance: works out who to invite and where to go, with a reason attached to every suggestion.
The intersection of the events and network modules, and the most practical page on the platform. The score is not a black box: same city, same industry, same level, three rules added together, and the screen says outright that it is not a model guessing.
| Element | What it shows | How you use it |
|---|---|---|
| Claim | “Who to invite and where to go, worked out in one pass” plus “calculated live from your events, city and industry; every result comes with a reason” | Read this line and you know where the score comes from |
| Comparison basis | FP-L / Taipei City / Technology; “compared 809 members × 82 events” | The sample size is published, so nobody has to ask “on what basis” |
| Two perspectives | Who to invite (host) / Where to go (attendee) | Hosts use the left; people looking for something to attend use the right |
| Pick an event | Taiwan north-central-south | WX WeaveInX OPC training, 10/07 12:00, Taipei City / WX WeaveInX OPC public course, 09/27 21:30, Taichung City | Pick the event first; the list depends on it |
| Suggested list | “12 suggested | same city · same industry · same level, understandable”; Lin Xiuwen FP-L 80, Yin Xinghua Member 70, Lu Lixian FP-L 55, Wu Juanling FP-L 55 | The score is a proxy for likelihood of attending, not a guarantee |
| Reason | “Also in Taipei City, lowest cost to attend; in technology, the core audience for this event; FP-L, relatively active on the platform.” | The reason matters more than the list: it tells you what to say |
| Action row | Invite / view card; “0 selected (select all / clear)” plus “Forward invitation” and “Message them on WeChat” | Tick people, then send in a batch |
- Pick one of your events.
- Read the reasons for the top three high scorers and understand why they were chosen.
- Tick them (or select all).
- Tap “Forward invitation” — but change the first sentence.
- Remind them again the day before.
Invitations succeed not because the list is precise but because the person understands why you invited them. That is why the reason sits next to the name: copy the reason, not the same paragraph to everyone.
The score adds up same-city, same-industry and same-level rules and says nothing about willingness. Mass-sending one identical invitation usually gets fewer replies than a personalised one.
Fig. 11-21
Pulse Chain Map (referral circles)
How you were brought in, and who you brought in — a chain that cannot be overwritten and can be traced.
Four views (pulse chain tree / cloud relationships / referral circles / pulse chain circles) are four readings of one data set. The circles are best at answering one question: how far from me are my relationships? Chain 1 is direct referral; chain 4 is indirect twice over.
| Element | What it shows | How you use it |
|---|---|---|
| View switch | Pulse chain tree / Cloud relationships / Referral circles / Pulse chain circles (current) | Tree for structure, circles for distance, cloud for clustering |
| Level tabs | All / Chain 1 / Chain 2 / Chain 3 / Chain 4+ | Tap a level to list only that level |
| Statistics bar | Chain 1: 107 / Chain 2: 41 / Chain 3: 25 / Chain 4 and beyond: 186 | Chain 1 is who you referred directly; the numbers move as referrals happen |
| Circle chart | Centre “me” → +1 → +2 → +3 → +4 dashed rings, members plotted as dots | Dot size and colour encode level; hover to see who it is |
| Bottom total | 107 / 41 / 25 / 186 / 359 total | 359 is the number of people on the chain, not your whole network |
- Look at how many are in chain 1 (your core 107).
- Tap “Chain 2” to see who came in indirectly through you.
- Find the branch with unusually many in “Chain 4+” — that is usually an active convener.
A referral chain means traceability: who introduced you, and whom you introduced, both stay on the chain. That turns referral from a favour into an asset.
359 is not the 612 total network (figure 11-8): members with no referral source who signed up themselves are not placed on a chain level. Levels are computed from back-end referral records and cannot be set by the user.
Fig. 11-22
Member messaging (conversation list)
The move that turns a public business card into a private relationship, packaged as a manageable list.
Messaging happens inside the platform, not in WeChat. The advantage is that it is manageable (unread, search, find by industry); the disadvantage is that the other person may not see it immediately — so anything important still needs a phone number or a meeting.
| Element | What it shows | How you use it |
|---|---|---|
| Summary line | “32 conversations · 1 unread” / “30 have industry and region data” | Clear unread first; those with industry data are easier to judge |
| Search | Search name, industry, city or message content | Searching message content finds that sentence from three months ago |
| Unread only | Toggle on the right | A once-a-day clearing habit |
| Conversation rows | Avatar (red dot when unread), name, industry · city, last message, time | Times range from six days ago to 08-11, which tells you this is a list of long-term relationships, not a live chat room |
- Turn on “Unread only”.
- Reply one by one, and refer back to something specific (“the thing you mentioned last time”).
- Turn it off and search old conversations, for example searching “coffee” to find where you last agreed to meet.
The platform deliberately does not build a live chat tool: it wants purposeful conversation, not small talk. That is why the list shows industry and city — so you can judge whether this person is worth answering right now.
The other person may not be online. For anything important, leave a phone number or meet in person. Conversations are private correspondence and the platform does not disclose them without consent.
11.8 Business card, invitation sheet and communities11-23 to 11-25
The last three return to people and rooms: one card, one invitation, one space to gather in.
Fig. 11-23
Member detail (business card page)
The card page is their shopfront: the footfall at the door, the work on the wall, and the “message me” at the end.
Every path on the platform ends here. Top to bottom: image (large photo) → identity (name, level, region) → evidence (three metrics) → content (six tabs) → action (message).
| Element | What it shows | How you use it |
|---|---|---|
| Three buttons at the top | Save / Card / Share (purple) | Save adds them to your list; card saves an image; share passes them on |
| Identity block | Zhang Liqi, FP-L / Jianghan District, Wuhan, Hubei | Level and region are the two fastest judgements |
| Three metrics | 83 visitors / 10 trust likes / 11 shares | Visitors: how many sought them out. Likes: how many endorse them. Shares: how many passed them on |
| Six tabs | Profile / Work / Education / Skills / Video / Posts | Check the profile for fit first, then posts and video for what they have done |
| Voice introduction | “Not recorded yet” → “they have not recorded a voice introduction” | A differentiating field: most people leave it blank, so recording one is an advantage |
| Shared pulse chain | Shows whether you have a common referral source | A common referrer means you can open with “X sent me” |
| Bottom bar | Share / Address / Message | Address opens navigation; messaging is the main action |
- Read the three metrics (83 visitors means they are not obscure).
- Switch to “Posts” to see what they have done.
- Check “Shared pulse chain” for a mutual contact.
- Tap “Save”.
- Open with the mutual contact when you message.
“Trust likes” is a smart piece of design: it is not a like count, it is an endorsement from people who know them. Ten trust likes mean more than a thousand hearts.
“Save” is visible both ways — the other person may see that you saved them — so use it with that in mind. The card image contains personal information; confirm before forwarding it.
Fig. 11-24
Info sheet and “Ask them to talk”
The most honest page in this manual: there is no calendar here, so it hands you a paragraph you can actually send.
Most products would leave a “coming soon” calendar tab. This page does the opposite and says so: there is no member/schedule tab (it returns 404), so rather than leave a permanently blank page it helps you actually arrange the meeting. A constraint turned into a design.
| Element | What it shows | How you use it |
|---|---|---|
| Title and description | “Info sheet / Data we can actually read · only what the back end has” | States up front that it only shows data that really exists |
| Icon tabs | Seven-axis radar (31) / Messages / Activity / Itinerary | The 31 is an item count for the radar |
| Content tabs | Seven-axis radar / Basics / Offers-looking for / Links / Momentum / Itinerary (current) | Switch between different sides of the data |
| Time slot | Today / Two days / This week / Next week / You decide | “You decide” gives the other person the most flexibility and usually gets the most replies |
| Format | Online call / Coffee / I visit you / Phone call first | For a first meeting, “phone call first” or “coffee” is cheapest for both sides |
| What to discuss (optional) | For example: cross-strait channel partnership, an AI implementation project | Filling this in triples the success rate: they know what to prepare |
| Compose the invitation | One tap produces a paragraph you can send as is | Always change the first sentence afterwards, or it reads like a template |
| Footnote | “Choose a slot and a format and this composes an invitation you can send… rather than leave it blank, we would rather you actually meet.” | That is the design rationale, stated rather than guessed |
- Choose a slot (if unsure, “You decide”).
- Choose a format (phone call first for a first meeting).
- Fill in one sentence under “what to discuss”.
- Tap “Compose invitation”.
- Copy it into WeChat or a message, change the first sentence, send.
Invitations usually fail not because the other person is uninterested but because they do not know what would be discussed or how long it would take. Stating time, format and topic changes the reply rate immediately.
The generated text is a template; sending it unchanged looks like a mass message. The “itinerary” tab currently has no back-end data — a known limitation (see 6.3).
Fig. 11-25
Communities (the seven and the list)
The platform is a square; a community is a small room. Most real collaboration happens in the small room.
Communities gather the same group of people into a space that can be managed, interacted with and charged for: alumni, chambers, industries, projects, brands, certification, alliances. The list separates entry thresholds by price state (free / annual fee / closed).
| Element | What it shows | How you use it |
|---|---|---|
| Search | “Search communities, organisations, people” | All three can be searched, not only communities |
| The seven categories | Alumni chain / International chamber / Business chain / Projects / Brand collaboration / WX certification / Business alliance / OPC network (eight icons in total) plus “All >” | A browsing taxonomy; the icon count does not match the “seven” heading — an interface copy issue |
| Community total | “30 communities in total” | Small enough to browse one by one |
| Price tabs | All / Free / Annual fee / Closed | New members should start with “Free” to test the water |
| Community card | Logo, name, “View details”, price state on the right (free / annual fee / closed) | For example EUDA, Cross-strait Comics OPC, Suipei OPC, Prime Generation OPC, Cross-strait Youth OPC — all free |
- Switch to “Free” and browse.
- Tap “View details” to see members and rules.
- Apply to join (annual fee and closed communities need approval).
- Introduce yourself first, then post your first request.
The value of a community is shared language and shared rules, not headcount. A thirty-person industry community will often close a deal faster than a six-hundred-person square.
The heading says “seven communities” but eight icons are shown (the extra is “OPC network”) — a known interface copy issue, listed in appendix F. Closed communities require an invitation or approval.
12Publishing an event
This chapter is for the person running the event: from tapping “Me → Publish event” to the event appearing in the list and on the map, that is 18 fields, 4 states and 2 check-in methods. The chapter is written from two real sources — the internal training deck “WX WeaveInX event system” (10 pages) and real-device screenshots of the current publishing form. Where the two disagree we say so (see 12.1) rather than smoothing it over for either side.
12.1 Who can publish, and how bigFour tiers: 8 / 20 / 40 / unlimited
Publishing rights and headcount limits are tied to your membership level. After the form update on 9 November 2026, the event types are four tiers again — Small Circle, Gathering, Mid Gathering and Convergence, with limits of 8 / 20 / 40 / unlimited. This matches the internal training deck; the earlier claim that “there are only two tiers and a Gathering is capped at 10” no longer holds.
| Type | Limit | Role in the deck | What it suits |
|---|---|---|---|
| Small Circle | Up to 8 | Standard member (circle host) | Four for dinner, six for tea, one-to-many advice. Few enough that everyone can finish describing what they do — the easiest tier to close a deal in |
| Gathering | Up to 20 | Circle host | Themed exchange, a talk, an industry meet-up. Twenty is the ceiling at which everyone still gets a chance to speak |
| Mid Gathering | Up to 40 | Advisor member | Practical training, chapter meetings, policy briefings. At this size the stage and the audience start to separate |
| Convergence | No limit blank = unlimited | Chapter president | Forums, investment fairs, annual conferences. Capacity is set by the venue and catering, not by the system |
12.2 How to get there, and the four statesThree taps to the form
Four states, four different jobs
| State | What it means | What you should do |
|---|---|---|
| All | Everything you have published, including under review, live and rejected | For stock-taking: history and current status in one pass |
| Under review | Submitted, not yet approved | If it takes longer than expected, contact your core association or headquarters to speed it up |
| Live | Approved, including past and ongoing events | Share the link, chase registrations, read the list |
| Rejected | The application did not pass | Revise as suggested and publish again — you do not have to retype everything; use “Reuse” from 12.8 |
12.3 Field by field (first half)The basics and the money
The form has two halves. The first decides what this event is and what it costs; the second decides where, when and how people check in. Fields are listed in screen order. An asterisk means required.
| Field | Rule | How to fill it well |
|---|---|---|
| *Event type | One of four: Small Circle / Gathering / Mid Gathering / Convergence | Up to 8 for a dinner → Small Circle; 10–20 for a themed session → Gathering; 20–40 → Mid Gathering; an open public event → Convergence. Options lock if your level is insufficient |
| Headcount limit | The ceiling follows the type: 8 / 20 / 40; blank for Convergence. Exceeding it is blocked | Better low than high: type 6 for a six-person tea and open another when it fills. Filling in less than the ceiling costs you nothing |
| *Event title | Free text | Topic + audience + format, for example “Cross-strait channel matching | Taiwanese businesses | six-person round table”. Never just “Exchange meeting” |
| *Category | Pick a subcategory from the six groups (see 12.5) | The category decides who sees it; the wrong one sends it to the wrong people |
| *Fee (CNY) | Enter 0 for free; the unit is renminbi | Charging filters for intent; free maximises reach. For a first event, free or cheap |
| *Refundable | Yes / No | “Yes” converts better, but you handle the refunds yourself |
| *Cover image | 3:2 recommended | A face plus title text works best; do not use a screenshot of text |
12.4 Field by field (second half)Venue, timing and detail
| Field | Rule | How to fill it well |
|---|---|---|
| *Carousel images | 686×320 recommended | The top carousel on the event page: two to five images of the venue, the speaker and previous sessions |
| Contact phone | Optional | If you fill it in, questions come straight to you; use a service number if you do not want to be called |
| *Format | Online / offline | Online events never appear on the event map (see the note on figure 11-12) |
| *Venue | Address for offline, URL for online | Take the address down to the door number, or the map pin drifts |
| *Registration deadline | Date-time picker | It can match the end time, so latecomers can still register |
| *Start time | Date-time picker | Set it 15 minutes before the real start to absorb lateness |
| *End time | Date-time picker | Leave a buffer — winding down and networking always overrun |
| *Event detail | Rich text: bold, italic, underline, lists, alignment, colour, size, images | Five fixed sections: what this is / who it suits / what you take away / the run sheet / the speaker. Images and links are allowed |
12.5 Categories: six groups and their subcategoriesThe wrong category sends it to the wrong people
A category is not decoration, it is the distributor of exposure: users filter by it and judge from it whether an event concerns them. The subcategories below were copied one by one from the current picker, so you can choose straight from the list.
| Group | Subcategories |
|---|---|
| Resource matching | Capital–industry matching, supply–demand matching, technology transfer, investment promotion, going global, business exchange |
| Knowledge | Private board (closed door), practical training, policy briefing, experience sharing |
| Circle and social | Exchange tea, business dinner, corporate study tour, alumni gathering, same clan or home region |
| Me time | Sport and leisure, arts gathering, craft workshop, hobby group, travel together, family time, healing and relaxation, pet social, everyday meet-up |
| Public good | Public action, volunteering, charity fundraising (per the six groups in the deck; the picker is authoritative on the actual items) |
| Major events / WX official | Annual conference, forum, official course (official and authorised roles only) |
12.6 Fees, refunds and the split10% / 90%
There is only one money field, fee (CNY), but three things the host has to decide behind it: pricing, refunds and the split.
| Item | Rule | What it means for the host |
|---|---|---|
| Currency | Renminbi (CNY); 0 means free | For cross-strait sessions, convert yourself and state the currency in the title, to avoid disputes after registration |
| Platform fee | 10% of the event fee is the Pulse Chain system management fee | Price the 10% into your cost — do not treat your net receipt as the list price |
| Host share | The remaining 90% is returned to the account the host nominates | The receiving account must be set up in advance; cross-border arrival times and transfer fees are separate |
| Refundable | Yes or no at publishing time | “Yes” converts better but you must allow time to process refunds; if “no”, say why in the event detail |
12.7 Check-in and visibilityWho can see it, how people check in
The three switches at the bottom of the form decide who can see the event and how people check in. They are hard to change once published, so confirm them before you submit.
| Switch | Options and meaning | How to choose |
|---|---|---|
| *Check-in required | No / Yes. Only “Yes” records actual attendance | Want an attendance rate or certificates? Choose Yes |
| *Visibility | Open to all (all information public, detail page reachable) / Members only (only members can view) | Recruiting and reach → open; internal training or sensitive topics → members only |
| *Non-member registration | Allowed / not allowed | Open it to use the event as a funnel; restrict it to protect member value |
(1) Self check-in — the host displays a QR code and guests scan it. Good for few staff and many guests.
(2) Host check-in — the host scans each guest's event QR code. Good when identities must be verified one by one.
The current form only has the yes/no switch; choosing between the two methods happens on the event management page, not here.
12.8 Publishing history and “Reuse”From the second event, half the work
At the lower left of the form there is a clock icon, “Publishing history”. It lists the events you have run, each with a “Reuse” button that copies every field into a new form; you only change the date, venue and title.
When to use “Reuse”
- A series: a monthly meeting or a quarterly course. Copy, change the date and the topic.
- Same venue, different topic: venue, fee and check-in settings identical; only the copy and cover change.
- After a rejection: revising is far faster than retyping.
12.9 What it looks like once publishedThe seven fields on the card
Once approved, the event appears in the Events tab list and on the map (see figure 11-11 and figure 11-12). The list card has exactly seven fields, all of them taken from what you typed — so while filling the form you are not thinking “just get it done”, you are thinking “what will this card look like”.
| On the card | Comes from | What it decides |
|---|---|---|
| Host name and level | Your member profile | Trust; people dare to register for events run by senior members |
| Category tag (for example “Me time · travel together”) | *Category | Whose filter it appears in |
| Title | *Event title | Eighty per cent of the click-through |
| Time (with weekday) | Start time | Whether they can come at all |
| Venue | *Venue | Whether it is reachable this week |
| Members: level restriction | Non-member registration + visibility | Who is eligible |
| Fee / popularity / distance | Fee / view data / distance | The last threshold |
12.10 Twelve checks before you submitTick every line before pressing submit
- The title carries topic, audience and format, and a stranger can understand it.
- The category reflects the main output, not the secondary one.
- The headcount is filled in, does not exceed the tier ceiling (Small Circle 8 / Gathering 20 / Mid Gathering 40; blank for Convergence), and matches the venue.
- The fee is in CNY, 0 means free, and the detail says whether food and drink are included.
- The refund policy is chosen and the conditions are written in the detail.
- The cover is 3:2, carries title text, and is not last event's image.
- There are two to five carousel images at 686×320, with no unauthorised portraits.
- The format (online / offline) matches the venue or URL.
- The registration deadline is in the future, and the start and end times leave a buffer.
- The detail has all five sections: what it is, who it suits, what you take away, the run sheet, the speaker.
- You have decided on the check-in switch (whether you want an attendance rate).
- Visibility and non-member registration match the purpose of this particular event.
12.11 Common sticking pointsFind the symptom
| Symptom | Likely cause | What to do |
|---|---|---|
| Submitted, stuck on “under review” | Manual review queue, or the material needs something added | Contact your core association or headquarters to expedite; meanwhile check the detail for sensitive wording |
| Rejected, and you cannot see why | Usually fees, medical or investment claims, or someone else's portrait | Revise as suggested; copy via “Publishing history → Reuse” rather than retyping |
| Published, but not in the list | The event ranks lower in your city, or registration has closed | Search by event name, or send people the share link directly |
| My event is not on the map | Format was set to online, or the address only goes down to the city | Change to offline and add a door-level address (online events never appear on the map) |
| Check-in count stays at 0 | “Check-in required” was set to No | Turn it on for the next event; finished events cannot be backfilled |
| Very low attendance (many registered, few came) | No reminder, a free event, too early or too far | Message them the day before, charge a small fee, and pick a venue reachable by metro |
AThe new member's seven-day action card
This page is for people who have registered and do not know what to do next. One thing a day: after seven days you will have a profile that can be found, believed and passed on.
| Day | What to do | Time | How (section) | What "done" looks like |
|---|---|---|---|---|
| D1 | Write your one-line positioning and your trade | 10 min | 2.3, template ① | The line on the list page tells a stranger who you help and with what |
| D2 | Write "can offer / looking for" | 8 min | 3.6 / 3.2 | Both columns contain concrete nouns and numbers, not adjectives |
| D3 | Post your first demand | 10 min | 3.4, examples | Title carries result plus scale plus timing, with two or three tags |
| D4 | Look at five contacts, message one | 12 min | 3.2 / 3.3, template ④ | One three-sentence message with context sent |
| D5 | Join one community and speak | 8 min | 3.11 | One self-introduction posted in the community group |
| D6 | Sign up for one event (a Small Circle first) | 5 min | 3.10 | A registration and a check-in code appear in My Events |
| D7 | Review the seven dimensions, act on the lowest | 6 min | 3.8, Table 3-11 | You know what to fix next instead of grinding blindly |
The tick-box area (print this page)
- D1 My one-line positioning: ____________________________________
- D2 What I can offer: __________________________________________
- D3 The title of my demand post: ______________________________
- D4 Who I messaged, and why: _________________________________
- D5 The community I joined: ___________________________________
- D6 The event I signed up for, and its date: ____________________
- D7 My lowest dimension is: __________, the action I will take: __________
BThe one-page starter sheet (printable)
This page is deliberately designed so that forwarding it on its own causes no offence: give it to someone who has just been invited, and one sheet covers the five things they need to do. Print it, or screenshot and send it.
program
code
- Scan in — ask whoever invited you for their QR code. Scanning records your referral on the chain, which is worth more than searching.
- Fill four fields — name, full company name, job title, city. These four decide whether anyone can find you.
- Write one sentence — "I am [company plus title]; I help [whom] solve [what]; right now I am looking for [what]."
- Post one demand — the title carries result, scale and timing. Example: looking for a cross-border logistics partner (Southeast Asia lane, three containers a month).
- Sign up for one Small Circle — the eight-person kind. Meeting once beats ten messages.
② the one specific thing I am asking or proposing
③ the equal value I bring
② do not open with "are you there?"
③ do not walk away without leaving a review
COperations pack: monthly SOP and checklists
For chamber officers and operators: the rhythm of a month, the closing of an event, and a weekly report you can hand over. Follow it and you do not have to reinvent it each time.
C.1 Monthly operations SOP
| When | What | Which module | Output |
|---|---|---|---|
| Week 1 | Close last month's numbers, publish this month's event schedule, invite ten new members | Dashboard / Events / Members | A one-page monthly report, an event calendar |
| Week 2 | Run one Small Circle (eight people), follow up in the 48 hours after | Events plus messages | Attendee list, notes from three real conversations |
| Week 3 | Demand review: chase closures, fix tags, push three good posts | Supply & Demand | Higher closure rate, refreshed content |
| Week 4 | Review drive: find this month's completed collaborations and ask both sides to review | Reviews | New cases on the Trust Wall |
C.2 The 48-hour post-event checklist
Seventy per cent of an event's value is afterwards. Start this the day it ends and finish within 48 hours:
- 0–6 hours: upload the photos to the album; post an event summary in the community (one group photo plus three key points).
- 6–24 hours: message the three people you most want to talk to, each message referring to one specific detail from the day.
- 24–36 hours: turn a need you heard at the event into one demand post (anonymised, with consent).
- 36–48 hours: ask participants for reviews; send those who registered but did not come an invitation to the next session.
C.3 The operations funnel: from intake to conversion
C.4 Running members by segment
| Segment | Signs | What you do | What you do not do |
|---|---|---|---|
| Dormant | Registered over thirty days ago, no demand, no interaction | Message them one to one, asking only "is there anything you need help with just now" | Do not mass-send event notices; that just accelerates the block |
| Beginner | Registered, profile incomplete | Give them the seven-day card and help rewrite their one-line positioning | Do not hand them a fourteen-field checklist at once |
| Active | Interacts monthly, posts a demand now and then | Invite them to run a Small Circle — give them a stage | Do not keep them as an audience |
| Core | Refers often, reviews often, brings newcomers | A title, priority seats, a role in community co-management | Do not substitute "thank you" for actual benefit |
C.5 Weekly report template (copy as is)
DTraining pack: teaching map and assessment
For trainers and those responsible for training: a ninety-minute outline, an operating assessment, and a thirty-day follow-up design. Cut it to your audience if you must, but do not skip the practice.
D.1 Ninety-minute course outline
| Time | Segment | Content | What learners produce |
|---|---|---|---|
| 0–10 | Opening: why a network does not keep | The three kinds of loss plus the comparison table | Name the loss that hurts them most |
| 10–25 | The whole picture: five entries, thirteen modules | Figure 1-1 / Figure 2-3 | Draw the three cells they will actually use |
| 25–45 | Practice 1: make yourself findable | 2.3 templates plus 3.6, four key fields | A one-line positioning and a demand draft |
| 45–60 | Practice 2: find three people | Multi-dimension filters plus the thirty-second checklist | Three names and the first sentence for each |
| 60–75 | Cases: the three scenarios | Chapter 4 | Pick one scenario, write tomorrow's first step |
| 75–85 | Rules: index, credits, boundaries | Chapter 5 plus Chapter 9 | Know what not to do |
| 85–90 | Close: the seven-day card | Appendix A | Sign their own seven-day commitment |
D.2 Operating assessment (eight items, usable as a completion standard)
| # | Action | Pass standard | Section |
|---|---|---|---|
| 1 | Complete a one-line positioning | Contains company, audience and problem | 2.3 |
| 2 | Publish a demand | Title carries result plus scale plus timing; two tags | 3.4 |
| 3 | Find a specified person using three dimensions | Found within three minutes, with the reasoning stated | 3.2 |
| 4 | Send a three-sentence message | Has context, a specific request, and equal value | 3.3 |
| 5 | Register for an event and show the check-in code | Code located in My Events | 3.10 |
| 6 | Submit a specific review | Contains a verifiable action or result | 3.13 |
| 7 | Name your lowest dimension and your plan for it | Maps to one concrete action | 3.8 |
| 8 | Name three things not to do | For example faking reviews, trading credits, mass advertising | 9.4 |
D.3 Thirty days after the training
The biggest problem with training is that it is forgotten. Three touchpoints, one broadcast or one-to-one each:
- Day 3: ask one question — "have you posted the demand? where are you stuck?" Only that question, with no other notices attached.
- Day 14: ask them to post "one thing I did on the platform this week" — peer pressure does the work.
- Day 30: look at their index movement and praise the most improved publicly — not the highest score.
D.4 How to talk about the gaps (suggested wording)
You can say: "Two things are still being built — AI recommendations and image messages. But the four things you need to do today — be found, post a demand, register for an event, leave a review — all work. I will walk you through them now, and by the end you can use it."
Why say it that way: what learners want to know is "can I start now", not "is the product complete". Admitting the gap while giving a workable route raises trust rather than lowering it.
EEditorial conventions (for whoever revises this)
This section is not for readers; it is for the next person who maintains the manual. With it, a revision will not produce "the same thing written two ways".
E.1 Terminology and variant characters
| Avoid | Use | Reason |
|---|---|---|
| Mixed simplified and traditional characters in one Chinese sentence | All traditional in the traditional edition | Where the interface shows a simplified character, quote it as is and mark it |
| "Coming soon" | Scheduled | Four words for four states makes readers think there are four states; this book keeps three |
| "Member" used for everyone | Chain contact (form of address) / member (status) | The division of labour is in Chapter 8 |
| WX 脉链链 / WX脈鏈鏈 mixed in English text | WeaveInX, with the Chinese name on first use | Never mix scripts within one edition; English is always WeaveInX |
| "Institution" and "community" used interchangeably | Community (public) / institution (system term) | On first use write "community (also called an institution in the system)" |
| Radar Score called a "trust score"; Pulse Credits called "Pulse Ore"; "six dimensions" for a seven-axis radar | Radar Score, Pulse Credits, seven dimensions — while Trust Score and Pulse Ore are separate things, not earlier names for these | The Radar Score is the seven-axis average; the Trust Score is a separate trust indicator; Pulse Credits are contribution points; Pulse Ore is a different asset. One name for two things misleads readers |
E.2 Person, numbers and labelling
- Person: address the reader as "you"; the platform refers to itself as "we"; a third-party chamber is "your chamber". Exception: templates written to a counterpart (the three-sentence message, asking for a review) use formal address, because that is outward communication, not the manual speaking to the reader.
- Numbers: spelled-out numbers for rhetorical counting ("three scenarios", "five entries"); figures for interface values, amounts, days, version numbers and section numbers.
- Example figures: anything that is not a real statistic must be marked "(example)" or "as shown on the page". Never present an example as fact.
- Screenshots: each carries "taken YYYY-MM-DD · version" underneath, the version being the review submission number.
- Figure numbering: figures and tables are numbered separately as "Figure chapter-index" and "Table chapter-index"; appendices use "Figure C-1" and "Table C-1". Inserting a figure means renumbering everything after it.
E.3 Three delivery formats
| Format | Good for | Notes |
|---|---|---|
| Single HTML file | Internal reading, jumping around by chapter | Images are embedded, so one file forwards on its own; the file is large (about 3 MB) |
| PDF (A4) | External distribution, printing, attaching to a proposal | Printed from Chrome with headers and footers off; cover on its own page |
| The Appendix B sheet | At an event, inviting from a list, sharing in a group | Can be screenshotted alone; contains no internal notes |
FWhat still needs confirming by the operator
This page is the honesty column of the document. The fifteen items below could not be confirmed from the source code, existing material or these screenshots, so they are not written into the body text (we do not substitute guesses for facts). Items 1–6 affect the whole book, 7 and 8 affect Chapter 10, and items 9–15 are discrepancies found when the drawings were replaced with real screenshots.
Items 9 and 10 are now confirmed — the publishing form now offers four tiers (Small Circle 8 / Gathering 20 / Mid Gathering 40 / Convergence unlimited), matching the training material. The two rows are kept and marked "confirmed" so that anyone who read an earlier draft can see what changed and why, not to pad the table. The other thirteen still await the operator.
| # | What is missing | Which section | What to change once supplied |
|---|---|---|---|
| 1 | The official mini program QR code (image file) | The placeholder in 2.1 and the top right of Appendix B | Replace the .qrph block with the real image |
| 2 | Real member count, event count, number of partner institutions | Chapter 1 (no social-proof numbers are given at present) | Add a "as of" paragraph after 1.2, with the date of the count |
| 3 | How many days a review can be edited | 3.13, 9.2 | Replace "as shown on the page" with the actual number of days |
| 4 | Who actually receives event payments (platform on behalf, or organiser directly) | 3.5, 9.3 | Rewrite the "payee" column of Table 9-2 to match the real arrangement |
| 5 | Who issues invoices, and how | 3.5, 9.3 | Add who issues, how long it takes, electronic or paper |
| 6 | Time windows for future releases (if a public commitment is decided) | 6.4 | The manual gives order, not dates; if dates are decided, commit to an update mechanism at the same time |
| 7 | Three settings needed before H5 can go live: its own domain with HTTPS, the WeChat business-domain allowlist, and the JS-SDK parameters for in-WeChat payment and authorisation Status: still not in place (the dual-platform page is written, but there is no real address for it to point at) | 10.2, 10.4, the "current status" row of Table 10-6, 10.8 | When all three are done, change H5 from "prototype v0.5" to "live" and put the real address in Table 10-6; until then ship the language switch first |
| 8 | Native-speaker editing of the English copy: the three dictionaries (89 keys each) are done and the term list is settled (see Table 10-9); what is missing is proofreading by a native speaker | 10.1, the "English term" column of Table 10-9, common/i18n/en.js | Replace the strings in en.js — no code change needed — and add an English column to Table 8-1 |
| 9 Confirmed | The Small Circle cap: ten or twenty people Original status: training material said twenty, the form said ten — the two documents contradicted each other 9 Nov 2026: the form now reads "Gathering: up to 20", matching the training material | Table 12-1, 3.10, "seat limit" in 12.3 | ✅ Rewritten from the new form; every "ten or fewer" in the body text corrected to twenty |
| 10 Confirmed | Does the "Mid Gathering" tier still exist? Original status: the training material had "Mid Gathering (40)", the form had only Gathering and Convergence 9 Nov 2026: the form restored Mid Gathering and added Small Circle (8) — four tiers in all | 12.1, Table 3-16b | ✅ Rewritten as the four-tier comparison (Table 12-1, Figure 12-1); the training material needs no revision, but it does not list Small Circle and should add it |
| 11 | The heading "seven communities" against eight icons: the screen shows Alumni Chain / International Chamber / Business Chain / Projects / Brand Cooperation / WX Certification / Business Alliance / OPC Smart Network (eight in total) Status: interface copy to be fixed | Figure 11-25, 3.11 | Either change the heading to "eight communities" or fold OPC Smart Network into an existing category |
| 12 | Where the Mall entry is, and whether it is still live: it appears neither in the bottom navigation nor in the home grid, and not among these 25 screenshots Status: not covered in this edition | 3.5 | Confirm the route and its status, and supply a real screenshot; if it has been withdrawn, 3.5 should be rewritten as "benefit redemption" |
| 13 | The task centre and credit redemption pages and rules: "Me" shows only the credit figure (45), with no screenshot of a task entry Status: not covered in this edition | 3.12 | Supply screenshots and the rules (daily tasks, streak bonus, redemption items), and confirm whether credits can actually be redeemed |
| 14 | When trade reviews (F1) go live: the seven-dimension page states "the seventh axis scores only once F1 ships; it currently shows 0 and is excluded from the average" Status: not live | 3.13, Figure 11-10, 12.7 | Once live: add the seventh score, screenshot 3.13, and add "how to object" to the FAQ |
| 15 | Screenshots of the H5 interface: the H5 panel in the preview at the top of the manual currently says "screens to follow" Status: to be obtained | The system preview at the top of the manual, 10.4 | Replace that panel with the real H5 screens and add an "H5 screen guide" section to Chapter 11 |
GThe 160 suggestions, and what happened to each
This page is the construction record: 160 specific suggestions raised from eight viewpoints, one by one. Most revised manuals say only "improved", and the reader has no way to check. We lay every item out, show which section it landed in, and say why a few were deliberately not done.
G.1 V1 — the newcomer's view: can a first-time reader follow it
| No. | Suggestion | Landed in | Status |
|---|---|---|---|
| V1-01 | Add a three-panel "register in 90 seconds" diagram at the start of Chapter 2 | Figure 2-1 | Done |
| V1-02 | "Complete verification" should say what to have ready | Table 2-1 | Done |
| V1-03 | Add copy-and-fill templates after the priority table in 2.3 | 2.3, templates ①②③ | Done |
| V1-04 | Turn every how-to passage into numbered steps | "How to" in each section | Done |
| V1-05 | Map the grid entries to the chapters they lead to | Table 2-4 | Done |
| V1-06 | The floating buttons need a small icon label | Table 2-3 | Partial |
| V1-07 | Reorder the FAQ by "the moment I hit the problem" | Chapter 7, situations 1–7 | Done |
| V1-08 | Add a "five most common sticking points" box at the end of Chapter 2 | Table 2-5 | Done |
| V1-09 | Open Chapter 6 with one positive framing sentence | Chapter 6 opening | Done |
| V1-10 | Add a redemption mapping row to the 3.12 task table | Table 3-19 | Done |
| V1-11 | Explain the three core concepts the first time they appear | 3.2 / Chapter 8 | Done |
| V1-12 | Annotate the home screenshot with zones ①②③④ | Figure 2-2 plus Table 2-3 | Done |
| V1-13 | Mark the status wherever the AI assistant is mentioned | Table 1-2 | Done |
| V1-14 | Add "if you only have one minute" at the end of every module | "One minute" in each section | Done |
| V1-15 | Give the thirteen modules a recommended order | Table 3-1 | Done |
| V1-16 | Add "what if they never reply" to message etiquette in 3.3 | 3.3 | Done |
| V1-17 | Pair the five Mall ordering steps with a flow explanation | 3.5, transaction flow | Done |
| V1-18 | Give a cancel-and-refund conclusion beside the attendee path in 3.10 | 3.10 | Done |
| V1-19 | Give every glossary entry a "back to the text" anchor | Table 8-1, third column | Done |
| V1-20 | Add a "new member seven-day card" at the end of the book | Appendix A | Done |
G.2 V2 — the senior business view: can I take this straight into a negotiation
| No. | Suggestion | Landed in | Status |
|---|---|---|---|
| V2-01 | Add an end-to-end "deal path" diagram | Figure 4-4 | Done |
| V2-02 | Upgrade the "golden formula" into "five checks before anyone can refer you" | 3.2, five checks | Done |
| V2-03 | Give two complete examples of how to write a demand | 3.4, examples A and B | Done |
| V2-04 | Add a thirty-second due diligence checklist | 3.3 | Done |
| V2-05 | Give the Radar Score a band reference | 3.8, how the index is defined | Done |
| V2-06 | Pair each of the seven dimensions with "three things this week" | Table 3-11 | Done |
| V2-07 | Add a referral request script | Templates ③ and ④ | Done |
| V2-08 | Add three criteria for "is this worth taking on" to the Opportunity Plaza | Table 3-10 | Done |
| V2-09 | Add "how to ask for a review gracefully" | 3.13 | Done |
| V2-10 | Mark which four of the fourteen fields most affect being found | Table 3-9 | Done |
| V2-11 | The Mall should answer "can I list my own products" | 3.5 | Done |
| V2-12 | State plainly "this chapter can be skipped" | Chapter 3 opening | Done |
| V2-13 | One page: "from I need X to sending the first message" | Appendix B | Done |
| V2-14 | Three scenario variants for the first line of a message | Template ④, three scenarios | Done |
| V2-15 | Teach how to use L1 / L2 / L3, not only what they mean | Table 3-12 | Done |
| V2-16 | Add a dedicated section on common failure patterns | 5.4 | Done |
| V2-17 | Be explicit about time invested and what comes back | Chapter 7, question ② | Done |
| V2-18 | Say clearly whether credits convert into money or services | Table 3-19 plus 5.2 | Done |
| V2-19 | Treat "closed" on a demand post as visible social proof | 3.4 | Done |
| V2-20 | Add a section on cross-city and cross-border use | 1.7 (new in this edition) | Done |
G.3 V3 — the chamber operator's view: can I manage this group of people
| No. | Suggestion | Landed in | Status |
|---|---|---|---|
| V3-01 | Add a monthly operations SOP | Appendix C.1 | Done |
| V3-02 | Give health thresholds for the six dashboard metrics | Table 3-13 | Done |
| V3-03 | The four event tiers need a decision table, not only a size table | Table 3-16 | Done |
| V3-04 | Add a 48-hour post-event action list | Appendix C.2 | Done |
| V3-05 | Add a community cold start | 3.11 | Done |
| V3-06 | Say whether operators can define their own tasks | 3.12 | Done |
| V3-07 | Add a method for running members by segment | Appendix C.4 | Done |
| V3-08 | Turn the manual into a ninety-minute course outline | Appendix D.1 | Done |
| V3-09 | Explain the operations route for bulk import and inviting members | Table 3-4 | Done |
| V3-10 | Explain how rights differ between institution and personal identity | Chapter 7 plus Table 6-2 | Partial |
| V3-11 | Mark the eight toolbox items with who they suit best | Table 3-14 | Done |
| V3-12 | Add two real pain points to on-site check-in | 3.10 | Done |
| V3-13 | Say whether the dashboard can export | 3.9 | Done |
| V3-14 | Split out a one-page A4 member starter sheet | Appendix B | Done |
| V3-15 | Give the reviewers a review-standards checklist | Table 9-3 | Done |
| V3-16 | Explain joint events across communities and chambers | — | Not done |
| V3-17 | Provide a weekly operations report template | Appendix C.5 | Done |
| V3-18 | Say who sets a community's benefits | 3.11 | Done |
| V3-19 | The dashboard should answer "member churn" | Appendix C.4, dormant segment | Partial |
| V3-20 | Add a funnel diagram: intake → activation → retention → conversion | Figure C-1 | Done |
G.4 V4 — the document engineering view: will this survive revision
| No. | Suggestion | Landed in | Status |
|---|---|---|---|
| V4-01 | Unify variant traditional characters | Appendix E.1 | Done |
| V4-02 | Define the division between "member" and "chain contact" | Chapter 8 opening | Done |
| V4-03 | Add Figures 4-1, 4-2 and 4-3 | Figures 4-1 to 4-4 | Done |
| V4-04 | The Chapter 4 flow diagrams must have written steps | Chapter 4 | Done |
| V4-05 | Number and caption every table | All tables | Done |
| V4-06 | Cross-references in the text must actually be clickable | Cross-references | Done |
| V4-07 | Unify the sub-structure of every section | The 3.x four-part structure | Done |
| V4-08 | Unify the status vocabulary to three states | The three-state definition | Done |
| V4-09 | Add a document metadata page | Document page | Done |
| V4-10 | Add a change log | — | Deferred |
| V4-11 | Label every screenshot with date taken and version | Under each figure | Done |
| V4-12 | Inline the images so a forwarded copy does not break | All figures | Done |
| V4-13 | Verify that tables do not overflow sideways on a phone | Responsive styles | Done |
| V4-14 | Group the thirteen modules in the side navigation | Navigation grouping | Done |
| V4-15 | Unify how the brand name is written | Appendix E.1 | Done |
| V4-16 | Add a quick index | Contents plus Table 8-1 | Done |
| V4-17 | Fix the rules for person | Appendix E.2 | Done |
| V4-18 | Fix the rules for numbers | Appendix E.2 | Done |
| V4-19 | Chapter 6 must state its attitude to scheduling | 6.3 and 6.4 | Done |
| V4-20 | Offer two delivery formats (three were delivered) | Appendix E.3 | Done |
G.5 V5 — the product manager's view: will the manual tell a lie
| No. | Suggestion | Landed in | Status |
|---|---|---|---|
| V5-01 | Add "what you can do today" to every partly-usable item | Table 6-1, last column | Done |
| V5-02 | Split "partly usable" into three granularities | The three types of limit | Done |
| V5-03 | Mark the three states by colour on the architecture diagram | Figure 1-1 | Done |
| V5-04 | 1.2 "AI as a capability lever" was empty | Table 1-2 | Done |
| V5-05 | Establish a list of what the manual promises | 6.5, Table 6-5 | Done |
| V5-06 | Give the index's calculation basis, or say plainly that it is not published | 3.8 | Done |
| V5-07 | State how often the data updates | 3.8 | Done |
| V5-08 | Unify the rule for labelling example numbers | Appendix E.2 | Done |
| V5-09 | Give the rationale behind the "next five things" | Table 6-4 | Done |
| V5-10 | Add a known issues section | 6.3 | Done |
| V5-11 | Explain what happens after you report something | 6.7 | Done |
| V5-12 | Add a readiness table by role | Table 6-2 | Done |
| V5-13 | Add the key payment and invoice information to the Mall section | Table 3-8 | Done |
| V5-14 | Unify how "review" is explained | 3.4 / 3.10 / 9.4 | Done |
| V5-15 | Add a section on quotas and limits | 6.6 | Done |
| V5-16 | Give an actual number of days for "update within the window" | Appendix F, item 3 | Partial |
| V5-17 | Add "how we decide what to build" to Chapter 6 | 6.4 | Done |
| V5-18 | Say which features will never be built | 6.4, four items | Done |
| V5-19 | Use three-colour status badges, marked where they appear | Throughout the text | Done |
| V5-20 | Bind the manual to the app version and announce it | Document page | Done |
G.6 V6 — the growth view: can I use this to persuade someone
| No. | Suggestion | Landed in | Status |
|---|---|---|---|
| V6-01 | Put the mini program QR code on the cover | 2.1, placeholder | Partial |
| V6-02 | Split out a member starter sheet that can be forwarded alone | Appendix B | Done |
| V6-03 | Turn the "three kinds of loss" into a standalone shareable card | Table 1-1 | Partial |
| V6-04 | The book lacks social proof (real statistics) | Appendix F, item 2 | Not done |
| V6-05 | Add a call to action at the end of every chapter | Each chapter's "next" | Partial |
| V6-06 | Pair the trust flywheel diagram with a quotable slogan | Figure 5-1 | Done |
| V6-07 | Scanning in carries the invitation, but the book never says what the inviter gets | 2.1 | Done |
| V6-08 | Add a comparison table against traditional methods | Table 1-4 | Done |
| V6-09 | Extend the three reading routes into a forwarding guide | Chapter 0 | Done |
| V6-10 | Add member levels and benefits — the biggest conversion gap | 1.6 | Done |
| V6-11 | Show typical products and price bands in the Mall section | — | Not done |
| V6-12 | If there is a newcomer gift or first-week bonus, it must be stated | — | Not done |
| V6-13 | Add a support entry and contact details at the end | 9.7 and the end page | Done |
| V6-14 | Make a one-page infographic | Appendix B | Partial |
| V6-15 | Add a pseudonymous character story to the Chapter 4 scenarios | Chapter 4, Mr Lin | Done |
| V6-16 | Distil the FAQ into the top three worries, placed first | Chapter 7 opening | Done |
| V6-17 | Rewrite "does not replace legal remedy" as "what protection the platform does offer" | 9.5, Table 9-4 | Done |
| V6-18 | Give every chapter its own anchor link | Chapter anchors | Done |
| V6-19 | Add a fixed entry for "how to get the latest version" | 9.7 | Partial |
| V6-20 | Produce a three-minute video script | — | Not done |
G.7 V7 — the compliance view: will something go wrong
| No. | Suggestion | Landed in | Status |
|---|---|---|---|
| V7-01 | "Verification" must state what is collected and why | 9.1, Table 9-1 | Done |
| V7-02 | The index is automated scoring of a natural person | 9.2 | Done |
| V7-03 | The review mechanism must cover objection and appeal | 9.2, four steps | Done |
| V7-04 | Explain who can see a case fingerprint | Table 5-2 | Done |
| V7-05 | Messages: retention period and the rules for access | Table 9-1, message row | Done |
| V7-06 | State explicitly that verified data is not given to the chamber | Table 9-1 and 2.2 | Done |
| V7-07 | "Nearby members" involves location: explain the scope of consent | Table 9-1, location row | Done |
| V7-08 | Raise the rank of the disclaimer | Chapter 9 | Done |
| V7-09 | Add a full chapter on disclaimers and the limits of responsibility | Chapter 9 | Done |
| V7-10 | The flow of event fees must be clear | Table 9-2 | Done |
| V7-11 | Credits statement: not transferable, not cashable, no monetary value | 5.2 | Done |
| V7-12 | "A referral cannot be overwritten" — explain what happens on exit | Table 9-5 (new) | Done |
| V7-13 | The book has no "how to close an account" | 9.6 | Done |
| V7-14 | Add eligibility restrictions | 9.4 (new) | Done |
| V7-15 | Check that examples do not point at identifiable real companies | Chapter 4 | Done |
| V7-16 | Showing another's company, title and city involves third-party data | 9.1, last paragraph | Done |
| V7-17 | Add a summary of content review standards | Table 9-3 | Done |
| V7-18 | "There are no fake people here" was an absolute claim; rewritten | Throughout and the end page | Done |
| V7-19 | AI features must state their data boundary | 9.2, platform data only | Done |
| V7-20 | The end must carry a compliance information page | 9.7 | Done |
G.8 V8 — the instructional design view: can I teach from it
| No. | Suggestion | Landed in | Status |
|---|---|---|---|
| V8-01 | Open each chapter with three "what you can do after this" bullets | The 3.x structure plus "one minute" | Partial |
| V8-02 | Tag the thirteen modules must-learn / optional / role-specific | Chapter tags | Done |
| V8-03 | Add an operating assessment | Table D-2 | Done |
| V8-04 | Turn the Chapter 4 scenarios into situation cards | Chapter 4 | Partial |
| V8-05 | Add trainer-note markers | Appendix D.4 | Partial |
| V8-06 | Turn the glossary into a pre-reading card with a five-question quiz | Chapter 8 | Done |
| V8-07 | Add the ten questions learners ask most, with model answers | Chapter 7 | Partial |
| V8-08 | Package the 3.12 task mechanism as a 21-day habit programme | 3.12 | Done |
| V8-09 | Order by increasing difficulty rather than by screen order | Table 3-1 | Done |
| V8-10 | Give every screenshot a line of trainer voice-over | — | Not done |
| V8-11 | The three-role drill in 3.10 lacks a task sheet | Appendix D.1, practice segment | Partial |
| V8-12 | Design a thirty-day post-training follow-up | Appendix D.3 | Done |
| V8-13 | Produce a separate "one-line answer" version of the FAQ | Chapter 7 opening | Partial |
| V8-14 | Explain the blended learning path | — | Not done |
| V8-15 | Turn 3.13 into a "find the mistake" exercise — the best teaching point in the book | Table 3-21 | Done |
| V8-16 | Add how to evaluate whether the training worked | — | Not done |
| V8-17 | Say whether there is a certificate | — | Not done |
| V8-18 | The trainer edition needs wording for discussing the gaps | Appendix D.4 | Done |
| V8-19 | Suggest three self-check questions per chapter | Chapter 8, five questions | Partial |
| V8-20 | Produce a one-page teaching map for trainers | Appendix D.1 plus Table 0-1 | Done |
G.9 The items only partly done, and why
Nine items were not done and sixteen were only partly done. Writing "improved" and stopping there would be exactly the habit this appendix exists to break, so each gets a reason:
| No. | Status | Reason |
|---|---|---|
| V1-06 | Partial | An icon for the floating buttons would have to follow the real UI; a hand-drawn icon would differ from what is online. Instead Table 2-3 explains in words what the three buttons do. |
| V3-10 | Partial | The personal / enterprise distinction is explained in Chapter 7 and Table 6-2, but was not made a separate section — that would confuse it with the membership levels in 1.6. |
| V3-16 | Not done | The product has no cross-community joint-event function; writing it in would be a false promise. Logged for the next edition. |
| V3-19 | Partial | Churn can be inferred from the dormant segment in C.4; the dashboard itself has no churn metric, and we will not invent one. |
| V5-16 | Partial | The number of days a review stays editable must come from the operator (Appendix F, item 3). We will not insert a guessed figure. |
| V6-01 | Partial | The official QR code has not been supplied (Appendix F, item 1); a placeholder and replacement instruction are in place. |
| V6-03 | Partial | The three kinds of loss are tabulated (Table 1-1); a standalone card is a design asset and needs design resource, so it is deferred. |
| V6-04 | Not done | The platform has no publishable real member or event statistics; writing numbers would be fabrication. Honestly logged as Appendix F, item 2. |
| V6-05 | Partial | Each chapter ends with a "next" pointer, but a conversion-style call to action was not designed for every chapter, to avoid a sales tone. |
| V6-11 | Not done | Typical products and price bands need the Mall's real catalogue; there is no stable data, and hard-coding it would soon be out of date. |
| V6-12 | Not done | Whether a newcomer gift or first-week bonus exists, and what it contains, is unconfirmed. Writing it wrongly would be a false promise. |
| V6-14 | Partial | Appendix B is already a one-page starter that can be printed or forwarded; a separate infographic needs design resource. |
| V6-19 | Partial | 9.7 already says "the online version governs"; a fixed entry at the end needs a stable release URL, which does not exist yet. |
| V6-20 | Not done | A three-minute video script is a different deliverable (audio-visual) and falls outside the scope of a manual; handled separately. |
| V8-01 | Partial | The 3.x sections already follow purpose → meaning → features → value plus a one-minute version; adding three opening bullets as well would repeat the same thing in every section. |
| V8-04 | Partial | Chapter 4 already carries the pseudonymous character and the step-by-step; turning it into situation cards is classroom material and belongs in a separate trainer edition. |
| V8-05 | Partial | Trainer wording is concentrated in Appendix D.4; marking trainer notes throughout would disturb the reading rhythm for ordinary readers. |
| V8-07 | Partial | Chapter 7 is organised by seven situations, with the direction of the answer for each; a separate "ten questions" list would duplicate it. |
| V8-10 | Not done | Screenshot voice-over belongs to a trainer edition; in an external manual it adds length and reading burden. |
| V8-11 | Partial | Appendix D.1 already contains two practice segments; a task sheet specific to 3.10 belongs with the course pack. |
| V8-13 | Partial | "Start with these three" at the opening of Chapter 7 is the prototype of a one-line version; a full one would require rewriting every question, and is scheduled for the next edition. |
| V8-14 | Not done | A blended path (online plus in-person) has to match an actual course schedule, and there is no schedule data. |
| V8-16 | Not done | Evaluating training needs a pre- and post-test design and a sample; that belongs to a training project, not to this manual. |
| V8-17 | Not done | Whether a certificate exists, and who awards it, is decided by the chamber; the platform should not promise it. |