Agents with defined roles and queues
Assign work such as order confirmation, supplier follow-up or invoice matching to an agent. It processes its queue in connected systems and brings decisions that need a person to staff.
Put AI agents to work around your ERP with Riff: automate operational queues, share context with staff and control which actions agents can take.
Riff is an AI agent platform for industrial operations. Agents take defined roles, work through operational queues and act in connected business systems, while staff handle the decisions that require judgment. Its prebuilt work areas include order handling, procurement, logistics, aftermarket and production.
The platform brings together shared operational context, work interfaces, ERP connectors and IT controls. Teams can adapt existing agents or describe new agents and interfaces in a studio, test changes and move versions into production. Riff also provides implementation and training alongside the software; an organization can book a demo around its own workflow and ERP environment.
Assign work such as order confirmation, supplier follow-up or invoice matching to an agent. It processes its queue in connected systems and brings decisions that need a person to staff.
Connect information from the ERP, inboxes, spreadsheets and portals. People and agents work on the same orders, suppliers and cases, with corrections and decisions contributing to shared context.
Named connectors include Dynamics 365, Infor LN and M3, IFS, SAP, Monitor, Jeeves and Epicor. Agents invoke ERP business functions such as creating orders or posting receipts; the ERP remains the system of record.
Describe an agent’s role, queue, rules and permitted actions, or the interface a team needs. The studio produces editable code; changes are versioned, tested against historical work and promoted through staging to production.
IT sets identity, roles and action rules for people and agents. Actions are logged, and workflows can require approval. Procurement agents can begin by proposing actions for a buyer to approve.
Use a direct-procurement workflow to chase supplier confirmations by email, compare dates and prices with purchase orders, and update confirmed information in the ERP.
Have agents prepare and send RFQs, follow up with suppliers and normalize their quotes into a comparison for category managers.
Collect what an employee needs, apply purchasing policies and approval rules, then create an order in the ERP through an indirect-procurement workflow.
Describe an interface for orders, suppliers or cases using the connected data and shared context, then adapt the generated code or agent behavior for the team’s process.
No. It connects to existing ERP systems and uses their business functions. In procurement workflows, orders, prices and confirmations are updated in the ERP, which remains the system of record.
Yes. IT defines roles, permissions and action rules, and workflows can require human approval. Procurement agents can start in propose-and-approve mode; their autonomy can be widened or narrowed.
Yes. Teams can describe an agent or work interface in the studio, correct the generated procedure, test it against historical work and promote versions through staging to production. The output is editable code.
Book a demo of the platform or an agent around the team’s workflow and ERP. A procurement implementation can start with one workflow, such as confirmations or RFQs, connect it to relevant systems and run initially with human approval. Riff provides implementation support and training.
No. Direct, strategic and indirect procurement are offered as three solutions that can be bought individually or together. They share a view of suppliers; select the scope that matches the organization’s work.
Данные о трафике приведены только для справки.