安全客July 28, 2026🇨🇳Translated from Chinese

88% of Enterprises Run AI Agents but Fewer Than 10% Generate Profits, Ronglian Cloud Reports at WAIC Forum

At the 2026 World Artificial Intelligence Conference, a striking statistic was repeatedly cited: 88% of enterprises worldwide already have AI Agents running internally, yet fewer than 10% are generating real profits from them. The gap has prompted a shift in evaluation criteria from “what can the Agent do” to “what concrete business outcomes has it delivered.”

On July 20, Ronglian Cloud hosted the fourth WAIC Enterprise Agent Forum at the Shanghai World Expo Center under the theme “Evolution and Commercial Landing of Enterprise Agents.” The company, which began with call-center and contact-platform technology and now serves 20,000–30,000 enterprises while managing over one million agent seats, has spent the past two years determining how to move Agents from “deployed” to “profitable.”

Ronglian Cloud Vice President of R&D Tang Xingcai presented the 88% versus sub-10% figures and noted that many firms previously measured intelligence by token consumption volume. That metric has lost credibility in 2026. Speakers from industry alliances, retail, finance, and electronic-signature vendors all stressed that enterprises now pay only for measurable returns rather than possibilities.

Multi-point Digital Intelligence Vice President Zhang Yu reported that clients no longer ask about system functions; they ask directly how the solution will increase sales or reduce losses. eSignBao founder Jin Hongzhou added that the ultimate test is whether customers are willing to pay and continue using the Agent successfully.

Tang Xingcai described a four-stage adoption framework derived from four years of internal deployment. Stage one is Copilot-style single-task assistance such as call summarization. Stage two enables independent task closure, for example analyzing 30 days of calls for complaint risks or missed opportunities. Stage three integrates Agents into existing human-designed business processes so one employee can supervise ten Agents. Stage four delivers fully autonomous end-to-end business loops without human intervention.

Most organizations remain between stages two and three: tools are purchased but have not been embedded into workflows, preventing value creation. Ronglian Cloud also discovered that optimal efficiency requires humans to adapt to Agent workflows rather than the reverse; contact-center agents now act as reviewers and trainers who confirm or refine Agent suggestions, continuously improving model performance.

To make Agents deliver results, Ronglian Cloud implemented three concrete measures. First, a semantic data layer connects Agents to CRM, ticketing, and financial systems so they can read and act on orders, contracts, and work orders without altering employee habits. Second, layered governance using prompts, skills, orchestration engines, and an independent quality-inspection platform controls randomness according to compliance requirements. Third, Agents are evaluated on business KPIs—order conversion rate, ticket resolution time, GMV contribution—rather than technical accuracy scores.

In June the company launched Voice Agent and Private Domain Operation Agent. The Voice Agent handles collections, customer service, and marketing with a 94% conversation completion rate and supports tiered escalation from specialist Agent to supervisor Agent to human. The private-domain Agent allows one operator to manage hundreds of thousands of customers; a benchmark healthcare client uses it to oversee 80,000 private-domain users, generating approximately 1.2 million RMB monthly GMV with 87% year-over-year growth.

Cost comparisons are compelling: a human agent costs 5,000–8,000 RMB per month and handles 150–300 calls daily after weeks of training, while an Agent costs 2,000–3,000 RMB, operates 24/7, processes over 20,000 conversations daily, and retains all accumulated experience. Although current Agents reach only 70–80% of top human performance, the combination of acceptable quality and near-zero marginal cost is already reshaping staffing models. Ronglian Cloud has begun testing outcome-based pricing in revenue-generating scenarios such as collections, sharing risk with clients via recovery-rate revenue share.

Forum participants concluded that the three-to-six-month window for establishing defensible ROI and scaling is narrow. Companies that first embed Agents deeply into real business processes and demonstrate clear returns will build the lasting competitive moat; industry know-how accumulated through daily operations cannot be purchased or easily replicated.

Related articles

SecuritylabOther

Prioritizing Account Protection: Moving From Job Titles to Real Business Risks

When budgets are limited, companies must decide whether to protect C-level executives first or focus on employees handling critical data such as accountants, database administrators, and developers. The article outlines four practical scenarios that determine protection priorities instead of relying on corporate hierarchy. These include perimeter defense through VPN access, safeguarding email and documents against phishing, addressing unique user cases like offline executive work, and managing contractor accounts with mandatory multi-factor authentication. A protection matrix maps assets such as commercial information, infrastructure access, and privileged accounts to specific threats and controls including 2FA, DLP systems, and PAM solutions. The piece also highlights three common mistakes, such as treating tool deployment as the finish line, underestimating pilot preparation, and attempting to secure everything simultaneously. It concludes with actionable first steps: inventory accounts, disable unused ones, enable two-factor authentication for high-risk users, and expand coverage gradually.

AntiMalwareOther

Russian Voice Traffic Surges 25-30% as Mobile Internet Usage Falls for First Time

In the first half of 2026, voice traffic in Russian mobile networks grew by 25-30 percent while mobile internet consumption declined 10-12 percent for the first time. Home broadband traffic rose 18-20 percent as users shifted conversations to traditional voice calls and moved video, AI services, and other data-heavy applications to fixed Wi-Fi connections. Experts attribute the changes primarily to mobile internet restrictions and difficulties accessing foreign messengers, prompting a return to basic phone functionality. Additional load on wired networks comes from IoT devices including surveillance cameras, sensors, and smart watches. In May, traffic generated by AI bots exceeded the volume of data created by human users for the first time. Analysts forecast that by the end of 2026 mobile internet traffic will drop another 5-10 percent, while fixed broadband will grow 15-20 percent and voice call volumes will increase 10-15 percent.

HabrOther

Incident Reconstruction Fails When Logs Lack Time Zone Offsets and Proper Synchronization

Reconstructing security incidents from multiple log sources often collapses when timestamps lack time zone information or consistent synchronization. Events from web servers, load balancers, applications, and mail gateways can appear in physically impossible order, such as responses preceding requests or sessions closing before they open. The root causes include clock drift without NTP, mismatched reference points like UTC versus local time, and timestamps recorded at message processing rather than event occurrence. Classic BSD syslog (RFC 3164) omits both year and offset, forcing investigators to consult potentially unavailable source systems. Modern RFC 5424 provides full timestamps with offsets, making normalization possible without external context. Organizations must enforce offset-inclusive formats at ingestion, monitor actual synchronization status rather than service uptime, and document external sources whose timestamps cannot be controlled.

SecuritylabOther

HTTP Methods Explained: GET, POST, PUT, PATCH, DELETE and the New QUERY Standard

HTTP methods define the actions a client requests from a server regarding a resource. The core semantics are outlined in RFC 9110, with extensions for specialized protocols. A new standardized method called QUERY was introduced in June 2026 via RFC 10008 to handle complex queries that include a request body while remaining safe and idempotent. The article details safe and idempotent properties, compares each method including GET, HEAD, POST, PUT, PATCH, DELETE, OPTIONS, TRACE, CONNECT, and QUERY, and explains their correct usage to avoid breaking caches, proxies, and infrastructure expectations. It also covers WebDAV extensions and other registered methods in the IANA registry.