GrabFujiao LiuProblem & solution
Streamlining RiskOps with the SOP agent framework
Summary
Risk Operations teams investigating Account Takeover (ATO) cases must gather data across systems, run SQL queries, and make decisions under pressure, creating delays and error risk. The SOP-driven LLM agent framework represents the workflow as a natural-language, indentation-based tree whose steps specify queries, external functions, and decision criteria. During execution, the SOP planner navigates the tree and produces JSON-formatted instructions, while a Worker Agent invokes APIs or SQL queries and stores results in a feedback loop. The process ends by synthesising investigation data into a report and final decision. In reported results, handling time fell from 22 to 3 minutes per ticket, 87% of ATO cases were automated since launch, and the error rate was zero.
Context
ATO investigations in Risk Operations traditionally require analysts to analyse large amounts of data from disparate systems, cross-reference information, execute multiple SQL queries, and make repeated decisions. The source identifies delays, decision fatigue, human-error risk, and resource constraints as barriers to an efficient, reliable, and scalable process.
Approach / What changed
The framework encodes an ATO investigation as a natural-language SOP with an indentation-based tree. The SOP planner determines investigation steps and API calls using a Depth-First Search-inspired execution strategy, while the Worker Agent interprets JSON-formatted SOPs, invokes APIs or SQL queries, stores results, and supports iterative progression through the investigation.
Takeaways
SOPs use an intuitive indentation format, with @function_name notation marking external function or system integration points such as @IP_web_login_history.
The SOP planner and Worker Agent divide responsibilities: the planner navigates the investigation and selects calls, while the Worker Agent executes APIs or SQL queries and stores results.
Reported outcomes include a reduction in handling time from 22 to 3 minutes per ticket, automation of 87% of ATO cases since launch, and a zero-error rate.
Source and freshness
- Source
- engineering.grab.com
- Published
- Added to Yomu
- Last updated
Summaries are generated from the original by a language model. Check the original before relying on it.
Keep reading
Related reading
The Good Stuff
Paid picks we use ourselves. Links carry a referral code — a subscription through one earns us a commission at no extra cost to you.
The best engineering reads, once a week
One useful email. Unsubscribe anytime.