WeChat (WeCom)
WeChat (WeCom)
WeChat (WeCom) lets customers on WeChat reach your organisation through WeCom (企业微信) customer-service accounts (module wecom). Their messages arrive in Conversations, where you and your agents answer them. It can also read staff members' own WeCom contacts, so a supplier can be asked for quotes through the staff member who knows them.
In the sidebar under Connections → WeChat (WeCom).
Before you start
WeCom has its own requirements before Max can connect. These are your organisation's steps, outside Max. Allow a few weeks for the filing.
- A verified mainland WeCom organisation.
- A domain filed (ICP 备案) under the same company.
- A small mainland server in your company's own cloud account, to run the relay.
- A self-built app in WeCom.
Show the checklist shows these again.
WeChat (WeCom)
Connection
Your WeCom organisation and its self-built app, and where the relay runs:
- Label and Owner: the person who answers for WeChat. Notices go to them and they own each account's conversations. They need permission to reply to conversations.
- Corp ID, AgentId and App Secret, from the WeCom admin console. The Secret is sealed the moment it is saved and never shown again.
- Relay address: where the relay answers WeCom on your filed domain. Relay tunnel: every call Max makes to WeCom goes through it.
- The organisation is verified (已认证): tick once WeCom shows it. Unverified organisations can serve only about 100 customers in all, and Max counts them.
Set-up checklist
The values to paste into WeCom and the relay's settings file: the URL (paste into WeCom), Token and EncodingAESKey. Max makes the Token and EncodingAESKey itself. Showing them is recorded in the audit trail. Copy URL, Copy Token, Copy EncodingAESKey, Download relay settings, New Token, New EncodingAESKey and New relay key.
Test
Six checks, each through the relay where it needs WeCom: whether WeCom accepts the Secret, answers from the trusted address, has verified the callback URL, lists customer-service accounts for the app, whether a message has arrived, and whether the organisation is verified. Each one passes or says what is wrong and how to fix it.
Customer-service accounts
The WeCom customer-service accounts (微信客服) assigned to your app. Switch one on and it becomes an account in Conversations: its messages arrive there and replies go from there. Its reply settings are set under Conversation settings →.
Entry links
Make link and QR code for an account, with a label people in Max see on each conversation from it, such as "Canton Fair catalogue". WeCom's entry links do not expire: removing one here does not stop a printed copy from working.
Staff contacts
Off until you switch it on. Then once a night, and when you press Sync now, Max reads the external contacts (客户联系) of every staff member the app may see: names, companies, and the staff member's remark and tags. Search with Find and link a contact to a Supplier or a contact in Max. Requests for quotes to that supplier can then go through the staff member, who confirms them in WeCom.
Staff messages
Messages Max prepared in WeCom for a staff member to confirm and send to one of their contacts, such as a request for quotes. Nothing reaches the contact until the staff member taps send in their WeCom app.
Costs
What WeChat through WeCom costs your organisation and where each figure comes from, including the Relay server's price, which you enter and Save price.
Who can do what
| Permission | Lets you |
|---|---|
wecom:read | See the WeCom connection, its customer-service accounts and entry links, staff contacts and staff messages. |
wecom:manage | Connect WeCom, change its credentials, relay, customer-service accounts and entry links, link staff contacts. |
See People, roles and permissions.
What happens on its own
| Job | When | What it does |
|---|---|---|
events | Every minute, and as soon as a callback arrives | Reads stored WeCom callbacks and hands messages to Conversations. |
sync | Every 2 minutes | Reads new messages from the switched-on customer-service accounts. |
health | Every 10 minutes | Checks the connection when a check is due. |
unknown | Every 15 minutes | Settles sends whose outcome stayed unknown. |
contacts | Every day at 03:00 UTC | Reads staff members' WeCom contacts, when staff contacts are switched on. |
staffResults | Every 15 minutes | Checks whether staff confirmed the messages prepared for them. |
tidy | Every day at 03:30 UTC | Removes old rows. |
Needs
Nothing has to be switched on first. Messages are answered in Conversations. Linking a supplier needs Sourcing.
What agents can do
Reads run straight away. Changes wait for a person's approval by default. Staff contacts' names, remarks and tags are outside content. See Agents and approvals.
Read only: wecom.status, wecom.test, wecom.contacts
Change: wecom.linkContact links a staff contact to a supplier or contact in Max, and writes nothing to WeCom. wecom.prepareStaffMessage prepares a message in WeCom for the staff member to confirm and send.
Over MCP the same tools are named wecom__status and so on. See API keys and MCP access.