Roy, and the systems it reads and writes
The shape of it
Roy is ROIAI One's AI agent for retailer deductions.
It reaches the records that decide a case in your ERP, in the mailboxes where retailer notices land, and in the retailer portals themselves.
It reads broadly and writes narrowly, and ROIAI One's own analysts review and release what it prepares.
What Roy does with a deduction
Done by hand, every deduction is worked one at a time, a different portal, reason code, and evidence pack for each retailer.
Roy reads the chargeback, gathers your documents and drafts the dispute, ready for review. After review, packets are filed to the retailer portal or emailed to the right contact.
Where Roy works, and what it does there
Roy reads broadly and writes narrowly.
The outer boundary is the permission set your IT team grants the login. Scope that login read-only and none of it can write.
Who checks what gets filed
Roy reviews each deduction, assembles the evidence and prepares the dispute, and ROIAI One’s own analysts review and release it. That review is selective and exception-based. This is our AI-native Service-as-a-Software model: the review burden is ours, not yours.
Roy is also not always a yes. Where the evidence says the charge is valid, Roy says so. The security and access overview covers how that access is scoped in practice.
The two platform pages, and what each answers
What is the agent?
ReadERP IntegrationWhat does connecting actually require of us?
The connection: what Roy reads and what Roy writes, record by record, what connecting does not require of you, and what your side actually has to do.
ReadFor what the platform is pointed at rather than how it is built, the solutions pages route by problem, and the retailer intelligence library covers the channel, evidence, and reason codes for a specific retailer.
See it against your own deductions
The platform is easier to judge on your own book than in the abstract. We look at your deduction history and tell you what is worth recovering.