AI Models & Platforms
Appian Expands AI Agent Controls and Unveils Ask Appian

Key PointsAppian places agents inside deterministic processes so rules handle predictable work…
View more
- Appian places agents inside deterministic processes so rules handle predictable work and agents handle judgment.
- Raiffeisen reported that a hybrid agent-and-rules approach cut token consumption and processing time by 80% in testing.
- Appian's control plane still lacks cross-platform tracing and measurement for agents built outside its platform.
Appian expanded its AI-agent control plane and unveiled Ask Appian at Appian Europe in London on November 17, 2026, with tools for process-level oversight and outcome measurement. In the announcement, Raiffeisen Bank International reported that a hybrid agent-and-rules approach reduced token consumption and processing time by 80% in testing.
The control plane is designed to register Appian and third-party agents in one management view, monitor activity and cost, restrict usable models, track policy compliance and generate alerts. Its optimization layer uses evaluations to track accuracy and connects agents to the cases and process steps they handled, with business key performance indicators (KPIs) such as cost per case and cycle time supplying the operating context.
Ask Appian is a separate interface for requesting work in plain language. It is designed to draw relevant context from systems connected through Appian’s data fabric and dispatch agents to finish the task. The stated goal is to spare employees from moving between underlying applications to assemble information and complete a request.
Agents as Steps in Deterministic Processes
Appian’s approach places agents inside deterministic business processes, where the process controls the sequence and each step is assigned to an agent, person, system or rule. Rules handle predictable work, while agents receive guardrails and shared context for steps requiring judgment. If an agent fails or is stopped, the task can go to a person, rule or another agent so the case continues.
Sanat Joshi, Appian’s executive vice president of product management, said permissions, guardrails and model access cannot establish whether an agent is doing useful work. “Appian puts business process at the center,” he said, describing the company’s focus on how each agent affects business outcomes.
A November 16, 2026 Appian blog post explains the trade-off. Process-led steps are consistent, repeatable and auditable; agent-led steps can handle open-ended work but add cost and latency, with outcomes that can vary by case. In one example, an agent assessing a loan hands debt calculations to deterministic formulas while a loan officer makes the final decision.
Current Integrations and Planned Measurement
Appian’s control-plane documentation draws a line between current functions and later additions. Third-party agents can now serve as steps in Appian processes through MCP or direct integration without moving into Appian. Support for the A2A protocol, a registry encompassing third-party agents and tracing for agents running outside Appian come next.
Measurement has a similar boundary. Appian agents are already measured against process KPIs. The documentation lists estimated cost per case and per step for Appian and third-party agents, before-and-after comparisons with manual work and agent-improvement recommendations as forthcoming.
Many control-plane capabilities are available, including controls, orchestration and process intelligence, and customers can join an early-adopter program for access before general availability. Appian said additional capabilities would start arriving during 2026, but planned features and timing can change and purchasing decisions should rest on generally available functionality.
Raiffeisen’s Agent-and-Rules Test
Raiffeisen Bank International intends to automate payment inquiries with Appian. Claus Mitterlehner, its head of smart automation, said the team initially gave most tasks to AI agents. “After testing it, the team changed course and moved the predictable steps to deterministic automation, keeping agents for the steps that need judgment,” he said.
That is the control plane’s broader optimization loop: evaluations and process KPIs identify how agents perform, and repeated agent steps can become deterministic workflows or business rules. The intended result is a process in which agent spending is concentrated on judgment-based work rather than predictable execution.
The landing page for a study by Appian and Harvard Business Review Analytic Services reports that 92% of respondents said agents need rules-based guardrails to be safe and effective, while 48% had such rules in place. The study surveyed AI decision-makers and examined modernization and workflow integration.
The control plane’s business case therefore depends on more than keeping agents within policy. Its useful test is whether process evidence can show where agents improve cost, speed or accuracy and where repeated work should become rules. Raiffeisen’s reported test supplies the concrete example; the planned cross-platform registry, tracing and measurement features will determine how consistently Appian can extend that analysis across agents built elsewhere.












