Preface
If you want to implement an enterprise WeChat robot, such as JD/Pinduoduo welfare group, Meituan Luckin scheduled marketing group, self-service order inquiry, intelligent consultation or community management robot, first of all, the official robot API for external groups/customer groups is not provided. Session archiving is only applicable in certain scenarios. When using session archiving in a timely manner, there is also the problem that it can only be received but not sent. What methods can be used to create customer group robots in compliance with regulations?
I think the summary of enterprise WeChat automation technology on the Internet is similar in terms of functions and advantages and disadvantages. The attached picture is as follows:
I will add it from the perspective of compliance and the risk of account ban .
Compliance perspective
- Web page-side protocol: protocol reverse + data forgery + data tampering, non-compliance
- iPad protocol: protocol reverse + data forgery + data tampering, non-compliance
- MAC protocol: protocol reversal + data forgery + data tampering, non-compliance
- PC Hook: code injection + process/memory monitoring, non-compliant
- Xposed technology: code injection + process/memory monitoring, non-compliant
- WorkTool simulation technology: no protocol reverse + no data forgery/tampering + no code injection + no process/memory monitoring, security compliance
Risk of account ban
- Web page protocol: most accounts cannot be used, ignore it
- iPad Agreement: There is a certain probability of account closure. The probability of new accounts or accounts without real names is high, and future risks are uncontrollable.
- MAC Agreement: There is a certain probability of account closure. There is a high probability of new accounts or unidentified accounts, and future risks are uncontrollable.
- PC Hook: There is a certain probability of account closure. The probability of new accounts or accounts without real names is high, and future risks are uncontrollable.
- Xposed technology: There is a high probability of account closure, and the probability of new accounts or accounts without real names is extremely high
- WorkTool simulation technology: no risk of account suspension
Why WorkTool is compliant and risk-free
? This is determined by the principle of the program. Because WorkTool is based on the Google Android system's native accessibility service (an auxiliary service for the elderly or people with visual and hearing impairments), this service is often used to assist screen reading or assist screen recognition and clicking, etc., the Ministry of Industry and Information Technology issued a document requiring All major apps (as shown below) must undergo barrier-free transformation . This is the only automated solution officially supported and endorsed by the government , so we will not have any risk of account closure in the past, present and future.
Click to jump to the link to the Ministry of Industry and Information Technology article
Why WorkTool attaches so much importance to compliance issues?
The WorkTool developer team had many years of experience in WeChat Xposed research and development before 2019, realizing full-featured automation on WeChat. However, because Xposed itself has problems such as easy account closure and non-compliance risks, the team is aware of confrontation with the official There is no future, and the projects involved have been completely cancelled. But we still haven’t given up on finding automation solutions within the scope of compliance, so we decided to develop our own automation framework to make it 100% compliant while improving its automation operation efficiency and response speed, and increasing its business value and social value. . Our self-developed automation framework will continue to be open source. It has no backdoors, is non-intrusive, and does not require root. It is available on 99% of Android devices and runs stably 24/7.
What are the shortcomings of WorkTool?
No automation solution is perfect. We are based on Android’s built-in accessibility service. Before the emergence of WorkTool, this model was often criticized for: high response delay, low efficiency of simulating manual operations; too few functions and Unable to meet business needs. WorkTool is designed to solve the problems of high latency and low efficiency in simulating manual operations. The self-developed automation framework brings the ultimate response speed and is infinitely close to the limit speed of operations in simulating manual operations; in terms of functional perfection, WorkTool already has a wealth of The API functional interface provides the same functional capabilities as those of gray products such as protocols and hooks. Of course, we are not comparing for the purpose of comparing functions. Our purpose is always to serve users and be people-oriented. Products that can meet needs are good products.
See documentation for API interface
postscript
WorkTool's built-in self-developed automation framework can also be quickly expanded to other applications. If you have used automation software such as AutoJS but feel it is not stable enough, you can also use our automation framework to develop automation software for each APP. Compared with It is more stable than using JS engine and directly using Android native development. Github open source address: https://github.com/gallonyin/worktool
If it is helpful, please like and collect it. If you have suggestions, contributions or questions about the automation framework, you can send a private message~